From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 22:40:01 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 286E4106564A for ; Wed, 17 Nov 2010 22:40:01 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id 08D9C8FC13 for ; Wed, 17 Nov 2010 22:40:00 +0000 (UTC) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id oAHMe0ce006086; Wed, 17 Nov 2010 14:40:00 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 17 Nov 2010 14:39:36 -0800 Message-ID: In-Reply-To: <4CE4540C.9050409@FreeBSD.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: immediate panic in vm Thread-Index: AcuGpPlym9jAZXNnQXiSS3Vz97k2MAAA0z/w References: <201011171704.03157.jhb@freebsd.org> <4CE4540C.9050409@FreeBSD.org> From: "Li, Qing" To: "Dimitry Andric" , "John Baldwin" Cc: freebsd-current@FreeBSD.org Subject: RE: immediate panic in vm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2010 22:40:01 -0000 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?