linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis Claudio R. Goncalves" <lclaudio@uudg.org>
To: linux-rt-users@vger.kernel.org
Subject: 2.6.33.9-rt31: Lockdep: BUG: circular locking deadlock detected!
Date: Thu, 14 Apr 2011 09:45:04 -0300	[thread overview]
Message-ID: <20110414124503.GA18084@uudg.org> (raw)

I have been running 2.6.33.9-rt31 for three days now and just noticed this
message in my dmesg:

(I can't investigate it now so I decided to share the message)

============================================
[ BUG: circular locking deadlock detected! ]
--------------------------------------------
udisks-daemon/2229 is deadlocking current task hald-addon-stor/1554


1) hald-addon-stor/1554 is trying to acquire this lock:
 [ffff880075b59220] {&bdev->bd_mutex}
.. ->owner: ffff88005f7ec401
.. held by:     udisks-daemon: 2229 [ffff88005f7ec400, 120]

2) udisks-daemon/2229 is blocked on this lock:
 [ffffffff81aafb90] {kernel_sem.lock}
INFO: lockdep is turned off.
INFO: lockdep is turned off.

udisks-daemon/2229's [blocked] stackdump:

 ffff8800762cb6d8 0000000000000046 0000000000000000 ffffffff8141fc81
 0000000000000000 0000000000000046 000000000000b428 ffff88005f7ec7f0
 ffff880078710b80 ffff88005f7ec400 0000000000000000 0000000000000000
Call Trace:
 [<ffffffff8141fc81>] ? rt_spin_lock_slowunlock+0x23/0x7d
 [<ffffffff8141eb3f>] schedule+0x13/0x23
 [<ffffffff8141eded>] schedule_timeout+0x36/0xed
 [<ffffffff81420bb4>] ? _raw_spin_unlock_irqrestore+0x53/0x61
 [<ffffffff8141fcb1>] ? rt_spin_lock_slowunlock+0x53/0x7d
 [<ffffffff81074714>] ? rt_spin_lock_fastunlock.clone.11+0x2d/0x2f
 [<ffffffff8141e10c>] wait_for_common+0xb1/0x10b
 [<ffffffff8103c147>] ? default_wake_function+0x0/0x16
 [<ffffffff814202cb>] ? rt_spin_unlock+0x2e/0x32
 [<ffffffff8141e209>] wait_for_completion+0x1d/0x1f
 [<ffffffff811f98fb>] blk_execute_rq+0xd3/0x108
 [<ffffffff812b5702>] scsi_execute+0xf5/0x147
 [<ffffffff812b57db>] scsi_execute_req+0x87/0xb9
 [<ffffffff812bfdfb>] sd_revalidate_disk+0x1e8/0x16a4
 [<ffffffff81074714>] ? rt_spin_lock_fastunlock.clone.11+0x2d/0x2f
 [<ffffffff814202cb>] ? rt_spin_unlock+0x2e/0x32
 [<ffffffff81125371>] ? __invalidate_device+0x48/0x53
 [<ffffffff81120000>] ? submit_bh+0x10b/0x11a
 [<ffffffff811254f9>] check_disk_change+0x52/0x5d
 [<ffffffff812be48f>] sd_open+0xf9/0x1a8
 [<ffffffff811262fa>] __blkdev_get+0xde/0x39d
 [<ffffffff811265cb>] ? blkdev_open+0x0/0xbf
 [<ffffffff811265c9>] blkdev_get+0x10/0x12
 [<ffffffff8112664e>] blkdev_open+0x83/0xbf
 [<ffffffff810fccc1>] __dentry_open+0x22a/0x373
 [<ffffffff811e15f4>] ? devcgroup_inode_permission+0xf0/0x11d
 [<ffffffff811c6598>] ? security_inode_permission+0x21/0x23
 [<ffffffff810fdc83>] nameidata_to_filp+0x3f/0x50
 [<ffffffff81109f0b>] do_filp_open+0x591/0xade
 [<ffffffff8106ea1c>] ? lock_acquire+0xd2/0xe1
 [<ffffffff8141fc81>] ? rt_spin_lock_slowunlock+0x23/0x7d
 [<ffffffff81420bb4>] ? _raw_spin_unlock_irqrestore+0x53/0x61
 [<ffffffff81074714>] ? rt_spin_lock_fastunlock.clone.11+0x2d/0x2f
 [<ffffffff814202cb>] ? rt_spin_unlock+0x2e/0x32
 [<ffffffff81113d13>] ? alloc_fd+0x10b/0x11d
 [<ffffffff810fdcf8>] do_sys_open+0x64/0x119
 [<ffffffff810fddcd>] sys_open+0x20/0x22
 [<ffffffff81002db2>] system_call_fastpath+0x16/0x1b

