Date: Sat, 8 Feb 1997 12:57:52 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: dwhite@resnet.uoregon.edu (Doug White) Cc: hackers@FreeBSD.ORG Subject: Re: ASUS MB panics Message-ID: <Mutt.19970208125752.j@uriah.heep.sax.de> In-Reply-To: <Pine.BSI.3.94.970207095809.229F-100000@localhost>; from Doug White on Feb 7, 1997 17:30:30 -0800 References: <Pine.BSI.3.94.970207095809.229F-100000@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
As Doug White wrote: > I've been having a heck of a time getting an ASUS P/I P55T2P4 motherboard > working with my custom 2.2 kernels. Just for the record, this board works fine for me. > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x8:0x0 > stack pointer = 0x10:0xefbffe2c > frame pointer = 0x10:0xefbffe84 > 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 = 5 (sh) > interrupt mask = net tty > panic: page fault Umm. It executes a null pointer. This is hard to track offline. Can you configure DDB, and try to look at the stack to learn where it happens? (You could also configure remote gdb, but don't ask me for a documentation of this.) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19970208125752.j>