From owner-freebsd-current@FreeBSD.ORG  Thu Jun 17 21:09:30 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 5EE6616A4CE
	for <current@freebsd.org>; Thu, 17 Jun 2004 21:09:30 +0000 (GMT)
Received: from mail.sandvine.com (sandvine.com [199.243.201.138])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D1E6143D45
	for <current@freebsd.org>; Thu, 17 Jun 2004 21:09:29 +0000 (GMT)
	(envelope-from don@sandvine.com)
Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72)
	id <MTR28QT4>; Thu, 17 Jun 2004 16:52:57 -0400
Message-ID: <FE045D4D9F7AED4CBFF1B3B813C85337051D9018@mail.sandvine.com>
From: Don Bowman <don@sandvine.com>
To: 'Matthew Dillon' <dillon@apollo.backplane.com>,
	Don Bowman <don@sandvine.com>
Date: Thu, 17 Jun 2004 16:52:56 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
cc: Julian Elischer <julian@elischer.org>
cc: "'current@freebsd.org'" <current@freebsd.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: Thu, 17 Jun 2004 21:09:30 -0000

From: Matthew Dillon [mailto:dillon@apollo.backplane.com]
>     It is unlikely that the emulator is at fault, though I 
> suppose it is
>     a possibility.   It is more likely that there are simply no normal
>     interrupts being made pending and so your HLT is never waking up.
> 
>     If inserting a NOP makes things magically work, then the 
> emulator is
>     broken and needs to be fixed.  You can't have a NOP in 
> there for real
>     because you blow up the interlock.

I only have the emulator on there because of the bug,
not the other way around :)
The boards without the emulator are the ones that hang,
that's why i dragged it out.
I am definitely generating other interrupts
(e.g. serial, trying to drop into db, hardclock), but
all for naught. If I generate an NMI, it hangs
sending the stop ipi to the other processors, so
they don't receive that either. The core that i then
generate shows them in 'hlt'.

I'm wondering about some of the specification updates
for the Xeon, e.g. P72 of 
http://developer.intel.com/design/Xeon/specupdt/24967839.pdf
seems kind of esoteric, but...

--don