On 08/07/2012 10:50 AM, Joerg Roedel wrote: > On Tue, Aug 07, 2012 at 10:36:31AM -0400, Bryan Schumaker wrote: >> Your stack trace is showing v4 calls on the failing box, those >> definitely shouldn't be happening if you're using v3. Can you double >> check /etc/fstab and /proc/mounts on a working kernel to be sure? > > So the bug is probably (for whatever reason) that the nfs4 path is > called for an nfs3 mount :)
That's what I'm thinking. If you're not using v4, what happens if you turn CONFIG_NFS_V4 off in your .config for the broken machine? I still haven't been able to trigger the bug, even with your .config, so I'm going to keep poking at it. - Bryan > Anyway, I attach /proc/mounts and /etc/fstab from that box running a > v3.5-rc5 kernel (where it works). Thanks. I don't see anything weird in there. You're using the same settings for the other machine, too? > > > Joerg > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
