Lock recursion deadlock detected
in [Kernel]
|
From: Nick Austin on 4 Oct 2006 00:30 I have the following in my dmesg: $ uname -a Linux frank 2.6.17-1.2174_FC5 #1 SMP Tue Aug 8 15:30:44 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux It should be noted that lockd failed on this server at the same time. Many entries like the flowing occurred on my NFS clients at the same time: do_vfs_lock: VFS is out of sync with lock manager! do_vfs_lock: VFS is out of sync with lock manager! lockd: server 192.168.100.17 not responding, timed out lockd: server 192.168.100.17 not responding, timed out I'm reporting this, just as the error message asks. :) Thanks! ========================================== [ BUG: lock recursion deadlock detected! | ------------------------------------------ lockd/2607 is trying to acquire this lock: [ffffffff88b063a0] {nlm_file_mutex} ... held by: lockd: 2607 [ffff8101385fc040, 115] .... acquired at: nlm_traverse_files+0x20/0x109 [lockd] .... trying at: nlm_release_file+0x35/0x111 [lockd] ------------------------------ | showing all locks held by: | (lockd/2607 [ffff8101385fc040, 115]): ------------------------------ #001: [ffffffff88b063a0] {nlm_file_mutex} .... acquired at: nlm_traverse_files+0x20/0x109 [lockd] lockd/2607's [current] stackdump: Call Trace: <ffffffff88af81ba>{:lockd:nlm_release_file+53} <ffffffff802a1df0>{report_deadlock+321} <ffffffff88af81ba>{:lockd:nlm_release_file+53} <ffffffff802a1fac>{check_deadlock+415} <ffffffff88af81ba>{:lockd:nlm_release_file+53} <ffffffff88af81ba>{:lockd:nlm_release_file+53} <ffffffff802a2059>{debug_mutex_add_waiter+159} <ffffffff802692e2>{__mutex_lock_slowpath+353} <ffffffff88af627f>{:lockd:lockd+0} <ffffffff88af81ba>{:lockd:nlm_release_file+53} <ffffffff88af722c>{:lockd:nlmsvc_free_block+162} <ffffffff88af718a>{:lockd:nlmsvc_free_block+0} <ffffffff80237961>{kref_put+117} <ffffffff88af680c>{:lockd:nlmsvc_traverse_blocks+212} <ffffffff88af803a>{:lockd:nlm_traverse_files+88} <ffffffff88af8113>{:lockd:nlmsvc_free_host_resources+40} <ffffffff88af8137>{:lockd:nlmsvc_invalidate_all+11} <ffffffff88af6381>{:lockd:lockd+258} <ffffffff80263b9e>{child_rip+8} <ffffffff88af627f>{:lockd:lockd+0} <ffffffff88af627f>{:lockd:lockd+0} <ffffffff80263b96>{child_rip+0} Showing all blocking locks in the system: S init: 1 [ffff81013acb47a0, 115] (not blocked on mutex) S migration/0: 2 [ffff81013acb4040, 0] (not blocked on mutex) S ksoftirqd/0: 3 [ffff81013acb67e0, 134] (not blocked on mutex) S watchdog/0: 4 [ffff81013acb6080, 0] (not blocked on mutex) S migration/1: 5 [ffff81013acb7820, 0] (not blocked on mutex) S ksoftirqd/1: 6 [ffff81013acb70c0, 134] (not blocked on mutex) S watchdog/1: 7 [ffff81013acc3860, 0] (not blocked on mutex) S events/0: 8 [ffff81013aecb7a0, 110] (not blocked on mutex) S events/1: 9 [ffff81013aecb040, 110] (not blocked on mutex) S khelper: 10 [ffff81013aecc7e0, 110] (not blocked on mutex) S kthread: 11 [ffff81013aecc080, 113] (not blocked on mutex) S kblockd/0: 15 [ffff81013acca7a0, 110] (not blocked on mutex) S kblockd/1: 16 [ffff81013acca040, 110] (not blocked on mutex) S kacpid: 17 [ffff81013acc97e0, 114] (not blocked on mutex) S khubd: 149 [ffff81013acc9080, 110] (not blocked on mutex) S kseriod: 151 [ffff81013a917080, 110] (not blocked on mutex) S pdflush: 214 [ffff81013a9177e0, 120] (not blocked on mutex) S pdflush: 215 [ffff81013a911040, 115] (not blocked on mutex) S kswapd0: 216 [ffff81013a86c7e0, 115] (not blocked on mutex) S aio/0: 217 [ffff81013a9117a0, 113] (not blocked on mutex) S aio/1: 218 [ffff81013a910100, 113] (not blocked on mutex) S kpsmoused: 372 [ffff810139eb4860, 111] (not blocked on mutex) S ata/0: 393 [ffff810139f02100, 110] (not blocked on mutex) S ata/1: 394 [ffff810139f057a0, 110] (not blocked on mutex) S scsi_eh_0: 400 [ffff810139eac860, 115] (not blocked on mutex) S scsi_eh_1: 401 [ffff810139ef9040, 115] (not blocked on mutex) S scsi_eh_2: 402 [ffff810139efb7e0, 115] (not blocked on mutex) S scsi_eh_3: 403 [ffff810139efb080, 115] (not blocked on mutex) S scsi_eh_4: 428 [ffff810139eae040, 112] (not blocked on mutex) S scsi_eh_5: 429 [ffff810139ea5080, 112] (not blocked on mutex) S scsi_eh_6: 442 [ffff810139eef7e0, 111] (not blocked on mutex) S scsi_eh_7: 443 [ffff810139eab0c0, 111] (not blocked on mutex) S kmirrord: 477 [ffff81013a9bb040, 116] (not blocked on mutex) S md1_raid1: 492 [ffff810139eb3820, 110] (not blocked on mutex) S md0_raid1: 496 [ffff810139eb4100, 110] (not blocked on mutex) S kjournald: 502 [ffff810139eaf080, 110] (not blocked on mutex) S kauditd: 541 [ffff810139ea1820, 111] (not blocked on mutex) S udevd: 567 [ffff810139eaf7e0, 113] (not blocked on mutex) S khpsbpkt: 1421 [ffff810138746860, 115] (not blocked on mutex) S knodemgrd_0: 1457 [ffff8101387560c0, 116] (not blocked on mutex) S md2_raid5: 1671 [ffff81013a8d67e0, 110] (not blocked on mutex) S kjournald: 1706 [ffff81013a9bc7e0, 110] (not blocked on mutex) S kjournald: 1708 [ffff81013a8d80c0, 110] (not blocked on mutex) S kjournald: 1710 [ffff8101385fc7a0, 110] (not blocked on mutex) S cpuspeed: 1852 [ffff810138756820, 115] (not blocked on mutex) S cpuspeed: 1853 [ffff810139eb30c0, 115] (not blocked on mutex) S dhclient: 2151 [ffff8101387cf860, 115] (not blocked on mutex) S syslogd: 2186 [ffff8101377db820, 116] (not blocked on mutex) R klogd: 2189 [ffff81012f318860, 116] (not blocked on mutex) S irqbalance: 2199 [ffff8101386467e0, 116] (not blocked on mutex) S portmap: 2215 [ffff81013a86c080, 116] (not blocked on mutex) S rpc.statd: 2234 [ffff81013affb0c0, 116] (not blocked on mutex) S mdadm: 2244 [ffff81013731c080, 115] (not blocked on mutex) S rpc.idmapd: 2269 [ffff810138627100, 115] (not blocked on mutex) S dbus-daemon: 2283 [ffff810132f277e0, 115] (not blocked on mutex) S hcid: 2292 [ffff810139eee040, 125] (not blocked on mutex) S sdpd: 2297 [ffff81012f7a90c0, 1
From: Peter Zijlstra on 4 Oct 2006 11:20 On Tue, 2006-10-03 at 21:29 -0700, Nick Austin wrote: > I have the following in my dmesg: > > $ uname -a > Linux frank 2.6.17-1.2174_FC5 #1 SMP Tue Aug 8 15:30:44 EDT 2006 > x86_64 x86_64 x86_64 GNU/Linux > > It should be noted that lockd failed on this server at the same time. > > Many entries like the flowing occurred on my NFS clients at the same time: > do_vfs_lock: VFS is out of sync with lock manager! > do_vfs_lock: VFS is out of sync with lock manager! > lockd: server 192.168.100.17 not responding, timed out > lockd: server 192.168.100.17 not responding, timed out > > I'm reporting this, just as the error message asks. :) > > Thanks! Thanks for reporting; however this bug has been fixed in .18-rc5, upgrading your kernel should rid you of this nuisance. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|
Pages: 1 Prev: second-best Girl here doing optimum . Next: 2.6.18: Kernel BUG at mm/rmap.c:522 |