hald-addon-stor/1554's [current] stackdump:

Pid: 1554, comm: hald-addon-stor Not tainted 2.6.33.9-rt31 #8
Call Trace:
 [<ffffffff81074d4a>] debug_rt_mutex_print_deadlock+0x17f/0x1a6
 [<ffffffff81074bfa>] ? debug_rt_mutex_print_deadlock+0x2f/0x1a6
 [<ffffffff8141f64f>] __rt_mutex_slowlock.clone.10+0x86/0xc8
 [<ffffffff8141f80f>] rt_mutex_slowlock+0x17e/0x23a
 [<ffffffff811262a6>] ? __blkdev_get+0x8a/0x39d
 [<ffffffff8141f93c>] rt_mutex_lock+0x35/0x3a
 [<ffffffff8142033c>] _mutex_lock_nested+0x3a/0x41
 [<ffffffff811262a6>] ? __blkdev_get+0x8a/0x39d
 [<ffffffff811262a6>] __blkdev_get+0x8a/0x39d
 [<ffffffff811265cb>] ? blkdev_open+0x0/0xbf
 [<ffffffff811265c9>] blkdev_get+0x10/0x12
 [<ffffffff8112664e>] blkdev_open+0x83/0xbf
 [<ffffffff810fccc1>] __dentry_open+0x22a/0x373
 [<ffffffff811e15f4>] ? devcgroup_inode_permission+0xf0/0x11d
 [<ffffffff811c6598>] ? security_inode_permission+0x21/0x23
 [<ffffffff810fdc83>] nameidata_to_filp+0x3f/0x50
 [<ffffffff81109f0b>] do_filp_open+0x591/0xade
 [<ffffffff8106ea1c>] ? lock_acquire+0xd2/0xe1
 [<ffffffff8141fc81>] ? rt_spin_lock_slowunlock+0x23/0x7d
 [<ffffffff81420bb4>] ? _raw_spin_unlock_irqrestore+0x53/0x61
 [<ffffffff81074714>] ? rt_spin_lock_fastunlock.clone.11+0x2d/0x2f
 [<ffffffff814202cb>] ? rt_spin_unlock+0x2e/0x32
 [<ffffffff81113d13>] ? alloc_fd+0x10b/0x11d
 [<ffffffff810fdcf8>] do_sys_open+0x64/0x119
 [<ffffffff810fddcd>] sys_open+0x20/0x22
 [<ffffffff81002db2>] system_call_fastpath+0x16/0x1b
INFO: lockdep is turned off.
[ turning off deadlock detection.Please report this trace. ]


Cheers,
Luis
-- 
[ Luis Claudio R. Goncalves                    Bass - Gospel - RT ]
[ Fingerprint: 4FDD B8C4 3C59 34BD 8BE9  2696 7203 D980 A448 C8F8 ]


                 reply	other threads:[~2011-04-14 12:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20110414124503.GA18084@uudg.org \
    --to=lclaudio@uudg.org \
    --cc=linux-rt-users@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).