Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Dec 2009 13:59:42 +0100
From:      Jakob Breivik Grimstveit <jakob@grimstveit.no>
To:        Bernt Hansson <bernt@bah.homeip.net>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: fbsd8.0: Fatal trap 9: general protection fault while in kernel mode
Message-ID:  <40a50a8c0912110459w2eff38c1ue92edfcff621ba00@mail.gmail.com>
In-Reply-To: <4B1AE7D2.7050105@bah.homeip.net>
References:  <40a50a8c0912051116v68c97228vf363bfab3af1cf7d@mail.gmail.com>  <4B1AE7D2.7050105@bah.homeip.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Dec 6, 2009 at 00:08, Bernt Hansson <bernt@bah.homeip.net> wrote:

> Jakob Breivik Grimstveit said the following on 2009-12-05 20:16:
>>
>> I have - after having upgraded from 7.2 to 8.0, started experiencing
>> system unstability, with crashes about every 12-24h. Last time my
>> system crashed, I got the following screen output:
>>
>> Fatal trap 9: general protection fault while in kernel mode
>> couid =3D 0; apic id =3D 00
>> instruction pointer =A0 =A0=3D 0x20:0xffffffff804eb471
>> stack pointer =A0 =A0 =A0 =A0 =A0=3D 0x28:0xffffff803e933a50
>> frame pointer =A0 =A0 =A0 =A0 =A0=3D 0x28:0xffffff803e933a70
>> code segment =A0 =A0 =A0 =A0 =A0 =3D base 0x0, limit 0xfffff, type 0x1b
>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =3D DPL 0, pres 1, long 1, d=
ef32 0, gan 1
>> processor eflags =A0 =A0 =A0 =3D interrupt enabled, resume, IOPL =3D 0
>> current process =A0 =A0 =A0 =A0=3D 3208 (httpd)
>> trap number =A0 =A0 =A0 =A0 =A0 =A0=3D 9
>> panic: general protection fault
>> cpuid =3D 0
>> Uptime: 12h19m9s
>> Cannot dump. Device not defined or unavailable
>> Automatic reboot in 15 seconds - press a key on the console to abort
>>
>>
>> (Typed in manually while reading screen).
>>
>> What might be the problem? How can I resolve this?
>>
>> Thanks in advance!
>
> How old is the motherboard. Check the capacitors on the MB and PSU.

The motherboard is probably 2-3 years old, but this problem occured
when upgrading from 7.2 to 8.0, and has happened several times the
last week. Why should this be a hardware problem?

--=20
Vyrdsamt,
   Jakob Breivik Grimstveit | +47 4829 8152
   http://grimstveit.no/jakob | http://www.google.com/profiles/jakobbg



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40a50a8c0912110459w2eff38c1ue92edfcff621ba00>