From nobody@FreeBSD.org  Mon Mar  1 22:33:46 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 71C7416A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Mon,  1 Mar 2004 22:33:46 -0800 (PST)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6CD3B43D1D
	for <freebsd-gnats-submit@FreeBSD.org>; Mon,  1 Mar 2004 22:33:46 -0800 (PST)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.10/8.12.10) with ESMTP id i226Xf72074434
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 1 Mar 2004 22:33:41 -0800 (PST)
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.10/8.12.10/Submit) id i226Xfsd074433;
	Mon, 1 Mar 2004 22:33:41 -0800 (PST)
	(envelope-from nobody)
Message-Id: <200403020633.i226Xfsd074433@www.freebsd.org>
Date: Mon, 1 Mar 2004 22:33:41 -0800 (PST)
From: Chris England <cengland@obscurity.org>
To: freebsd-gnats-submit@FreeBSD.org
Subject: panic: _mtx_lock_sleep: recursed on non_recursive mutex sbc ....
X-Send-Pr-Version: www-2.3

>Number:         63630
>Category:       kern
>Synopsis:       panic: _mtx_lock_sleep: recursed on non_recursive mutex sbc ....
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Mar 01 22:40:19 PST 2004
>Closed-Date:    Sat Mar 06 00:57:04 PST 2004
>Last-Modified:  Sat Mar  6 01:00:37 PST 2004
>Originator:     Chris England
>Release:        FreeBSD 5.2-CURRENT
>Organization:
>Environment:
FreeBSD eternal.stabs.org 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Mon Mar  1 20:51:26 PST 2004     stab@eternal.stabs.org:/usr/src/sys/i386/compile/GENERIC  i386

>Description:
Using 'device pcm' and 'device sbc' in kernel, or loading snd_pcm/snd_sb16 modules results in kernel panic when sound is played:

panic: _mtx_lock_sleep: recursed on non_recursive mutex sbc @ ../../../dev/sound
/isa/sbc.c:131
at line 436 in file ../../../kern/kern_mutex.c
Stopped at Debugger+0x45: xchgl %ebx, in_Debugger.0

dmesg:
sbc0: <SoundBlaster 16> at port 0x220-0x22f irq 5 drq 1 flags 0x15 on isa0
pcm0: <SB16 DSP 4.13> on sbc0

device.hints:
hint.sbc.0.at="isa"
hint.sbc.0.irq="5"
hint.sbc.0.port="0x220"
hint.sbc.0.drq="1"
hint.sbc.0.flags="0x15"

Last cvsup to -CURRENT was done on March 1st @ 12PM PST.
>How-To-Repeat:
Play a sound with the configuration mentioned.
>Fix:
      
>Release-Note:
>Audit-Trail:

From: Chris England <cengland@obscurity.org>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: kern/63630:panic: _mtx_lock_sleep: recursed on non_recursive
 mutex sbc ...
Date: Fri, 5 Mar 2004 16:28:19 -0800

 It is working after checking out the latest source and recompiling. I think this PR can be closed.
State-Changed-From-To: open->closed 
State-Changed-By: kris 
State-Changed-When: Sat Mar 6 00:56:43 PST 2004 
State-Changed-Why:  
Submitter reports problem resolved 

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

From: Kris Kennaway <kris@obsecurity.org>
To: Chris England <cengland@obscurity.org>
Cc: freebsd-gnats-submit@FreeBSD.org
Subject: Re: kern/63630: panic: _mtx_lock_sleep: recursed on non_recursive mutex sbc ....
Date: Sat, 6 Mar 2004 00:55:22 -0800

 On Mon, Mar 01, 2004 at 10:33:41PM -0800, Chris England wrote:
 
 > FreeBSD eternal.stabs.org 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Mon Mar  1 20:51:26 PST 2004     stab@eternal.stabs.org:/usr/src/sys/i386/compile/GENERIC  i386
 > 
 > >Description:
 > Using 'device pcm' and 'device sbc' in kernel, or loading snd_pcm/snd_sb16 modules results in kernel panic when sound is played:
 > 
 > panic: _mtx_lock_sleep: recursed on non_recursive mutex sbc @ ../../../dev/sound
 > /isa/sbc.c:131
 > at line 436 in file ../../../kern/kern_mutex.c
 > Stopped at Debugger+0x45: xchgl %ebx, in_Debugger.0
 
 Have you raised this on the mailing list?  Bug reports in -CURRENT
 should usually only be entered as PRs if you can't solve the problem
 there first.
 
 Kris
>Unformatted:
