From owner-freebsd-current@FreeBSD.ORG  Wed Nov 17 22:41:23 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 E7BC11065674
	for <freebsd-current@freebsd.org>; Wed, 17 Nov 2010 22:41:23 +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 C38468FC12
	for <freebsd-current@freebsd.org>; Wed, 17 Nov 2010 22:41:23 +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 oAHMfNmK006531;
	Wed, 17 Nov 2010 14:41:23 -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:41:03 -0800
Message-ID: <B583FBF374231F4A89607B4D08578A430883C826@bcs-mail03.internal.cacheflow.com>
In-Reply-To: <20101117222909.GY2392@deviant.kiev.zoral.com.ua>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: immediate panic in vm
Thread-Index: AcuGpt6HCWdF2BucSnmTV5i94ri7IwAAXQmg
References: <B583FBF374231F4A89607B4D08578A43087AD856@bcs-mail03.internal.cacheflow.com>
	<201011171704.03157.jhb@freebsd.org> <4CE4540C.9050409@FreeBSD.org>
	<20101117222909.GY2392@deviant.kiev.zoral.com.ua>
From: "Li, Qing" <qing.li@bluecoat.com>
To: "Kostik Belousov" <kostikbel@gmail.com>, "Dimitry Andric" <dim@freebsd.org>
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Nov 2010 22:41:24 -0000

Building kernel on 8.1-RELEASE should not require a buildworld, right ?

Or there have been changes committed since that would mandate a
buildworld?

-- Qing


> -----Original Message-----
> From: Kostik Belousov [mailto:kostikbel@gmail.com]
> Sent: Wednesday, November 17, 2010 2:29 PM
> To: Dimitry Andric
> Cc: John Baldwin; Li, Qing; freebsd-current@freebsd.org
> Subject: Re: immediate panic in vm
>=20
> On Wed, Nov 17, 2010 at 11:15:40PM +0100, Dimitry Andric wrote:
> > 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.
> >
> > That is indeed possible; Qing, can you please try to revert r215212,
> and
> > see if that fixes it?
> I suggest to see how old is the world where buildkernel was done ?
> In particular, the thing to check is whether the ld(1) used to link
> the kernel contains r210245.