Date: Wed, 15 Jun 2005 17:54:05 -0700 From: Nate Lawson <nate@root.org> To: Eric Anderson <anderson@centtech.com> Cc: freebsd-acpi@FreeBSD.org, John Baldwin <jhb@FreeBSD.org> Subject: Re: cvs commit: src/sys/dev/acpica acpi.c Message-ID: <42B0CDAD.6040806@root.org> In-Reply-To: <42B0C40F.2050503@centtech.com> References: <200506032012.j53KCC5k077879@repoman.freebsd.org> <42B06B2D.4010600@centtech.com> <42B08B57.6010203@root.org> <200506151638.15687.jhb@FreeBSD.org> <42B0C40F.2050503@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Eric Anderson wrote: > John Baldwin wrote: >> >> Actually, we already reprogram all the APIC intpins on resume in >> ioapic_resume() from saved state. There's actually not anything for >> ioapic_suspend() to do, so I've mostly left this as a marker until the >> current resume code is tested. > > I now see that when it is trying to come out of resume, it panics. I > can't see it, and my serial access doesn't seem to work at that point (I > booted with boot -h, maybe I should have set some additional options) - > but if I type 'call doadump' on the keyboard, it dumps. However, I have > no idea what to do with it now that it's dumped :) That's getting somewhere. Use savecore(8) to get a copy of the dump image. Then run dmesg on it to get console messages and gdb /boot/kernel/kernel vmcore and type "bt" to get a backtrace and "print panicstr" to get the panic message. -- Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42B0CDAD.6040806>