From: Neil Brown <neilb@suse.de>
To: "Phy Prabab" <phyprabab@gmail.com>
Cc: "Adrian Bunk" <bunk@stusta.de>,
linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: Opps in 2.6.21-rc4 nfsd
Date: Mon, 26 Mar 2007 10:50:31 +1000 [thread overview]
Message-ID: <17927.6359.721594.133569@notabene.brown> (raw)
In-Reply-To: message from Phy Prabab on Friday March 23
On Friday March 23, phyprabab@gmail.com wrote:
> Adrian et al,
>
> Under 2.6.20.2+3 I get a similar crash and more frequently. At least
> under 2.6.21rc4 I only get this about once every two hours under heavy
> nfs testing.
That is very odd. The code where it is crashing in the trace you
provide does not exist in 2.6.20 at all.
Do you have an Oops trace from when it crashed under 2.6.20.x ??
I'll try to have a patch for you to try on 2.6.21rc4 shortly.
What version of nfs-utils are you using?
Thanks,
NeilBrown
next prev parent reply other threads:[~2007-03-26 0:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 19:24 Phy Prabab
2007-03-23 15:29 ` Adrian Bunk
2007-03-23 15:45 ` Phy Prabab
2007-03-26 0:50 ` Neil Brown [this message]
2007-03-26 1:08 ` Neil Brown
2007-03-26 7:07 ` Phy Prabab
2007-03-23 17:47 ` Chuck Ebbert
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=17927.6359.721594.133569@notabene.brown \
--to=neilb@suse.de \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=phyprabab@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
all inboxes | Powered by JetHome®