From owner-freebsd-stable@FreeBSD.ORG Tue Jun 16 17:27:51 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD6EC1065712 for ; Tue, 16 Jun 2009 17:27:51 +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 7E3AD8FC14 for ; Tue, 16 Jun 2009 17:27:51 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 2F33646B82; Tue, 16 Jun 2009 13:27:51 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 2DDB48A072; Tue, 16 Jun 2009 13:27:50 -0400 (EDT) From: John Baldwin To: pluknet Date: Tue, 16 Jun 2009 13:14:56 -0400 User-Agent: KMail/1.9.7 References: <200906160830.29721.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200906161314.56449.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Tue, 16 Jun 2009 13:27:50 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-stable@freebsd.org Subject: Re: 6.2 sporadically locks up X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jun 2009 17:27:52 -0000 On Tuesday 16 June 2009 11:03:34 am pluknet wrote: > 2009/6/16 John Baldwin : > As for allpcpu, I often see the picture, when one CPU runs the "irq17: > bce1 aacu0" thread > and another one runs arcconf. I wonder if that might be a source of > bad locking or races, or.. > The arcconf utility uses ioctl that goes into aac/aacu(4) internals. I wondered about that. I would ask emaste@ as he has worked with arcconf. = I do think he has mentioned problems with arcconf locking up aac(4) controlle= rs in the past. > > Perhaps DDB in 6.2 doesn't know to > > look in stoppcbs[]. =A0Hmm, looks like 6.2 only does that if you are us= ing > > KDB_STOP_NMI. =A0Are you using that kernel option? =A0If not, you proba= bly want > > to. >=20 > No, I'm not. Will that add an additional visible overhead on a running sy= stem? No, it actually allows the kernel to more reliably stop other CPUs during a panic, etc. It's enabled in GENERIC as 'STOP_NMI' in 7.0 and later. =2D-=20 John Baldwin