Date: Fri, 06 Jul 2012 00:21:36 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: 10.0-CURRENT: kernel: Fatal trap 12: page fault while in kernel mode Message-ID: <4FF61370.4000200@zedat.fu-berlin.de> In-Reply-To: <201207051727.59295.jhb@freebsd.org> References: <4FF28682.9020705@zedat.fu-berlin.de> <201207051727.59295.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig547646070B1645203D695045 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable On 07/05/12 23:27, John Baldwin wrote: > On Tuesday, July 03, 2012 1:43:30 am O. Hartmann wrote: >> The most recent build of FreeBSD 10.0-CURRENT crashes on one of our >> boxes with recent Intel hardware, see dmesg extract below. FreeBSD doe= s >> obviously only crash on hardware with modern "Sandy-Bridge" hardware, >> the very same kernel config and a very similar setup does work very we= ll >> on an older Intel Core2Dua architecture. >> >> Machine in question runs an older kernel (set via nextboot -k >> kernel.old) very well: >> FreeBSD 10.0-CURRENT #0 r237697: Thu Jun 28 11:45:08 CEST 2012 >> >> Most recent buildworls/kernels crash after going into multiuser mode >> (/etc/rc-scripts getting executed). Below the kernel trap message. >> >> I do this report on the fly, so if there is need for deeper >> investigations let me know, I will provide necessary detail requested.= >=20 > We would need a stack trace to debug this further. Do you have a crash= dump? >=20 Well, I built a GENERIC kernel and bootet that, it also crashes, but I didn't find any coredump (as found in the crashes with the custom kernel). I was able to do a backtrace with the GENERIC kernel, but incapable of saving the trace - I did this in a rush, sorry. I went back, just on a hunch, to FreeBSD 10.0-CURRENT #1 r237000, which works, but this isn't the last working revision. I will look tomorrow for how to generate a dump or backtrace and save that somehow (if available in the handbook). Otherwise, if not not much efford, I would appreciate any hint (for the impatient) how to generate suiatbel debug informations. Regards, Oliver --------------enig547646070B1645203D695045 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBAgAGBQJP9hN5AAoJEOgBcD7A/5N81RsH/077oPhzRvG0R6ilzJkm7O2m w5s7x+HaOrj4uZ+BsV0hmAwsEQVCDJCleFMDbcA9IkVDRRYDouhQn88C7CmiYcf/ paKSwgCChajCAPx4GuKSQermESaczqviY7bvzc/vVha272LsHcfYGa3GVlSgGJ5+ sGGBmDMQL7YgWPNngZwfCFpnFQeYcgNQmqkpOajihnP/Eq6Veb/Iuad6YE+2R50W UOFWfYRrwt0uLozdTB5IwO3P2U8DKJF6zmCWf6+1bYBefRaqR3dAWsVhIvwzomkK Pf0nzAPPyWvOa0F5oP1JbYZ29nZktRqxaUXp1mn+dDEAyGGgb7vz/XPQqVR7P3Y= =i3+5 -----END PGP SIGNATURE----- --------------enig547646070B1645203D695045--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FF61370.4000200>