From owner-freebsd-current@FreeBSD.ORG  Sat Jul 17 19:42:53 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 2D69116A4CE; Sat, 17 Jul 2004 19:42:53 +0000 (GMT)
Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com
	[209.69.98.4])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id DFF3643D5A; Sat, 17 Jul 2004 19:42:52 +0000 (GMT)
	(envelope-from andy@siliconlandmark.com)
Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1])
	i6HJgjkp067254;	Sat, 17 Jul 2004 15:42:45 -0400 (EDT)
	(envelope-from andy@siliconlandmark.com)
Received: from localhost (andy@localhost)i6HJgjOL067251;
	Sat, 17 Jul 2004 15:42:45 -0400 (EDT)
	(envelope-from andy@siliconlandmark.com)
X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing
	-bs
Date: Sat, 17 Jul 2004 15:42:45 -0400 (EDT)
From: Andre Guibert de Bruet <andy@siliconlandmark.com>
To: Brian Fundakowski Feldman <green@freebsd.org>
In-Reply-To: <20040717184240.GT1626@green.homeunix.org>
Message-ID: <20040717154040.P24726@alpha.siliconlandmark.com>
References: <20040717103509.N24726@alpha.siliconlandmark.com>
	<20040717181026.GA63963@xor.obsecurity.org>
	<20040717184240.GT1626@green.homeunix.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-MailScanner-Information: Please contact the ISP for more information
X-MailScanner: Found to be clean
cc: "current@freebsd.org" <current@freebsd.org>
cc: Kris Kennaway <kris@obsecurity.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 19:42:53 -0000


On Sat, 17 Jul 2004, Brian Fundakowski Feldman wrote:

> On Sat, Jul 17, 2004 at 11:10:26AM -0700, Kris Kennaway wrote:
>> On Sat, Jul 17, 2004 at 06:10:45PM +0200, Lars Erik Gullerud wrote:
>>> On Sat, 17 Jul 2004, Andre Guibert de Bruet wrote:
>>>
>>>> pmap_rltacziynftirx(:a 9sfp4u4nc 8f4o,r0 ,56040f0b0f0c0108
>>>> ,a9f44c80,8) at 0x606f31c5
>>> [snip]
>>>
>>>> I am a little worried by the line that starts with pmap_rltac. It appears
>>>> to be the output of two interleaved messages, which I have yet to make
>>>> sense of. At this point the machine is deadlocked and nothing short of a
>>>> reset will get it to budge.
>>>
>>> FYI, the two interleaved lines actually seem to be:
>>>
>>> rtcintr(a9f44c84,0,64fbfc18,a9f44c80,8) at 0x606f31c5
>>> pmap_lazyfix: spun for 50000000
>>>
>>> I seem to remember Kris Kennaway also having a couple of panics where
>>> pmap_lazyfix errors got interleaved with the output.
>>
>> Yeah, I've had to disable SMP because this panic happens too often.
>
> Does it only happen with a constant $NCPU+ load average?  I have never
> seen it here.

Can't really tell, as that was the first time I had ever seen that 
message. I upgraded kernels and am able to successfully build world 
on the same machine without any problems. Dare I try it with -j($NCPU+1)?

Andy

> Andre Guibert de Bruet | Enterprise Software Consultant >
> Silicon Landmark, LLC. | http://siliconlandmark.com/    >