From owner-freebsd-bugs@FreeBSD.ORG  Thu May 10 05:34:34 2007
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
X-Original-To: freebsd-bugs@hub.freebsd.org
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 71C2D16A400;
	Thu, 10 May 2007 05:34:34 +0000 (UTC) (envelope-from vd@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40])
	by mx1.freebsd.org (Postfix) with ESMTP id 49B6413C448;
	Thu, 10 May 2007 05:34:34 +0000 (UTC) (envelope-from vd@FreeBSD.org)
Received: from freefall.freebsd.org (vd@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l4A5YYTb039941;
	Thu, 10 May 2007 05:34:34 GMT (envelope-from vd@freefall.freebsd.org)
Received: (from vd@localhost)
	by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l4A5YY5a039937;
	Thu, 10 May 2007 05:34:34 GMT (envelope-from vd)
Date: Thu, 10 May 2007 05:34:34 GMT
From: Vasil Dimov <vd@FreeBSD.org>
Message-Id: <200705100534.l4A5YY5a039937@freefall.freebsd.org>
To: vd@FreeBSD.org, freebsd-bugs@FreeBSD.org, jhb@FreeBSD.org
Cc: 
Subject: Re: kern/112518: regression: "panic: blockabe sleep lock" @ boot
	after upgrade -CURRENT SMP amd64
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2007 05:34:34 -0000

Synopsis: regression: "panic: blockabe sleep lock" @ boot after upgrade -CURRENT SMP amd64

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