2.6.33.5 rt23: machine lockup (nfs/autofs related?)
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 6 lines · john stultz
Quoted 5 lines · Fernando Lopez-Lezcano
Quoted 4 lines · john stultz
Quoted 3 lines · Fernando Lopez-Lezcano
We are having problems with 2.6.33.5+rt23, at least in our configuration while accessing an nfs automounted directory. This causes a complete machine lockup (press reset to exit as the only option).
I replied to this yesterday., then realized that it was a one-way news group of lkml. Let's see if I can fudge a threaded reply.
================================================
I also have some nfs issues with this combo, but not as severe. Maybe my fstab mount options help:
noauto,users,rsize=4096,wsize=4096,timeo=14,intr,hard
Anyway, Fedora 13,both vanilla 2.6.33.5 and Redhat patched, exhibit it as a kernel fault upon user mounting a nfs partition. It is the uniprocessor variant kernel (not PAE). I get an operating nfs connection, but the kernel auto bug reporting thingy (abrt) pops up shortly after the mount. I was going to work through a few variations on kernels etc before trying bugzilla but I've acquired a bug of the non-computer variety and won't feel up to this for a week or so.
WARNING: at fs/namespace.c:1203 umount_tree+0xd8/0x118() Hardware name: VT8366-8233A Modules linked in: nfs fuse nfsd lockd nfs_acl auth_rpcgss exportfs sunrpc ipv6 binfmt_misc snd_via82xx snd_ac97_codec ac97_bus snd_seq snd_pcm snd_timer snd_page_alloc snd_mpu401_uart 8250_pnp snd_rawmidi 8250 snd_seq_device pcspkr i2c_viapro snd serial_core parport_pc 8139too i2c_core fan thermal 8139cp soundcore mii firewire_ohci uhci_hcd floppy firewire_core [last unloaded: freq_table] Pid: 2842, comm: mount.nfs Not tainted 2.6.33.5-rt23.fc13.i686 #1 Call Trace: [<c0434f84>] warn_slowpath_common+0x6a/0x81 [<c04d281a>] ? umount_tree+0xd8/0x118 [<c0434fad>] warn_slowpath_null+0x12/0x15 [<c04d281a>] umount_tree+0xd8/0x118 [<c04d3084>] put_mnt_ns+0x80/0xa4 [<c04c8339>] ? vfs_path_lookup+0x8a/0x99 [<f89e58d2>] nfs_follow_remote_path+0x46/0xec [nfs] [<f89e587c>] ? nfs_do_root_mount+0x61/0x71 [nfs] [<f89e5a65>] nfs4_try_mount+0x61/0x94 [nfs] [<f89e6bc8>] nfs_get_sb+0x61d/0x815 [nfs] [<c04ba568>] ? pcpu_alloc+0x6bb/0x6d0 [<c070cd77>] ? rt_spin_unlock+0xd/0xf [<c04a3da5>] ? kstrdup+0x2f/0x3f [<c04a3da5>] ? kstrdup+0x2f/0x3f [<c04c11f7>] vfs_kern_mount+0x86/0x11f [<c04c12db>] do_kern_mount+0x34/0xb4 [<c04d44e1>] do_mount+0x67f/0x6de [<c04d26a2>] ? copy_mount_options+0x78/0xd7 [<c04d45a6>] sys_mount+0x66/0x94 [<c040329f>] sysenter_do_call+0x12/0x28
If you want to follow up via email bump the user digits by one place to the right.