Date: Sun, 15 Feb 1998 14:58:59 +1030 From: Greg Lehey <grog@lemis.com> To: "Arthur P. Pesa" <apesa@bellsouth.net>, Hackers@FreeBSD.ORG Subject: Re: panic: general protection fault (one long line) Message-ID: <19980215145859.56665@freebie.lemis.com> In-Reply-To: <34E6661B.A5778FBA@bellsouth.net>; from Arthur P. Pesa on Sat, Feb 14, 1998 at 10:50:55PM -0500 References: <34E6661B.A5778FBA@bellsouth.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 14 February 1998 at 22:50:55 -0500, Arthur P. Pesa wrote: > I apologize for the dispicably formatted email. You're right, I probably > would tend to ignore it as well. I obviously did not intend my question > to be posed as a "one liner", and was unaware it appeared as such. I > will refrain from using the offending email software. I think you can probably fix it. And Netscape can misbehave too :-) > However my question remains: > On Sat, 14 February 1998 at 13:24:43 -0500, Arthur P. Pesa wrote: >> Hello, I have been encountering the following panic for several > months. I have been running this particular machine since June '97 on > 2.2.2-Release. I initially got a similar Fatal trap 12 during the > install, the workaround was to disable cpu caching in the bios during > the install, then go back afterwards and re-enable. For the last several > months I have become more dedicated to configuring this machine as my > time frees up. I have changed out the memory in hopes it was a corrupt > Simm, no luck. The Mo. Board is an Octek Hippo with an Intel Overdrive > Cpu, it originally had an Intel 486 dx 4 /100. I seemed to get the same > panic with either CPU. It has a Promise IDE controller with 2 ide > drives, 1.6G and 540 MB seagate. It also has a 3Com 3C509 III ethernet > card, I do remember seeing that the ep0 interface was buggy? A lot of people say that, but I've been using the driver for 2½ years now, and I haven't had any problems. > I beleive that was on www.freebsd.com. I do not have another > ethernet card swap at the moment. Following what is logged after the > core dump: > >> Fatal trap 12: page fault while in kernel mode >> fault virtual address = 0x10 >> instruction pointer = 0x8:0xf012e2e6 >> stack pointer = 0x10:0xf01d5ea4 >> frame pointer = 0x10:0xf01d5eb4 >> syncing disks... >> >> Fatal trap 12: page fault while in kernel mode >> fault virtual address = 0x10 >> fault code = supervisor read, page not present >> instruction pointer = 0x8:0xf012e2e6 >> stack pointer = 0x10:0xf01d5e70 >> frame pointer = 0x10:0xf01d5e80 >> 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 = Idle >> interrupt mask = >> panic: page fault >> Fatal trap 9: general protection fault while in kernel mode >> instruction pointer = 0x8:0xf01afe35 >> stack pointer = 0x10:0xf01d6000 >> frame pointer = 0x10:0x0 >> panic: general protection fault >> stack pointer = 0x10:0xf01d5ea4 >> frame pointer = 0x10:0xf01d5eb4 >> syncing disks... done Do these all come at once? That's unusual. Anyway, what we need here is a dump to look at. Do you have one? Is the machine set up for one? If not, set it up and see if the dump will happen then. It would also help if you have a debug kernel. See http://www.freebsd.org/handbook/handbook264.html#599for further details. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980215145859.56665>