Re: finally a crash dump on 5.3
On Thu, Jan 06, 2005 at 08:56:45AM -0600, J.D. Bronson wrote: > I was up for 2wks and today saw this: > > Fatal trap 12 - page fault while in kernel mode > CPUID 0 APIC ID 0 > Fault write address = 0x418ad66c > Fault code = supervisor write, page not present > > Inst Pointer = 0x8:0xc05109d9 > Stack Pointer = 0x10:0xe5ea8978 > Frame Pointer = 0x10:0xe5ea8994 > Code Segment base 0x0 limit 0x type 0x1b > DPL 0, PRES 1 def 32 1, gran 1 > > current process= 7673 (telnetd) > > -JEFF > ..I had thought this was SCSI, but I dont have any scsi drives installed > and was running on IDE. > > What do I do with this information now that I finally have it ? That's not a crashdump, that's a panic. Check the handbook for the steps required to enable crashdumping. Kris pgpmU1hJFZvjP.pgp Description: PGP signature
Re: finally a crash dump on 5.3
On 2005-01-06 09:44, "J.D. Bronson" <[EMAIL PROTECTED]> wrote: > At 09:32 AM 1/6/2005, Giorgos Keramidas wrote: > >On 2005-01-06 08:56, "J.D. Bronson" <[EMAIL PROTECTED]> wrote: > >> I was up for 2wks and today saw this: > >> > >> Fatal trap 12 - page fault while in kernel mode > >> CPUID 0 APIC ID 0 > >> Fault write address = 0x418ad66c > >> Fault code = supervisor write, page not present > >> > >> What do I do with this information now that I finally have it ? > > > > During the next boot, savecore should save a crash dump in > > /var/crash (assuming one was successfully saved in swap when the > > crash happened). > > > > Look at the Developers Handbook for details about obtaining a stack > > trace of the kernel at the moment of the crash: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-gdb.html > > Well so much for that idea :( > > 9:43:24am /var/crash> ls -al > total 6 > drwxr-x--- 2 root wheel 512 Dec 29 18:25 . > drwxr-xr-x 23 root wheel 512 Jan 6 09:37 .. > -rw-r--r-- 1 root wheel5 Nov 4 19:27 minfree Then you are still seeing crashes without a dump :-( - Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: finally a crash dump on 5.3
On Thu, 2005-01-06 at 09:44 -0600, J.D. Bronson wrote: > At 09:32 AM 1/6/2005, Giorgos Keramidas wrote: > >On 2005-01-06 08:56, "J.D. Bronson" <[EMAIL PROTECTED]> wrote: > > > I was up for 2wks and today saw this: > > > > > > Fatal trap 12 - page fault while in kernel mode > > > CPUID 0 APIC ID 0 > > > Fault write address = 0x418ad66c > > > Fault code = supervisor write, page not present > > > [...] > > > > > > What do I do with this information now that I finally have it ? > > > >During the next boot, savecore should save a crash dump in /var/crash > >(assuming one was successfully saved in swap when the crash happened). > > > >Look at the Developers Handbook for details about obtaining a stack > >trace of the kernel at the moment of the crash: > >http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-gdb.html > > > Well so much for that idea :( > > 9:43:24am /var/crash> ls -al > total 6 > drwxr-x--- 2 root wheel 512 Dec 29 18:25 . > drwxr-xr-x 23 root wheel 512 Jan 6 09:37 .. > -rw-r--r-- 1 root wheel5 Nov 4 19:27 minfree Call me old-fashioned, but I'd run memtest. Peter. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: finally a crash dump on 5.3
At 09:32 AM 1/6/2005, Giorgos Keramidas wrote: On 2005-01-06 08:56, "J.D. Bronson" <[EMAIL PROTECTED]> wrote: > I was up for 2wks and today saw this: > > Fatal trap 12 - page fault while in kernel mode > CPUID 0 APIC ID 0 > Fault write address = 0x418ad66c > Fault code = supervisor write, page not present > [...] > > What do I do with this information now that I finally have it ? During the next boot, savecore should save a crash dump in /var/crash (assuming one was successfully saved in swap when the crash happened). Look at the Developers Handbook for details about obtaining a stack trace of the kernel at the moment of the crash: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-gdb.html Well so much for that idea :( 9:43:24am /var/crash> ls -al total 6 drwxr-x--- 2 root wheel 512 Dec 29 18:25 . drwxr-xr-x 23 root wheel 512 Jan 6 09:37 .. -rw-r--r-- 1 root wheel5 Nov 4 19:27 minfree -- J.D. Bronson Aurora Health Care // Information Services // Milwaukee, WI USA Office: 414.978.8282 // Email: [EMAIL PROTECTED] // Pager: 414.314.8282 This message should contain confidential and/or privileged information, but it doesn't. If you are not the addressee or authorized to receive this for the addressee, go ahead, copy, disclose, or take any action based on this message or any information herein that you wish, what the heck! If you have received this message in error, please ask the sender what the heck they were thinking about. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: finally a crash dump on 5.3
On 2005-01-06 08:56, "J.D. Bronson" <[EMAIL PROTECTED]> wrote: > I was up for 2wks and today saw this: > > Fatal trap 12 - page fault while in kernel mode > CPUID 0 APIC ID 0 > Fault write address = 0x418ad66c > Fault code = supervisor write, page not present > [...] > > What do I do with this information now that I finally have it ? During the next boot, savecore should save a crash dump in /var/crash (assuming one was successfully saved in swap when the crash happened). Look at the Developers Handbook for details about obtaining a stack trace of the kernel at the moment of the crash: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-gdb.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
finally a crash dump on 5.3
I was up for 2wks and today saw this: Fatal trap 12 - page fault while in kernel mode CPUID 0 APIC ID 0 Fault write address = 0x418ad66c Fault code = supervisor write, page not present Inst Pointer = 0x8:0xc05109d9 Stack Pointer = 0x10:0xe5ea8978 Frame Pointer = 0x10:0xe5ea8994 Code Segment base 0x0 limit 0x type 0x1b DPL 0, PRES 1 def 32 1, gran 1 current process= 7673 (telnetd) -JEFF ..I had thought this was SCSI, but I dont have any scsi drives installed and was running on IDE. What do I do with this information now that I finally have it ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
