Messages in this thread |  | | | Subject | Re: Lock recursion deadlock detected | | From | Peter Zijlstra <> | | Date | Wed, 04 Oct 2006 15:12:31 +0200 |
| |
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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |