From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: perex@suse.cz, alsa-devel@alsa-project.org,
"Andrew Morton" <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: 2.6.17-rc4-mm3-lockdep BUG: possible deadlock detected!
Date: Mon, 29 May 2006 20:32:47 +0200 [thread overview]
Message-ID: <6bffcb0e0605291132u701cd69tb855cf60fa317994@mail.gmail.com> (raw)
Hi,
I get this with Ingo's lockdep patch from
http://people.redhat.com/mingo/generic-irq-subsystem/
====================================
[ BUG: possible deadlock detected! ]
------------------------------------
modprobe/592 is trying to acquire lock:
(&grp->list_mutex){----}, at: [<fd9ee555>]
snd_seq_port_connect+0xc0/0x337 [snd_seq]
but task is already holding lock:
(&grp->list_mutex){----}, at: [<fd9ee4fb>]
snd_seq_port_connect+0x66/0x337 [snd_seq]
which could potentially lead to deadlocks!
other info that might help us debug this:
1 locks held by modprobe/592:
#0: (&grp->list_mutex){----}, at: [<fd9ee4fb>]
snd_seq_port_connect+0x66/0x337 [snd_seq]
stack backtrace:
<c1003f36> show_trace+0xd/0xf <c1004449> dump_stack+0x17/0x19
<c1039792> __lockdep_acquire+0xa1a/0xa39 <c1039bed> lockdep_acquire+0x69/0x82
<fd9ee570> snd_seq_port_connect+0xdb/0x337 [snd_seq] <fd9ea5f5>
snd_seq_ioctl_subscribe_port+0x96/0xe6 [snd_seq]
<fd9e91d4> snd_seq_do_ioctl+0x5d/0x68 [snd_seq] <fd9e921c>
snd_seq_kernel_client_ctl+0x2d/0x3b [snd_seq]
<f8877274> snd_seq_oss_create_client+0x12d/0x142 [snd_seq_oss]
<f88770f7> alsa_seq_oss_init+0xf7/0x147 [snd_seq_oss]
<c104116d> sys_init_module+0xa6/0x230 <c11efa8b> sysenter_past_esp+0x54/0x8d
Here is dmesg http://www.stardust.webpages.pl/files/lockdep/2.6.17-rc4-mm3-lockdep1/lockdep-dmesg
Here is config
http://www.stardust.webpages.pl/files/lockdep/2.6.17-rc4-mm3-lockdep1/lockdep-config
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)
next reply other threads:[~2006-05-29 18:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-29 18:32 Michal Piotrowski [this message]
2006-05-29 18:47 ` Andrew Morton
2006-05-30 10:34 ` Takashi Iwai
2006-05-29 19:07 ` Ingo Molnar
2006-05-29 19:53 ` Michal Piotrowski
2006-05-30 14:14 ` [Alsa-devel] " Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6bffcb0e0605291132u701cd69tb855cf60fa317994@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=akpm@osdl.org \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=perex@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®