On Tuesday 18 May 2004 01:53 pm, Robin P. Blanchard wrote: > > -----Original Message----- > > From: owner-freebsd-acpi_at_freebsd.org > > [mailto:owner-freebsd-acpi_at_freebsd.org] On Behalf Of Robin P. > > Blanchard > > Sent: Tuesday, May 18, 2004 1:26 PM > > To: current_at_freebsd.org; acpi_at_freebsd.org > > Subject: RE: panic: lockmgr: locking against myself (kern/64206) > > > > After much wailing and gnashing of teeth, I disabled acpi and > > all of these problems seem to have disappeared. Mobo is old asus P2B. > > Argh. Speaking too quickly. Panic follows (without acpi). Please let me > know what else I might provide. > > # gdb -k /usr/obj/usr/src/sys/fbsd5.vpn/kernel.debug ./vmcore.11 > GNU gdb 5.2.1 (FreeBSD) > Copyright 2002 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are welcome to change it and/or distribute copies of it under certain > conditions. Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-undermydesk-freebsd"... > panic: page fault > panic messages: Unfortunately this is missing the rest of the page fault panic messages including the 'trap 12' etc. Those messages include a line that says 'cs:eip = 0x8:0xblah', and we need the 0xblah part to work out where the page fault happened. Usually these bugs are a NULL pointer deref that can often be easily fixed if we can find out where it happened. Actually, though, the ip can be found from the tf_eip member of struct trapframe, which is 0xc05d1e69. Can you send the output of 'l *0xc05d1e69' from gdb on the same kernel.debug? -- John Baldwin <jhb_at_FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.orgReceived on Wed May 19 2004 - 02:45:15 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:54 UTC