=============================================
[ INFO: possible recursive locking detected ]
2.6.20-1.2962.fc7 #1
---------------------------------------------
rosegardenseque/5229 is trying to acquire lock:
 (&grp->list_mutex){----}, at: [<ffffffff881d4352>] 
snd_seq_deliver_event+0x93/0x173 [snd_seq]

but task is already holding lock:
 (&grp->list_mutex){----}, at: [<ffffffff881d4352>] 
snd_seq_deliver_event+0x93/0x173 [snd_seq]

other info that might help us debug this:
1 lock held by rosegardenseque/5229:
 #0:  (&grp->list_mutex){----}, at: [<ffffffff881d4352>] 
snd_seq_deliver_event+0x93/0x173 [snd_seq]

stack backtrace:

Call Trace:
 [<ffffffff802a303b>] __lock_acquire+0x151/0xbc4
 [<ffffffff802a3ea4>] lock_acquire+0x4c/0x65
 [<ffffffff881d4352>] :snd_seq:snd_seq_deliver_event+0x93/0x173
 [<ffffffff8029eab8>] down_read+0x3e/0x4a
 [<ffffffff881d4352>] :snd_seq:snd_seq_deliver_event+0x93/0x173
 [<ffffffff881d56c6>] :snd_seq:snd_seq_kernel_client_dispatch+0x54/0x68
 [<ffffffff881fd05f>] :snd_seq_dummy:dummy_input+0x54/0x5a
 [<ffffffff881d41cb>] :snd_seq:snd_seq_deliver_single_event+0xf8/0x1ec
 [<ffffffff881d43a1>] :snd_seq:snd_seq_deliver_event+0xe2/0x173
 [<ffffffff881d4819>] :snd_seq:snd_seq_dispatch_event+0xed/0x110
 [<ffffffff881d6e0e>] :snd_seq:snd_seq_check_queue+0xbc/0x105
 [<ffffffff881d70e3>] :snd_seq:snd_seq_enqueue_event+0xb6/0xca
 [<ffffffff881d4501>] :snd_seq:snd_seq_client_enqueue_event+0xcf/0x101
 [<ffffffff881d5db2>] :snd_seq:snd_seq_write+0x140/0x198
 [<ffffffff8021634f>] vfs_write+0xcf/0x178
 [<ffffffff80216d64>] sys_write+0x47/0x70
 [<ffffffff8025c2b5>] tracesys+0xdc/0xe1


-- 
http://www.codemonkey.org.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to