From owner-freebsd-current@FreeBSD.ORG  Sat Jul 17 22:53:13 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id D640816A4CE; Sat, 17 Jul 2004 22:53:13 +0000 (GMT)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id A73C343D46; Sat, 17 Jul 2004 22:53:13 +0000 (GMT)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id 831F272DF4; Sat, 17 Jul 2004 15:53:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP
	id 8088372DF2; Sat, 17 Jul 2004 15:53:13 -0700 (PDT)
Date: Sat, 17 Jul 2004 15:53:13 -0700 (PDT)
From: Doug White <dwhite@gumbysoft.com>
To: Kris Kennaway <kris@obsecurity.org>
In-Reply-To: <20040717195632.GA67466@xor.obsecurity.org>
Message-ID: <20040717154952.U41727@carver.gumbysoft.com>
References: <20040717103509.N24726@alpha.siliconlandmark.com>
	<20040717181026.GA63963@xor.obsecurity.org>
	<20040717195632.GA67466@xor.obsecurity.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: "current@freebsd.org" <current@freebsd.org>
Subject: Re: panic: APIC: Previous IPI is stuck
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
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: Sat, 17 Jul 2004 22:53:13 -0000

On Sat, 17 Jul 2004, Kris Kennaway wrote:

> > Does it only happen with a constant $NCPU+ load average?  I have never
> > seen it here.
>
> Yeah, it's usually a pretty busy machine.  It does a lot of
> buildworlds, nfs, concurrent www serving and ssh dispatching.

I triggered one of these last weekend, too.  Peter mentioned something to
me about it being caused by both CPUs IPIng at once and there no deadlock
avoidance in that case.  It died for me in installworld, though, which
made for a messy fixup job.

I guess our work on getting the kernel free-running is uncovering all
sorts of fun issues.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org