From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Nick Austin <nick.austin@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Lock recursion deadlock detected
Date: Wed, 04 Oct 2006 15:12:31 +0200 [thread overview]
Message-ID: <1159967551.2792.2.camel@taijtu> (raw)
In-Reply-To: <8a6316160610032129red27121rfceb223e04dc88a@mail.gmail.com>
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.
prev parent reply other threads:[~2006-10-04 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 4:29 Nick Austin
2006-10-04 13:12 ` Peter Zijlstra [this message]
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=1159967551.2792.2.camel@taijtu \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=nick.austin@gmail.com \
/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
Powered by JetHome