Date: Wed, 18 Jun 2008 18:12:33 -0500 From: "Edwin L. Culp" <eculp@casasponti.net> To: freebsd-questions@freebsd.org Subject: Re: reboot after panic : page fault for two consecutive days now with FreeBSD stable 7.0 Message-ID: <20080618181233.80176fck3bdyi680@intranet.casasponti.net> In-Reply-To: <4850203A.5080805@FreeBSD.org> References: <20080611133220.198644ite5u5r778@intranet.casasponti.net> <4850203A.5080805@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway <kris@FreeBSD.org> escribi=F3:
> eculp wrote:
>> This is on a relatively new Dell dualcore with 4G of ram running up =20
>> to date stable. I'm not on site so I have no idea what might be =20
>> provoking these crashes. In fact in many years of running FreeBSD =20
>> I've not seen something just happen like this. It is a =20
>> simi-production machine that cvsups daily and builds and installs a =20
>> new world and kernel. Ports are updated about once a week and =20
>> haven't seen any issues previously. It has been running 24/7 since =20
>> new, about 8 months.
>>
>> 3 files were generated info, bounds and vmcore. The info file follows:
>>
>> Dump header from device /dev/mfid0s1b
>> Architecture: i386
>> Architecture Version: 2
>> Dump Length: 341225472B (325 MB)
>> Blocksize: 512
>> Dumptime: Wed Jun 11 12:34:24 2008
>> Hostname: casasponti.net
>> Magic: FreeBSD Kernel Dump
>> Version String: FreeBSD 7.0-STABLE #258: Tue Jun 10 05:54:42 CDT 2008
>> root@casasponti.net:/usr/obj/usr/src/sys/ENCONTACTO
>> Panic String: page fault
>> Dump Parity: 2395754794
>> Bounds: 2
>> Dump Status: good
>>
>> the vmcore is about 300M so I'm not attaching it;) I could put it =20
>> on line at a moments notice. I think that what I need is probably =20
>> a crash course on debugging a crash and I really don't know where =20
>> to start since after over 10 years with freebsd I've never needed =20
>> it. Any help, suggestions, etc. would be greatly appreciated.
>
> See the developers' handbook chapter on kernel debugging.
>
> However, panics that "suddenly" start happening frequently on a =20
> system that has been stable for a while with no OS or workload =20
> changes made, are usually due to the hardware starting to fail.
>
> Kris
I got as far as I could. I recompiled the kernel with debuging and =20
waited for a new panic. I got the fourth one a few minutes ago and =20
went as far as I could with the handbook.
# kgdb kernel.debug /var/crash/vmcore.4
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 =3D 0; apic id =3D 00
fault virtual address=09=3D 0x0
fault code=09=09=3D supervisor write, page not present
instruction pointer=09=3D 0x20:0xc0716ba9
stack pointer=09 =3D 0x28:0xe6d2bc4c
frame pointer=09 =3D 0x28:0xe6d2bc4c
code segment=09=09=3D base 0x0, limit 0xfffff, type 0x1b
=09=09=09=3D DPL 0, pres 1, def32 1, gran 1
processor eflags=09=3D interrupt enabled, resume, IOPL =3D 0
current process=09=09=3D 13 (swi4: clock sio)
trap number=09=09=3D 12
panic: page fault
cpuid =3D 0
Uptime: 1d4h34m22s
Physical memory: 3315 MB
Dumping 273 MB: 258 242 226 210 194 178 162 146 130 114 98 82 66 50 34 18 2
Reading symbols from /boot/kernel/mfi_linux.ko...Reading symbols from =20
/boot/kernel/mfi_linux.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/mfi_linux.ko
Reading symbols from /boot/kernel/acpi.ko...Reading symbols from =20
/boot/kernel/acpi.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi.ko
Reading symbols from /boot/kernel/fdescfs.ko...Reading symbols from =20
/boot/kernel/fdescfs.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/fdescfs.ko
#0 doadump () at pcpu.h:195
195=09=09__asm __volatile("movl %%fs:0,%0" : "=3Dr" (td));
--------------------------------------------------------------------
That is as far as I got, any suggestions appreciated. I'm going to =20
check the others and see if the get further.
ed
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080618181233.80176fck3bdyi680>