Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757226Ab1BKPVR (ORCPT ); Fri, 11 Feb 2011 10:21:17 -0500 Received: from fieldses.org ([174.143.236.118]:49032 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756711Ab1BKPVQ (ORCPT ); Fri, 11 Feb 2011 10:21:16 -0500 Date: Fri, 11 Feb 2011 10:21:12 -0500 From: "J. Bruce Fields" To: Takashi Iwai Cc: Tino Keitel , Neil Brown , Trond Myklebust , linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: 2.6.38-rc3: kernel BUG at fs/nfsd/nfs4state.c:3132! Message-ID: <20110211152112.GA3005@fieldses.org> References: <20110208221235.GA16984@mac.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3581 Lines: 81 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:[] [] > > 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: > > [] ? nfsd4_read+0x79/0xc0 > > [] ? nfsd4_proc_compound+0x416/0x4d0 > > [] ? nfsd_dispatch+0xfd/0x240 > > [] ? svc_process_common+0x339/0x680 > > [] ? default_wake_function+0x0/0x20 > > [] ? nfsd+0x0/0x150 > > [] ? svc_process+0x10a/0x160 > > [] ? nfsd+0x0/0x150 > > [] ? nfsd+0xb2/0x150 > > [] ? kthread+0x96/0xa0 > > [] ? kernel_thread_helper+0x4/0x10 > > [] ? kthread+0x0/0xa0 > > [] ? 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 [] nfs4_preprocess_stateid_op+0x3a3/0x490 > > RSP > > ---[ 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/