On 08/07/2012 10:27 AM, Joerg Roedel wrote: > On Tue, Aug 07, 2012 at 10:17:33AM -0400, Bryan Schumaker wrote: >> On 08/07/2012 10:15 AM, Joerg Roedel wrote: >>> Yes, it reproduces pretty reliable here with Ubuntu 11.10 Server on an >>> Intel box with an NFSv3 directory mounted at boot. This is the only box >>> I have seen this so far, probably it depends on the config. I attach the >>> config of the failing box. >> >> Interesting. Are you mounting v4, too? This code shouldn't be >> running for v3... maybe that's why I haven't been able to hit it. > > No, I am not using NFSv4 on the box where the BUG happens. I have > another box mounting the same directory where the BUG does not trigger > with v3.6-rc1. A difference I spotted between the kernels is, that on > the failing box NFS is compiled as a module whereas it is compiled into > the kernel on the box that works fine. Not sure if that has anything to > do with the problem... > 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? My VM has nfs as a module, so I don't think that's the issue... I just started compiling your config to test on my own. > > Joerg > > -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
