Date: Sat, 14 Jun 2008 07:28:28 +0100 From: Bruce Cran <bruce@cran.org.uk> To: Ryan Coleman <ryan.coleman@cwis.biz> Cc: freebsd-questions@freebsd.org Subject: Re: Intermittent -- yet regular -- v6.3 kernel panic Message-ID: <20080614072828.318d0e7c@tau> In-Reply-To: <48536407.2040402@cwis.biz> References: <4852CF49.2000304@cwis.biz> <20080613215908.25d71e6e@tau> <4852FED0.2010805@FreeBSD.org> <48534D08.2050809@cwis.biz> <48536407.2040402@cwis.biz>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/2FNw6Mwbipk5vSCr7jvutxN Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 14 Jun 2008 01:24:07 -0500 Ryan Coleman <ryan.coleman@cwis.biz> wrote: > Ryan Coleman wrote: > > Kris Kennaway wrote: > >> Bruce Cran wrote: > >>> On Fri, 13 Jun 2008 14:49:29 -0500 > >>> Ryan Coleman <ryan.coleman@cwis.biz> wrote: > >>> > >>>> Jun 12 23:02:41 UnixBox2 kernel: Fatal trap 12: page fault while > >>>> in kernel mode > >>>> Jun 12 23:02:41 UnixBox2 kernel: cpuid =3D 1; apic id =3D 01 > >>>> Jun 12 23:02:41 UnixBox2 kernel: fault virtual address =3D 0x0 > >>>> Jun 12 23:02:41 UnixBox2 kernel: fault code =3D=20 > >>>> supervisor read, page not present > >>>> Jun 12 23:02:41 UnixBox2 kernel: instruction pointer =3D > >>>> 0x20:0x0 Jun 12 23:02:41 UnixBox2 kernel: stack pointer > >>>> =3D 0x28:0xec0ea8e0 Jun 12 23:02:41 UnixBox2 kernel: frame > >>>> pointer =3D 0x28:0xec0ea8e4 Jun 12 23:02:41 UnixBox2 > >>>> kernel: code segment =3D base 0x0, limit 0xfffff, type > >>>> 0x1b Jun 12 23:02:41 UnixBox2 kernel: =3D DPL 0, pres 1, def32 1, > >>>> gran 1 Jun 12 23:02:41 UnixBox2 kernel: processor eflags =3D > >>>> interrupt enabled, resume, IOPL =3D 0 > >>>> Jun 12 23:02:41 UnixBox2 kernel: current process =3D 925 > >>>> (cp) Jun 12 23:02:41 UnixBox2 kernel: trap number =3D 12 > >>>> Jun 12 23:02:41 UnixBox2 kernel: panic: page fault > >>>> Jun 12 23:02:41 UnixBox2 kernel: cpuid =3D 1 > >>>> Jun 12 23:02:41 UnixBox2 kernel: Uptime: 1h21m59s > >>>> Jun 12 23:02:41 UnixBox2 kernel: Cannot dump. No dump device > >>>> defined. > >>>> > >>>> > >>>> This is a regular occurrence, but varies by source. Brand new > >>>> fBSD 6.3 machine, what more information do I need to provide? > >>> > >>> To be of any use we need a backtrace. See=20 > >>> http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.h= tml=20 > >>> > >>> for details. First you need to configure a dump device then when > >>> the system crashes a crash dump will be written to /var/crash by > >>> default. You then run kgdb on the file to get the backtrace. > >>> > >> > >> It's quite likely to be due to bad hardware though. > >> > >> Kris > >> > > > > It's crashed twice and stalled on the dump. Any thoughts? >=20 > Anyone? I'm going to have to disable the dump as I need the machine > to come back up if possible. Since it sounds like it's bad hardware, the dump isn't going to provide any useful information so you may as well disable it until you can swap out the RAM etc. --=20 Bruce Cran --Sig_/2FNw6Mwbipk5vSCr7jvutxN Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIU2UQn4uvqcJsLfgRAtDgAJ43TenQ15Wvo84QCaj9Rgcd9zE5fACfXANd 0HCil4SqmmCOQTVIcot7BjU= =7N57 -----END PGP SIGNATURE----- --Sig_/2FNw6Mwbipk5vSCr7jvutxN--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080614072828.318d0e7c>