From vd@v5d.org  Tue May  8 09:10:52 2007
Return-Path: <vd@v5d.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 4DB0A16A400;
	Tue,  8 May 2007 09:10:52 +0000 (UTC)
	(envelope-from vd@v5d.org)
Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40])
	by mx1.freebsd.org (Postfix) with ESMTP id 3FBFD13C44C;
	Tue,  8 May 2007 09:10:52 +0000 (UTC)
	(envelope-from vd@v5d.org)
Received: from mail.v5d.org (root@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l489Apgh063675;
	Tue, 8 May 2007 09:10:52 GMT
	(envelope-from vd@v5d.org)
Received: by mail.v5d.org (Postfix, from userid 1002)
	id 4F4DF413F; Tue,  8 May 2007 12:10:55 +0300 (EEST)
Message-Id: <20070508091055.GA97654@polejan.hw.v5d.org>
Date: Tue, 8 May 2007 12:10:55 +0300
From: Vasil Dimov <vd@freebsd.org>
Reply-To: vd@freebsd.org
To: FreeBSD-gnats-submit@freebsd.org
Subject: regression: "panic: blockabe sleep lock" @ boot after upgrade
	-CURRENT SMP amd64
X-Send-Pr-Version: 3.113

>Number:         112518
>Category:       kern
>Synopsis:       regression: "panic: blockabe sleep lock" @ boot after upgrade -CURRENT SMP amd64
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    jhb
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue May 08 09:20:05 GMT 2007
>Closed-Date:    Thu May 10 15:07:35 GMT 2007
>Last-Modified:  Thu May 10 15:07:35 GMT 2007
>Originator:     Vasil Dimov
>Release:        FreeBSD 7.0-CURRENT amd64
>Organization:
N/A
>Environment:

FreeBSD 7.0-CURRENT as of May 7 2007, Intel Centrino Duo (amd64).

Dell Latitude D620 laptop

>Description:

After upgrading my 7.0-CURRENT system (which was from early March 2007)
to the latest as of May 7 2007 I get a kernel panic during boot:

...
acd0: DVDR <SONY DVD+/-RW DW-Q58A/UDS2> at ata1-master UDMA33
SMP: AP CPU #1 Launched!
panic: blockable sleep lock (sx) msi @ /usr/src/sys/amd64/amd64/msi.c:374
cpuid = 1
KDB: enter: panic
[thread pid 0 tid 0 ]
Stopped at      kdb_enter+0x2f: nop
db> bt
Tracing pid 0 tid 0 td 0xffffffff8099dda0
kdb_enter() at kdb_enter+0x2f
panic() at panic+0x225
witness_checkorder() at witness_checkorder+0x5db
_sx_slock() at _sx_slock+0x3a
msi_map() at msi_map+0x34
pci_remap_msi_irq at pci_remap_msi_irq+0x203
intr_assign_next_cpu() at intr_assign_next_cpu+0x18
intr_shuffle_irqs at intr_shuffle_irqs+0x68
mi_startup() at mi_startup+0xd3
btext() at btext+0x2c
db>

After disabling "Multi Core Support" from the BIOS, the system boots
just fine:

...
acd0: DVDR <SONY DVD+/-RW DW-Q58A/UDS2> at ata1-master UDMA33
pcm0: <HDA Codec: Sigmatel STAC9220>
pcm0: <HDA Driver Revision: 20070505_0044>
GEOM_JOURNAL: Journal 1215844039: ad0s3a contains journal.
...

>How-To-Repeat:

Just boot, but probably this is HW specific.

>Fix:

N/A

-- 
Vasil Dimov
moc.elcaro@vomid.lisav        Software Developer @ Oracle/Innobase Oy
gro.DSBeerF@dv                Committer @ FreeBSD.org
gro.d5v@dv                    Home @ Sofia, Bulgaria
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->jhb 
Responsible-Changed-By: vd 
Responsible-Changed-When: Thu May 10 05:27:18 UTC 2007 
Responsible-Changed-Why:  
Assign to John, looks like he played with sys/amd64/amd64/msi.c recently. 
John, do you think that the changes in 1.6 may have fixed this issue? 
Especially this one: 

- Change the MSI sx lock to a mutex.  If we need to create new sources, 
drop the lock, create the required number of sources, then get the lock 
and try the allocation again. 


http://www.freebsd.org/cgi/query-pr.cgi?pr=112518 
State-Changed-From-To: open->closed 
State-Changed-By: jhb 
State-Changed-When: Thu May 10 15:07:10 UTC 2007 
State-Changed-Why:  
Yes, this LOR was fixed by the subsequent commit. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=112518 
>Unformatted:
