From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 22:04:11 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 7A472106564A; Wed, 17 Nov 2010 22:04:11 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 4C8DA8FC12; Wed, 17 Nov 2010 22:04:11 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id E1E4346B58; Wed, 17 Nov 2010 17:04:10 -0500 (EST) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id D99F48A009; Wed, 17 Nov 2010 17:04:09 -0500 (EST) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 17 Nov 2010 17:04:03 -0500 User-Agent: KMail/1.13.5 (FreeBSD/7.3-CBSD-20101102; KDE/4.4.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201011171704.03157.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Wed, 17 Nov 2010 17:04:10 -0500 (EST) X-Virus-Scanned: clamav-milter 0.96.3 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.9 required=4.2 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bigwig.baldwin.cx Cc: "Li, Qing" , dim@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:04:11 -0000 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: > > > ... > panic: mtx_init: mtx_lock not aligned for netir_mtx: 0xffffffff8114791c > ... > > > 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