From owner-freebsd-current@FreeBSD.ORG  Thu Jun 24 14:36:33 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 DFD8116A4CE; Thu, 24 Jun 2004 14:36:33 +0000 (GMT)
Received: from mail.sandvine.com (sandvine.com [199.243.201.138])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 0FD7143D39; Thu, 24 Jun 2004 14:36:33 +0000 (GMT)
	(envelope-from gnagelhout@sandvine.com)
Received: by mail.sandvine.com with Internet Mail Service (5.5.2657.72)
	id <MTR29A7T>; Thu, 24 Jun 2004 10:36:06 -0400
Message-ID: <FE045D4D9F7AED4CBFF1B3B813C85337054EC4BB@mail.sandvine.com>
From: Gerrit Nagelhout <gnagelhout@sandvine.com>
To: 'John Baldwin' <jhb@FreeBSD.org>, freebsd-current@FreeBSD.org
Date: Thu, 24 Jun 2004 10:36:04 -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: Gerrit Nagelhout <gnagelhout@sandvine.com>
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: Thu, 24 Jun 2004 14:36:34 -0000

Here's some information about another slightly different 
lockup.  CPU0 is blocked in smp_targeted_tlb_shootdown (vector 0xf5).
CPU2 & 3 are in acpi_cpu_c1.  CPU1 (again) is in acpi_cpu_c1,
but it has an interrupt pending.  In this case, the pending
interrupt is bit 27.  224 + 27 = 251 = IPI_HARDCLOCK.
How can I figure out how CPU1 got stuck in this state?  As
far as I can tell, there is either a h/w problem, or CPU1
has gone to sleep after starting to handle an interrupt.
Thanks,

Gerrit

P0>dumpAllLocalApic
CPU 0
ID:    0x6000000 
TPR:   0x0 
PPR:   0x0 
icr_lo:0xf5 
APR:   0x0 
ISR0:  0x0 
ISR1:  0x0 
ISR2:  0x0 
ISR3:  0x0 
ISR4:  0x0 
ISR5:  0x0 
ISR6:  0x0 
ISR7:  0x0 
IRR0:  0x0 
IRR1:  0x0 
IRR2:  0x0 
IRR3:  0x0 
IRR4:  0x0 
IRR5:  0x0 
IRR6:  0x0 
IRR7:  0x18000000 
TMR0:  0x0 
TMR1:  0x0 
TMR2:  0x0 
TMR3:  0x0 
TMR4:  0x0 
TMR5:  0x0 
TMR6:  0x0 
TMR7:  0x0 
CPU 1
ID:    0x7000000 
TPR:   0x0 
PPR:   0xf0 
icr_lo:0xf3 
APR:   0x0 
ISR0:  0x0 
ISR1:  0x0 
ISR2:  0x0 
ISR3:  0x0 
ISR4:  0x0 
ISR5:  0x0 
ISR6:  0x0 
ISR7:  0x8000000 
IRR0:  0x0 
IRR1:  0x0 
IRR2:  0x0 
IRR3:  0x0 
IRR4:  0x0 
IRR5:  0x0 
IRR6:  0x0 
IRR7:  0x18200000 
TMR0:  0x0 
TMR1:  0x0 
TMR2:  0x0 
TMR3:  0x0 
TMR4:  0x0 
TMR5:  0x0 
TMR6:  0x0 
TMR7:  0x0 
CPU 2
ID:    0x0 
TPR:   0x0 
PPR:   0x0 
icr_lo:0xfb 
APR:   0x0 
ISR0:  0x0 
ISR1:  0x0 
ISR2:  0x0 
ISR3:  0x0 
ISR4:  0x0 
ISR5:  0x0 
ISR6:  0x0 
ISR7:  0x0 
IRR0:  0x0 
IRR1:  0x1000000 
IRR2:  0x0 
IRR3:  0x0 
IRR4:  0x20000 
IRR5:  0x0 
IRR6:  0x0 
IRR7:  0x0 
TMR0:  0x0 
TMR1:  0x0 
TMR2:  0x1000 
TMR3:  0x0 
TMR4:  0x20000 
TMR5:  0x0 
TMR6:  0x0 
TMR7:  0x0 
CPU 3
ID:    0x1000000 
TPR:   0x0 
PPR:   0x0 
icr_lo:0xf3 
APR:   0x0 
ISR0:  0x0 
ISR1:  0x0 
ISR2:  0x0 
ISR3:  0x0 
ISR4:  0x0 
ISR5:  0x0 
ISR6:  0x0 
ISR7:  0x0 
IRR0:  0x0 
IRR1:  0x0 
IRR2:  0x0 
IRR3:  0x0 
IRR4:  0x0 
IRR5:  0x0 
IRR6:  0x0 
IRR7:  0x0 
TMR0:  0x0 
TMR1:  0x0 
TMR2:  0x0 
TMR3:  0x0 
TMR4:  0x0 
TMR5:  0x0 
TMR6:  0x0 
TMR7:  0x0 
P3>
P3>