From owner-freebsd-current@FreeBSD.ORG  Mon Jun 28 13:12:58 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 B63DB16A4CE; Mon, 28 Jun 2004 13:12:58 +0000 (GMT)
Received: from mail.sandvine.com (sandvine.com [199.243.201.138])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id A898843D2D; Mon, 28 Jun 2004 13:12:57 +0000 (GMT)
	(envelope-from don@sandvine.com)
Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72)
	id <MTR29J38>; Mon, 28 Jun 2004 09:12:56 -0400
Message-ID: <FE045D4D9F7AED4CBFF1B3B813C85337051D9102@mail.sandvine.com>
From: Don Bowman <don@sandvine.com>
To: 'John Baldwin' <jhb@FreeBSD.org>,
	Gerrit Nagelhout <gnagelhout@sandvine.com>
Date: Mon, 28 Jun 2004 09:12:47 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
cc: kris@FreeBSD.org
cc: freebsd-current@FreeBSD.org
cc: Julian Elischer <julian@elischer.org>
Subject: RE: STI, HLT in acpi_cpu_idle_c1
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: Mon, 28 Jun 2004 13:12:58 -0000

From: John Baldwin [mailto:jhb@FreeBSD.org]
> On Friday 25 June 2004 05:05 pm, Gerrit Nagelhout wrote:
> > John Baldwin wrote:
> > > Odd, all it does is eoi fast interrupts earlier.  Oh, there's
> > > a bug. :(  In
> > > the second hunk, change 'pic_disable_source' to 
> 'pic_enable_source'.
> >
> > sigh...it just locked up again.  I have included the current apic
> > dump for completeness.  Is there anything other information that
> > would be useful to debug this problem?
> 
> Hmm, it appears it is consistently CPU1 that thinks that 
> IPI_HARDCLOCK is not 
> being EOI'd.  Can you try swapping the CPUs and see if the 
> lockup moves from 
> CPU1 to CPU3?

There is more than one device that does this, so
its probably not worth it (its a huge huge effort
on these systems due to the way the heatsink
is bonded on: it requires breaking the heatsink
glue with a heat gun, disassembling the motherboard,
etc).