From owner-freebsd-i386@FreeBSD.ORG  Thu Jan  6 18:34:09 2005
Return-Path: <owner-freebsd-i386@FreeBSD.ORG>
Delivered-To: freebsd-i386@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id F319616A4CE; Thu,  6 Jan 2005 18:34:08 +0000 (GMT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id BBEAB43D2F; Thu,  6 Jan 2005 18:34:08 +0000 (GMT)
	(envelope-from emax@FreeBSD.org)
Received: from freefall.freebsd.org (emax@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j06IY8Ak068150;
	Thu, 6 Jan 2005 18:34:08 GMT
	(envelope-from emax@freefall.freebsd.org)
Received: (from emax@localhost)
	by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j06IY8L4068146;
	Thu, 6 Jan 2005 18:34:08 GMT
	(envelope-from emax)
Date: Thu, 6 Jan 2005 18:34:08 GMT
From: Maksim Yevmenkin <emax@FreeBSD.org>
Message-Id: <200501061834.j06IY8L4068146@freefall.freebsd.org>
To: silvere.thommerel@free.fr, emax@FreeBSD.org,
	freebsd-i386@FreeBSD.org
Subject: Re: i386/69876: [panic] new kernel panic on boot (-CURRENT)
X-BeenThere: freebsd-i386@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: I386-specific issues for FreeBSD <freebsd-i386.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-i386>,
	<mailto:freebsd-i386-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-i386>
List-Post: <mailto:freebsd-i386@freebsd.org>
List-Help: <mailto:freebsd-i386-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-i386>,
	<mailto:freebsd-i386-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jan 2005 18:34:09 -0000

Synopsis: [panic] new kernel panic on boot (-CURRENT)

State-Changed-From-To: open->closed
State-Changed-By: emax
State-Changed-When: Thu Jan 6 18:28:45 GMT 2005
State-Changed-Why: 
The fix was committed to -current and will be MFC'ed to 5-STABLE in 3 days.

The problem was that both Netgraph(4) framework and Bluetooth device drivers
were initialized at the same (SI_SUB_DRIVERS, SI_ORDER_MIDDLE) level. That
created a race when a call to the Netgraph(4) framework from the Bluetooth
device driver initialization routine hit an uninitialized mutex.

The problem is fixed by moving Netgraph(4) framework initialization on its
own level SI_SUB_NETGRAPH that happens just before SI_SUB_DRIVERS.


http://www.freebsd.org/cgi/query-pr.cgi?pr=69876