2.6.38-rc3: kernel BUG at fs/nfsd/nfs4state.c:3132!

DISCUSSION Tino Keitel 2 participants 5 messages Feb 9, 2011 – Feb 15, 2011

Subsystems (2)

NFS client NFS server

lore

Share & tools

lore

Tino Keitel

author

2011-02-09 22:12 UTC #0 lore raw

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

<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 ]---

Regards,
Tino

J. Bruce Fields

2011-02-10 21:36 UTC #1 lore raw

Quoted 7 lines · Tino Keitel

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.

Quoted 3 lines

<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.

Quoted 9 lines

<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

Also, I haven't seen any commit b64606b.

Are you sure about the kernel version here?

--b.

Quoted 49 lines

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 ]---
Regards,
Tino
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Tino Keitel

author

2011-02-10 21:49 UTC #2 lore raw

Quoted 9 lines · J. Bruce Fields

Quoted 7 lines · Tino Keitel
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

Quoted 8 lines

Thanks for the report.
Quoted 3 lines
<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

Tino Keitel

author

2011-02-10 23:41 UTC #3 lore raw

In reply to J. Bruce Fields

Quoted 9 lines · J. Bruce Fields

Quoted 7 lines · Tino Keitel
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

Quoted 8 lines

Thanks for the report.
Quoted 3 lines
<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.

Mine does:

$ git show | head -n 5 ; echo ; head -n 3132 fs/nfsd/nfs4state.c | tail -n 1
commit ebf53826e105f488f4f628703a108e98940d1dc5
Author: Linus Torvalds <[email protected]>
Date:   Tue Feb 1 13:05:49 2011 +1000

    Linux 2.6.38-rc3

			BUG_ON(!*filpp);

This is vanilla upstream source.

Regards,
Tino

J. Bruce Fields

2011-02-15 01:08 UTC #4 lore raw

Quoted 26 lines · Tino Keitel

Quoted 9 lines · J. Bruce Fields
Quoted 7 lines · Tino Keitel
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
Quoted 8 lines
Thanks for the report.
Quoted 3 lines
<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.
Mine does:
$ git show | head -n 5 ; echo ; head -n 3132 fs/nfsd/nfs4state.c | tail -n 1
commit ebf53826e105f488f4f628703a108e98940d1dc5
Author: Linus Torvalds <[email protected]>
Date:   Tue Feb 1 13:05:49 2011 +1000

Quoted 6 lines

    Linux 2.6.38-rc3

			BUG_ON(!*filpp);
$
This is vanilla upstream source.

Yes, apologies, that was my mistake; please see

	git://linux-nfs.org/~bfields/linux.git for-2.6.38

for the fix.

--b.