Date: Thu, 24 May 2007 12:08:39 -0400 From: Joe Marcus Clarke <marcus@marcuscom.com> To: attilio@FreeBSD.org Cc: Jeff Roberson <jroberson@chesapeake.net>, jeff@FreeBSD.org, Current@FreeBSD.org Subject: Re: Panic on -CURRENT after LDT changes Message-ID: <1180022919.10757.24.camel@shumai.marcuscom.com> In-Reply-To: <4655D5C1.2010905@FreeBSD.org> References: <1179962663.75721.6.camel@shumai.marcuscom.com> <20070523165051.G9443@10.0.0.1> <4655D5C1.2010905@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Thu, 2007-05-24 at 20:13 +0200, Attilio Rao wrote: > Jeff Roberson wrote: > > Thanks, Attilio and I will look at this right away. > > > > Jeff > > > > On Wed, 23 May 2007, Joe Marcus Clarke wrote: > > > >> On a -CURRENT build today with Jeff's LDT locking changes, I get an > >> instant, reproducible panic by doing: > >> > >> # cd /usr/src > >> # make -DNO_CLEAN buildworld > >> > >> Backing out the LDT changes to /sys/i386/i386/*machdep* corrects the > >> problem. Here is a dmesg and backtrace. In frame 6, it appears mdp is > >> NULL (i.e. td->td_proc->p_md = 0x0). > > Did you enable WITNESS/INVARIANTS/INVARIANT_SUPPORT? No, this kernel does not have WITNESS or INVARIANTS. I can enable those tomorrow if that would give you more useful information. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBGVbiGb2iPiv4Uz4cRAgD5AJ4uNUyu/YH4RanCW1txiglYK9UaEwCgkj8f kxfujJI9KdDihBoIXp0HwZg= =3Qov -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1180022919.10757.24.camel>