Date: Wed, 17 Nov 2010 14:39:36 -0800 From: "Li, Qing" <qing.li@bluecoat.com> To: "Dimitry Andric" <dim@FreeBSD.org>, "John Baldwin" <jhb@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: RE: immediate panic in vm Message-ID: <B583FBF374231F4A89607B4D08578A430883C821@bcs-mail03.internal.cacheflow.com> In-Reply-To: <4CE4540C.9050409@FreeBSD.org> References: <B583FBF374231F4A89607B4D08578A43087AD856@bcs-mail03.internal.cacheflow.com> <201011171704.03157.jhb@freebsd.org> <4CE4540C.9050409@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I saw the panic before r215212. --Qing > -----Original Message----- > From: Dimitry Andric [mailto:dim@FreeBSD.org] > Sent: Wednesday, November 17, 2010 2:16 PM > To: John Baldwin > Cc: freebsd-current@FreeBSD.org; Li, Qing > Subject: Re: immediate panic in vm >=20 > On 2010-11-17 23:04, John Baldwin wrote: > > On Wednesday, November 17, 2010 2:56:28 pm Li, Qing wrote: > >> panic: mtx_init: mtx_lock not aligned for netir_mtx: > 0xffffffff8114791c > ... > > I'm guessing the recent changes to how the VNET stuff works have > broken the > > alignment of DPCPU and VNET structures again. >=20 > That is indeed possible; Qing, can you please try to revert r215212, > and > see if that fixes it?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B583FBF374231F4A89607B4D08578A430883C821>