Date: Thu, 25 Mar 2004 09:29:10 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: chris <wacky@wacky.ws> Cc: freebsd-questions@freebsd.org Subject: Re: page fault error? Message-ID: <20040325092910.GA61612@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <20040324235720.GG37516@eclipse.wacky.ws> References: <20040324205903.GE37516@eclipse.wacky.ws> <20040324235720.GG37516@eclipse.wacky.ws>
next in thread | previous in thread | raw e-mail | index | archive | help
--M9NhX3UHpAaciwkO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Mar 24, 2004 at 06:57:20PM -0500, chris wrote:
> Hello, I am having the following problem. About a week or so ago this
> started. My box running 4.9-STABLE keeps panicing and rebooting, below
> is an output of dmesg -a. Also i have tried to replace the memory and
> the hard drive is only 5 months old or so. I have also cvsup'ed and ran =
=20
> make/
> buildworld and rebuilt my kernel. It doesnt appear to be overheating =20
> either.
> Any help would be greatly appreciated, thanks
This sort of panicing that starts at an arbitrary time and not
associated with some system change (new hardware, OS update) is almost
always due to a hardware fault. You've eliminated two of the most
probable causes: bad memory and overheating, but unfortunately
computers are complicated beasties and there's a lot more that can go
wrong than that. It could be as simple as your power supply fading
and not providing the required +5V and +12V within spec. Or it could
be that one or more of the chips on your motherboard, or indeed, your
CPU has developed a fault and is trashing data that passes through it.
The page fault error you're seeing is due to the kernel trying to
access a memory page which was never previously allocated. You can
get so idea about what is triggering the problem by setting your
system up to save a core image and looking at what the kernel was
doing immediately it paniced. Instructions for doing that are here:
http://www.oreillynet.com/pub/a/bsd/2002/03/21/Big_Scary_Daemons.html
http://www.oreillynet.com/pub/a/bsd/2002/04/04/Big_Scary_Daemons.html
Now, grovelling in the bowels of the kernel is quite a daunting task
for the uninitiated, but gathering this sort of information is
precisely what will be most helpful to a FreeBSD developer who does
know their way around the kernel. =20
=20
> (if anyone recieved this twice i apologize, i sent it earlier but it =20
> didnt appear to go through for some reason)
Yes -- occasionally the freebsd.org mailer takes an hour or two or
three to get a message out to the list, rather than the usual minute
or so. Sometimes even longer. As a rule of thumb, wait for at least
4 hours and preferably a day before re-sending.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--M9NhX3UHpAaciwkO
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFAYqZmdtESqEQa7a0RAnUNAJ98E/Nk6XwtYjvbirzn38JpkeLFAQCdF9s1
CLJKQjXkRrSFXQqUEOkgOjI=
=qjP2
-----END PGP SIGNATURE-----
--M9NhX3UHpAaciwkO--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040325092910.GA61612>