Bug 439712 - INFO: possible circular locking dependency detected
INFO: possible circular locking dependency detected
Status: CLOSED DUPLICATE of bug 438584
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
rawhide
x86_64 Linux
low Severity low
: ---
: ---
Assigned To: John W. Linville
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-03-30 17:49 EDT by petrosyan
Modified: 2008-03-31 09:50 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-03-31 09:50:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description petrosyan 2008-03-30 17:49:59 EDT
Description of problem:
When suspending the laptop I get the following message.
=======================================================
[ INFO: possible circular locking dependency detected ]
2.6.25-0.172.rc7.git4.fc9.x86_64 #1
-------------------------------------------------------
NetworkManager/2167 is trying to acquire lock:
 ((name)){--..}, at: [<ffffffff81044a81>] flush_workqueue+0x0/0xa6

but task is already holding lock:
 (rtnl_mutex){--..}, at: [<ffffffff8122a687>] rtnetlink_rcv+0x1a/0x33

which lock already depends on the new lock.


the existing dependency chain (in reverse order) is:

-> #2 (rtnl_mutex){--..}:
       [<ffffffff81054828>] __lock_acquire+0xbd3/0xd63
       [<ffffffff81054a16>] lock_acquire+0x5e/0x78
       [<ffffffff812a43ec>] mutex_lock_nested+0xf7/0x295
       [<ffffffff8122a66b>] rtnl_lock+0x12/0x14
       [<ffffffff881296e2>] ieee80211_associated+0x1a4/0x1f4 [mac80211]
       [<ffffffff8812b4c4>] ieee80211_sta_work+0x170d/0x1890 [mac80211]
       [<ffffffff81043fe0>] run_workqueue+0xfc/0x203
       [<ffffffff810441c7>] worker_thread+0xe0/0xf1
       [<ffffffff8104778f>] kthread+0x49/0x76
       [<ffffffff8100cf78>] child_rip+0xa/0x12
       [<ffffffffffffffff>] 0xffffffffffffffff

-> #1 (&ifsta->work){--..}:
       [<ffffffff81054828>] __lock_acquire+0xbd3/0xd63
       [<ffffffff81054a16>] lock_acquire+0x5e/0x78
       [<ffffffff81043fda>] run_workqueue+0xf6/0x203
       [<ffffffff810441c7>] worker_thread+0xe0/0xf1
       [<ffffffff8104778f>] kthread+0x49/0x76
       [<ffffffff8100cf78>] child_rip+0xa/0x12
       [<ffffffffffffffff>] 0xffffffffffffffff

-> #0 ((name)){--..}:
       [<ffffffff8105472b>] __lock_acquire+0xad6/0xd63
       [<ffffffff81054a16>] lock_acquire+0x5e/0x78
       [<ffffffff81044adc>] flush_workqueue+0x5b/0xa6
       [<ffffffff8811f702>] ieee80211_stop+0x30e/0x3f0 [mac80211]
       [<ffffffff81221ca1>] dev_close+0x62/0x83
       [<ffffffff81221960>] dev_change_flags+0xaf/0x172
       [<ffffffff8122953e>] do_setlink+0x276/0x338
       [<ffffffff81229714>] rtnl_setlink+0x114/0x116
       [<ffffffff8122a878>] rtnetlink_rcv_msg+0x1d8/0x1f9
       [<ffffffff8123aa1e>] netlink_rcv_skb+0x3e/0xac
       [<ffffffff8122a696>] rtnetlink_rcv+0x29/0x33
       [<ffffffff8123a471>] netlink_unicast+0x1fe/0x26b
       [<ffffffff8123a7a8>] netlink_sendmsg+0x2ca/0x2dd
       [<ffffffff812148fe>] sock_sendmsg+0xfd/0x120
       [<ffffffff81214af3>] sys_sendmsg+0x1d2/0x23c
       [<ffffffff8100c1d0>] tracesys+0xd5/0xda
       [<ffffffffffffffff>] 0xffffffffffffffff

other info that might help us debug this:

1 lock held by NetworkManager/2167:
 #0:  (rtnl_mutex){--..}, at: [<ffffffff8122a687>] rtnetlink_rcv+0x1a/0x33

stack backtrace:
Pid: 2167, comm: NetworkManager Not tainted 2.6.25-0.172.rc7.git4.fc9.x86_64 #1

Call Trace:
 [<ffffffff810539ba>] print_circular_bug_tail+0x70/0x7b
 [<ffffffff810537d2>] ? print_circular_bug_entry+0x48/0x4f
 [<ffffffff8105472b>] __lock_acquire+0xad6/0xd63
 [<ffffffff81054a16>] lock_acquire+0x5e/0x78
 [<ffffffff81044a81>] ? flush_workqueue+0x0/0xa6
 [<ffffffff81044adc>] flush_workqueue+0x5b/0xa6
 [<ffffffff8811f702>] :mac80211:ieee80211_stop+0x30e/0x3f0
 [<ffffffff812a5e62>] ? _spin_unlock_bh+0x2f/0x33
 [<ffffffff81221ca1>] dev_close+0x62/0x83
 [<ffffffff81221960>] dev_change_flags+0xaf/0x172
 [<ffffffff8122953e>] do_setlink+0x276/0x338
 [<ffffffff812a5e2e>] ? _read_unlock+0x26/0x2b
 [<ffffffff81229714>] rtnl_setlink+0x114/0x116
 [<ffffffff8122a878>] rtnetlink_rcv_msg+0x1d8/0x1f9
 [<ffffffff8122a6a0>] ? rtnetlink_rcv_msg+0x0/0x1f9
 [<ffffffff8123aa1e>] netlink_rcv_skb+0x3e/0xac
 [<ffffffff8122a696>] rtnetlink_rcv+0x29/0x33
 [<ffffffff8123a471>] netlink_unicast+0x1fe/0x26b
 [<ffffffff8123a7a8>] netlink_sendmsg+0x2ca/0x2dd
 [<ffffffff812148fe>] sock_sendmsg+0xfd/0x120
 [<ffffffff81214788>] ? sock_recvmsg+0x10e/0x133
 [<ffffffff81047aa7>] ? autoremove_wake_function+0x0/0x38
 [<ffffffff810120aa>] ? native_sched_clock+0x50/0x6d
 [<ffffffff810ae2e9>] ? fget_light+0xac/0xdb
 [<ffffffff81051b75>] ? lock_release_holdtime+0x1e/0x108
 [<ffffffff81215314>] ? move_addr_to_kernel+0x40/0x49
 [<ffffffff8121c666>] ? verify_iovec+0x4f/0x91
 [<ffffffff81214af3>] sys_sendmsg+0x1d2/0x23c
 [<ffffffff81053637>] ? trace_hardirqs_on+0xf1/0x115
 [<ffffffff8102fbae>] ? hrtick_set+0x8b/0xfc
 [<ffffffff812a38a0>] ? thread_return+0x68/0xac
 [<ffffffff81073dd2>] ? audit_syscall_entry+0x126/0x15a
 [<ffffffff810133e7>] ? syscall_trace_enter+0xb5/0xb9
 [<ffffffff8100c1d0>] tracesys+0xd5/0xda


Version-Release number of selected component (if applicable):
kernel-2.6.25-0.172.rc7.git4.fc9.x86_64

How reproducible:
sometimes, when suspending the laptop.
Comment 1 John W. Linville 2008-03-31 09:50:23 EDT

*** This bug has been marked as a duplicate of 438584 ***

Note You need to log in before you can comment on or make changes to this bug.