Date: Mon, 23 Apr 2007 13:12:30 -0400 From: Michael Proto <mike@jellydonut.org> To: freebsd-stable@freebsd.org Subject: Re: 6.2-STABLE (i386) Repeating crash (supervisor read, page not present) Message-ID: <462CE8FE.8060807@jellydonut.org> In-Reply-To: <20070423155728.GC1006@xor.obsecurity.org> References: <462CA594.5000904@tomjudge.com> <20070423155728.GC1006@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > On Mon, Apr 23, 2007 at 01:24:52PM +0100, Tom Judge wrote: >> Hi, >> >> Recently I have noticed that one of our Dell PE1950's has been crashing >> a lot with the following reason "supervisor read, page not present". >> >> The system runs 6.2 Release under i386. >> >> I have attached 2 back traces, and I still have both cores if any more >> information is required. Any light that can be shed on this problem >> would be greatly appreciated. >> >> Tom >> >> =========== >> >> uname -a >> FreeBSD narthex.mintel.co.uk 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Mon >> Apr 2 20:13:11 BST 2007 >> root@bob.mintel.co.uk:/usr/obj/usr/src/sys/PE1950 i386 >> >> >> ## Core 1 >> >> root@narthex '13:14:47' '/home/london/tj' >>> $ kgdb /usr/obj/usr/src/sys/PE1950/kernel.debug /var/crash/vmcore.1 >> [GDB will not be able to debug user-mode threads: >> /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] >> GNU gdb 6.1.1 [FreeBSD] >> Copyright 2004 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-marcel-freebsd". >> >> Unread portion of the kernel message buffer: >> >> >> Fatal trap 12: page fault while in kernel mode >> cpuid = 0; apic id = 00 >> fault virtual address = 0x100005c >> fault code = supervisor read, page not present >> instruction pointer = 0x20:0xc05df61f >> stack pointer = 0x28:0xe4f63c30 >> frame pointer = 0x28:0xe4f63c90 >> code segment = base 0x0, limit 0xfffff, type 0x1b >> = DPL 0, pres 1, def32 1, gran 1 >> processor eflags = interrupt enabled, resume, IOPL = 0 >> current process = 12 (swi1: net) >> trap number = 12 >> panic: page fault >> cpuid = 0 >> Uptime: 1h25m33s >> Dumping 2047 MB (2 chunks) >> chunk 0: 1MB (159 pages) ... ok >> chunk 1: 2047MB (523944 pages) 2031 2015 1999 1983 1967 1951 1935 1919 >> 1903 1887 >> <7>arp_rtrequest: bad gateway 172.31.1.1 (!AF_LINK) >> <7>arp_rtrequest: bad gateway 172.31.0.1 (!AF_LINK) > > You might be hitting a bug in an obscure code path because of the > above errors. I'm CC'ing someone who might be able to help. > > Kris > Bear in mind that a recent "urgent" firmware update was released by Dell last week for 1950, 1955, and 2950 systems that is supposed to fix some data-corruption issues related to dual-core processors. I don't know if this problem is a symptom of that, but it strongly suggested to apply the firmware update regardless. -Proto
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?462CE8FE.8060807>