From: "J. Bruce Fields" <bfields@fieldses.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Tino Keitel <tino.keitel@tikei.de>, Neil Brown <neilb@suse.de>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.38-rc3: kernel BUG at fs/nfsd/nfs4state.c:3132!
Date: Fri, 11 Feb 2011 10:21:12 -0500 [thread overview]
Message-ID: <20110211152112.GA3005@fieldses.org> (raw)
In-Reply-To: <s5hsjvuoqqt.wl%tiwai@suse.de>
On Fri, Feb 11, 2011 at 10:38:34AM +0100, Takashi Iwai wrote:
> At Tue, 8 Feb 2011 23:12:35 +0100,
> Tino Keitel wrote:
> >
> > Hi,
> >
> > I get the following error with kernel 2.6.38-rc3 during normal file access via
> > NFS v4.
> >
> > At least one other user seems to have the same problem:
> > http://pastebin.com/QRq1TMkj
> >
> > <0>------------[ cut here ]------------
> > kernel BUG at fs/nfsd/nfs4state.c:3132!
> > <0>invalid opcode: 0000 [#1] SMP
> > <0>last sysfs file: /sys/devices/virtual/block/dm-8/uevent
> > CPU 0
> > Modules linked in: ipv6 usblp btusb bluetooth loop arc4 ecb
> > snd_hda_codec_idt snd_hda_intel snd_hda_codec snd_pcm_oss ath5k
> > dvb_usb_vp7045 ath dvb_usb snd_pcm snd_timer mac80211
> > snd_page_alloc evdev dvb_core sky2 rc_core ata_piix cfg80211
> >
> > Pid: 2280, comm: nfsd Not tainted 2.6.38-rc3-00062-gb64606b #6
> > Mac-F4208EAA/Macmini2,1
> > RIP: 0010:[<ffffffff8119f973>] [<ffffffff8119f973>]
> > nfs4_preprocess_stateid_op+0x3a3/0x490
> > RSP: 0018:ffff8800b399bd50 EFLAGS: 00010246
> > RAX: 0000000000000000 RBX: ffff8800b60a9000 RCX: ffffffff8175a010
> > RDX: ffff8800ab784e48 RSI: ffffffff8175a020 RDI: ffffffff8175a000
> > RBP: ffff8800a4ce5678 R08: 0000000000000000 R09: 0000000000000000
> > R10: ffff8800b3910180 R11: c600000000000000 R12: ffff8800b390f1c0
> > R13: ffff8800b390f1a0 R14: 0000000000000000 R15: ffff8800aba079a0
> > FS: 0000000000000000(0000) GS:ffff8800bde00000(0000)
> > knlGS:0000000000000000
> > CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> > CR2: 00007f2b8805d000 CR3: 00000000b6fe8000 CR4: 00000000000006b0
> > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> > DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> > Process nfsd (pid: 2280, threadinfo ffff8800b399a000, task
> > ffff8800b63a62d0)
> > <0>Stack:
> > 000000004d507f0d ffff8800b390f1a0 ffff8800b3910040 ffff8800b391c000
> > 0000000016000000 0000000000000000 ffff8800b3910040 ffffffff8118f549
> > ffff8800b390f000 ffff8800b3910000 ffff8800b390f000 ffff8800b391c000
> > <0>Call Trace:
> > [<ffffffff8118f549>] ? nfsd4_read+0x79/0xc0
> > [<ffffffff81190096>] ? nfsd4_proc_compound+0x416/0x4d0
> > [<ffffffff8117f5ad>] ? nfsd_dispatch+0xfd/0x240
> > [<ffffffff8146f1f9>] ? svc_process_common+0x339/0x680
> > [<ffffffff81035b70>] ? default_wake_function+0x0/0x20
> > [<ffffffff8117ecc0>] ? nfsd+0x0/0x150
> > [<ffffffff8146f80a>] ? svc_process+0x10a/0x160
> > [<ffffffff8117ecc0>] ? nfsd+0x0/0x150
> > [<ffffffff8117ed72>] ? nfsd+0xb2/0x150
> > [<ffffffff81055ff6>] ? kthread+0x96/0xa0
> > [<ffffffff810039b4>] ? kernel_thread_helper+0x4/0x10
> > [<ffffffff81055f60>] ? kthread+0x0/0xa0
> > [<ffffffff810039b0>] ? kernel_thread_helper+0x0/0x10
> > <0>Code: 27 29 41 3b 47 50 0f 87 9a fd ff ff 0f 83 e9 fe ff ff e9 76 ff
> > ff ff 48 8b 42 48 45 31 f6 49 89 04 24 48 85 c0 0f 85 7b fd ff ff <0f>
> > 0b 49 8b 57 48 48 8b 42 40 48 85 c
> > 0 0f 85 2a ff ff ff 48 8b
> > RIP [<ffffffff8119f973>] nfs4_preprocess_stateid_op+0x3a3/0x490
> > RSP <ffff8800b399bd50>
> > ---[ end trace 7ef2fa5b1b62014a ]---
>
> [Added relevant guys to Cc]
>
> This occurred on my machine with 2.6.38-rc4.
Again, 2.6.38-rc4 does not have a BUG() on line 3132. Could you post
the full oops message from your machine?
--b.
> I didn't see it in 2.6.37.
next prev parent reply other threads:[~2011-02-11 15:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110208221235.GA16984@mac.home>
2011-02-11 9:38 ` 2.6.38-rc3: kernel BUG at fs/nfsd/nfs4state.c:3132! Takashi Iwai
2011-02-11 15:21 ` J. Bruce Fields [this message]
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
2011-02-09 22:04 Tino Keitel
2011-02-10 21:36 ` J. Bruce Fields
2011-02-10 21:49 ` Tino Keitel
2011-02-10 23:41 ` Tino Keitel
2011-02-15 1:08 ` 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=20110211152112.GA3005@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tino.keitel@tikei.de \
--cc=tiwai@suse.de \
/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