Date: Wed, 17 Nov 2010 17:04:03 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: "Li, Qing" <qing.li@bluecoat.com>, dim@freebsd.org Subject: Re: immediate panic in vm Message-ID: <201011171704.03157.jhb@freebsd.org> In-Reply-To: <B583FBF374231F4A89607B4D08578A43087AD856@bcs-mail03.internal.cacheflow.com> References: <B583FBF374231F4A89607B4D08578A43087AD856@bcs-mail03.internal.cacheflow.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, November 17, 2010 2:56:28 pm Li, Qing wrote: > The latest -current panics immediately on start-up. > Running -current in VMware, I get: > > <snip> > ... > panic: mtx_init: mtx_lock not aligned for netir_mtx: 0xffffffff8114791c > ... > <snip> > > Has anyone else seen this? Any pointers ? I'm guessing the recent changes to how the VNET stuff works have broken the alignment of DPCPU and VNET structures again. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201011171704.03157.jhb>