Re: panic: process 839(xmms):1 holds process lock but isn't blocked ona lock

Another panic whilst mp3s were playing on xmms:

db> tr
kdb_enter(c068735f,c06df360,c068a355,e87308e4,c30adc80) at
kdb_enter+0x32
panic(c068a355,e4e,c2e18be4,1,c0686981) at panic+0x14b
turnstile_wait(c2b37200,c2e18b04,c30ade10,220,c2e18b04) at
turnstile_wait+0x5ec
_mtx_lock_sleep(c2e18b04,c30adc80,0,c0684acc,170) at
_mtx_lock_sleep+0xb0
_mtx_lock_flags(c2e18b04,0,c0684acc,170,c0518b28) at
_mtx_lock_flags+0xaf
fork1(c06da1e0,60034,0,e87309bc,8) at fork1+0x3f5
kthread_create(c0594878,c0709834,0,40000,0) at kthread_create+0x40
nfs_nfsiodnew(d69e16bc,200000a4,e8730a20,c04e7eca,c06dedf4) at
nfs_nfsiodnew+0x8d
nfs_asyncio(d69e15f4,0,0,0,0) at nfs_asyncio+0x69
nfs_strategy(e8730a64,1,c068e01e,36a,d69e16bc) at nfs_strategy+0x72
ibwrite(d69e15f4,0,c0693489,b1b,c0518b55) at ibwrite+0x2dc
nfs_flush(1,c30adc80,0,2,31d) at nfs_flush+0x3ed
nfs_close(e8730ba4,1,c068ff9d,140,c06d3360) at nfs_close+0x7d
vn_close(c3598738,3,c6d53700,c30adc80,c06b5e64) at vn_close+0x68
vn_closefile(c31453b8,c30adc80,c0684320,82a,0) at vn_closefile+0x5d
fdrop_locked(c31453b8,c30adc80,c06e2f20,c30adc80,0) at
fdrop_locked+0xab
closef(c31453b8,c30adc80,c0684320,3e3,0) at closef+0x32
close(c30adc80,e8730d14,4,431,1) at close+0xef
syscall(bfbf002f,8d4002f,bfbf002f,8062200,1) at syscall+0x13b
Xint0x80_syscall() at Xint0x80_syscall+0x1f
--- syscall (6, FreeBSD ELF32, close), eip = 0x28216b0f, esp =
0xbfbfe7bc, ebp = 0xbfbfe7e8 ---
db>


0n Wed, Dec 08, 2004 at 08:49:14AM -0500, Andrew R. Reiter wrote: 

> On Wed, 8 Dec 2004, Wilkinson, Alex wrote:
> 
> :Hi all,
> :
> :I got this panic today on a:
> :FreeBSD 5.3-STABLE #13: Mon Nov 29 09:49:10 CST 2004
> :
> :This panic is reproduceable via two methods:
> :
> :1.  # kldload snd_ich
> :
> :2.  add snd_ich_load="YES" to /boot/loader.conf; reboot;
> :    # kldunload snd_ich
> :
> 
> For what it's worth, on recent -CURRENt, I've had 'kdload snd_ich' hang my
> machine... as in full lock up.  kldload snd_driver I've had varied
> success... I booted yesterday AM's -CURRENT and after boot kldload'd
> snd_Driver and had a hang... but after reb ooting, starting X, su'ing to
> root, and loading.. it worked.  Random :-)
> 
> :I have a kernel with debugging symbols and a vmcore if anyone is
> :interested.
> :
> :db> trace
> :kdb_enter(c068735f,c06df360,c068a355,e3744c64,c266c320) at
> :kdb_enter+0x32
> :panic(c068a355,347,c3020698,1,c0686981) at panic+0x14b
> :turnstile_wait(c2ef6600,c06ddec0,c3021e10,220,c06ddec0) at
> :turnstile_wait+0x5ec
> :_mtx_lock_sleep(c06ddec0,c266c320,0,c0684ceb,222) at
> :_mtx_lock_sleep+0xb0
> :_mtx_lock_flags(c06ddec0,0,c0684ceb,222,0) at _mtx_lock_flags+0xaf
> :ithread_loop(c2661480,e3744d48,c0684acc,323,c2661480) at
> :ithread_loop+0x1ea
> :fork_exit(c04de759,c2661480,e3744d48) at fork_exit+0xa6
> :fork_trampoline() at fork_trampoline+0x8
> :--- trap 0x1, eip = 0, esp = 0xe3744d7c, ebp = 0 ---
> :db> show pcpu
> :cpuid        = 0
> :curthread    = 0xc266c320: pid 28 "irq18: uhci2 bt0++"
> :curpcb       = 0xe3744da0
> :fpcurthread  = none
> :idlethread   = 0xc26644b0: pid 11 "idle"
> :APIC ID      = 0
> :currentldt   = 0x28
> :spin locks held:
> :db> show lockedvnods
> :Locked vnodes
> :db>
> :
> : (850)-08.12.2004 hostname-{17:26}-[/var/crash]->sudo kldunload snd_ich
> :Password:
> :lock order reversal
> : 1st 0xc2781a40 pcm0 (sound cdev) _at_
> :/usr/src/sys/modules/sound/sound/../../../dev/sound/pcm/sound.c:706
> : 2nd 0xc07c6a20 sndstat (sndstat) _at_
> :/usr/src/sys/modules/sound/sound/../../../dev/sound/pcm/sndstat.c:257
> :KDB: stack backtrace:
> :witness_checkorder(c07c6a20,9,c07c1a3d,101,0) at
> :witness_checkorder+0x5fa
> :_sx_xlock(c07c6a20,c07c1a3d,101,0,c2738e00) at _sx_xlock+0x5c
> :sndstat_unregister(c2753800,8,c07c1b35,2c2,c2753800) at
> :sndstat_unregister+0x27
> :pcm_unregister(c2753800,c06a5f7c,c2753800,e75e2bfc,c2753800) at
> :pcm_unregister+0x1f5
> :ich_pci_detach(c2753800,c26fd850,c06a5f7c,c07a88f1,3) at
> :ich_pci_detach+0x13
> :device_detach(c2753800,c07a8909,c26e2000,1,c26aed80) at
> :device_detach+0x6b
> :
> :_______________________________________________
> :freebsd-current_at_freebsd.org mailing list
> :http://lists.freebsd.org/mailman/listinfo/freebsd-current
> :To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
> :
> :
> 
> --
> Andrew R. Reiter
> arr_at_watson.org
> arr_at_FreeBSD.org
>