Re: LOR in pcm

Ariff Abdullah wrote:
> On Sat, 10 Dec 2005 18:44:00 +0300
> Maxim Maximov <mcsi_at_mcsi.pp.ru> wrote:
> 
>>Hi all.
>>
>>	Got this on SMP CURRENT from Sun Dec  4 22:06:46 MSK 2005.
>>	I have no recording devices, FWIW.
>>
>>lock order reversal:
>>  1st 0xc35884c0 pcm0 (sound cdev) _at_
>>  /usr/src/sys/dev/sound/pcm/dsp.c:277 2nd 0xc3562ac0 pcm0:record:0
>>  (pcm record channel) _at_ 
>>/usr/src/sys/dev/sound/pcm/dsp.c:290
>>KDB: stack backtrace:
>>kdb_backtrace(0,ffffffff,c09a4d28,c09a4cb0,c0929504) at
>>kdb_backtrace+0x29 witness_checkorder(c3562ac0,9,c08ab43d,122) at
>>witness_checkorder+0x580
>>_mtx_lock_flags(c3562ac0,0,c08ab43del22,1) at
>>_mtx_lock_flags+0x5b dsp_open(c3586c00,7,2000,c436cc00,c0995100) at
>>dsp_open+0x2b2 giant_open(c3586c00,7,2000,c436cc00,c3586c00) at
>>giant_open+0x30 devfs_open(db324a18) at devfs_open+0x223
>>VOP_OPEN_APV(c0921cc0,db324a18) at VOP_OPEN_APV+0x7e
>>vn_open_cred(db324b70,db324c70,468,c3ee6b80,43) at
>>vn_open_cred+0x448 vn_open(db324b70,db324c70,468,43,c09e2ad0) at
>>vn_open+0x1e kern_open(c436cc00,15696050,0,7,bfbf6478) at
>>kern_open+0xb6 open(c436cc00,db324d04,86,c06acb33,c436cc00) at
>>open+0x1a syscall(14da003b,bf2f003b,bf2f003b,bfbf6488,15696050) at
>>syscall+0x27e Xint0x80_syscall() at Xint0x80_syscall+0x1f ---
>>syscall (5, FreeBSD ELF32, open), eip = 0x28a70b5f, esp = 
>>0xbfbf644c, ebp = 0xbfbf6478 ---
> 
> 
> I believe this is during playback startup, right? 

I'm sorry, I'm not sure. I noticed it after a while.

> If so, just ignore
> it for a while, it is quite harmless (although a bit annoying). I'll
> fix it alltogether hopefully before new year.

Thanks!

-- 
Maxim Maximov