From: Oleg Verych <olecom@flower.upol.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: nfs3: possible recursive locking (Re: BUG: soft lockup detected on CPU#0! (2.6.18.2))
Date: Thu, 23 Nov 2006 08:31:45 +0000 (UTC) [thread overview]
Message-ID: <slrneman7h.1er.olecom@deen.upol.cz.local> (raw)
In-Reply-To: 86odqzbcmy.fsf@sif.msconsult.dk
On 2006-11-22, Rasmus BЬg Hansen wrote:
[]
>> Did this like "my server froze. It was entirely dead and had to be power
>> cycled."?
>
> Sorry, I forgot. No it didn't freeze, it is still gladly running as if
> nothing happened.
If something really bad will happen with nfsd, try to find somebody in
MAINTAINERS file to Cc to.
____
next prev parent reply other threads:[~2006-11-23 8:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 16:52 BUG: soft lockup detected on CPU#0! (2.6.18.2) Rasmus Bøg Hansen
2006-11-16 10:30 ` smbfs (Re: BUG: soft lockup detected on CPU#0! (2.6.18.2)) Oleg Verych
2006-11-17 15:45 ` Rasmus Bøg Hansen
2006-11-22 12:22 ` Rasmus Bøg Hansen
2006-11-22 14:12 ` nfs3: possible recursive locking " Oleg Verych
2006-11-22 17:43 ` Rasmus Bøg Hansen
2006-11-23 8:31 ` Oleg Verych [this message]
2006-11-17 22:53 ` smbfs " Andrew Morton
2006-11-18 3:30 ` [patch] smbfs: is obsolete, please use CIFS Oleg Verych
2006-11-19 22:18 ` smbfs (Re: BUG: soft lockup detected on CPU#0! (2.6.18.2)) Rasmus Bøg Hansen
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=slrneman7h.1er.olecom@deen.upol.cz.local \
--to=olecom@flower.upol.cz \
--cc=linux-kernel@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