Date: Tue, 12 Apr 2005 15:32:50 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Erik N?rgaard <norgaard@locolomo.org> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Don't Panic - how do I investigate a kernel panic? Message-ID: <20050412223250.GA71285@xor.obsecurity.org> In-Reply-To: <425C3B46.3090006@locolomo.org> References: <425C3B46.3090006@locolomo.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 12, 2005 at 11:19:02PM +0200, Erik N?rgaard wrote: > Hi, >=20 > I have a 5.3-STABLE which was stable untill last friday. Since then I=20 > experience irregular panics, with uptimes between 25 secs and 16 hours. >=20 > In most cases I got a fatal trap 12, the last panic was simply "panic:=20 > sbdrop". >=20 > I had 5.3p5 but upgraded to 5.3p8 after the first panics. After the last= =20 > trap 12, I replaced my custom kernel with a fresh built GENERIC, as I=20 > thought it might be easier to investigate. >=20 > I have experienced trap 12 before startup completed and after shutdown=20 > unmounted all disks. So, it seems not to be triggered by network events. >=20 > However, about the same time as the first panic and since then, I have=20 > experienced an unusually high amount of ilicit mail delivery attempts to= =20 > adresses like <random_chars>@mydomain.com - not the amount I would=20 > expect could cause a crash though, my connection is far to thin for that. >=20 > Following the kernel panic faq: >=20 > Fatal trap 12: Page fault while in kernel mode > Fault virtual address =3D 0xc > Fault code =3D supervisor read, page not present > instruction pointer =3D 0x8:0xc053d638 > stack pointer =3D 0x10:0xcb4ddaec > frame pointer =3D 0x10:0xcb4ddaf8 > code segment =3D base 0x0, limit 0xffff, type 0x1b > =3D DPL 0, pres 1, def32 1, gran 1 > processor eflags =3D interrupt enabled, resume, IOPL=3D0 > current process =3D 28 (swi1:net) > trap number =3D 12 > panic: page fault >=20 > # nm -n /boot/kernel/kernel | grep c053d6 > c053d610 T m_copydata > c053d670 T m_dup >=20 > Note: This was the same error for both the custom p5 and p8 kernels. >=20 > The sbdrop panic happened with the GENERIC kernel. >=20 > What does sbdrop mean? Is this a simple disk I/O or hardware error? How= =20 > do I get on from here? Upgrade to 5.4, I believe this was fixed some time ago. If you still see it, then follow the directions in the developers' handbook about compiling your kernel with debugging symbols and obtaining a traceback. Kris --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCXEySWry0BWjoQKURAvulAKDuvvkscT+k2ymxYevw/B+D7lXIoACg1E2Z j22nIpahSvtTvavuTY58Bxs= =rTd9 -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050412223250.GA71285>