From: Tino Keitel <tino.keitel@tikei.de>
To: linux-nfs@vger.kernel.org
Subject: Re: 2.6.38-rc3: kernel BUG at fs/nfsd/nfs4state.c:3132!
Date: Thu, 10 Feb 2011 22:49:14 +0100 [thread overview]
Message-ID: <20110210214914.GA24324@mac.home> (raw)
In-Reply-To: <20110210213632.GA29900@fieldses.org>
On Thu, Feb 10, 2011 at 16:36:32 -0500, J. Bruce Fields wrote:
> On Wed, Feb 09, 2011 at 11:04:27PM +0100, Tino Keitel wrote:
> > Hi,
> >
> > I get the following error with kernel 2.6.38-rc3 during normal file access via
> > NFS v4. The underlying FS is ext4, if that matters.
> >
> > At least one other user seems to have the same problem:
> > http://pastebin.com/QRq1TMkj
>
> Thanks for the report.
>
> >
> > <0>------------[ cut here ]------------
> > kernel BUG at fs/nfsd/nfs4state.c:3132!
>
> This is a bit odd: v2.6.38-rc3 doesn't have a BUG on line 3132 of
> fs/nfsd/nfs4state.c.
It is something after -rc3, and I have another patch applied (regarding
sd devices at suspend wakeup).
My nfs4state.c was last touched by the merge commit
18bce371ae09af6c20ee62c1092a4d1d0e84dd49.
Regards,
Tino
next prev parent reply other threads:[~2011-02-10 21:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 22:04 2.6.38-rc3: kernel BUG at fs/nfsd/nfs4state.c:3132! Tino Keitel
2011-02-10 21:36 ` J. Bruce Fields
2011-02-10 21:49 ` Tino Keitel [this message]
2011-02-10 23:41 ` Tino Keitel
2011-02-15 1:08 ` J. Bruce Fields
[not found] <20110208221235.GA16984@mac.home>
2011-02-11 9:38 ` Takashi Iwai
2011-02-11 15:21 ` J. Bruce Fields
2011-02-11 15:29 ` Takashi Iwai
2011-02-11 15:37 ` J. Bruce Fields
2011-02-11 16:01 ` Takashi Iwai
2011-02-11 16:05 ` J. Bruce Fields
2011-02-11 16:12 ` Takashi Iwai
2011-02-11 16:57 ` Takashi Iwai
2011-02-11 16:59 ` Takashi Iwai
2011-02-11 17:00 ` J. Bruce Fields
2011-02-11 17:43 ` J. Bruce Fields
2011-02-11 18:15 ` Takashi Iwai
2011-02-14 11:35 ` Takashi Iwai
2011-02-14 14:29 ` J. Bruce Fields
2011-02-11 17:00 ` J. Bruce Fields
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=20110210214914.GA24324@mac.home \
--to=tino.keitel@tikei.de \
--cc=linux-nfs@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