On Sun, 2010-04-25 at 23:49 +0300, Michael S. Tsirkin wrote: > So, it's an NFS-related regression, which is consistent with the bisect > results. I guess someone who knows about NFS will have to look at it... > BTW, you probably want to label the bug as regression. > > On Sun, Apr 25, 2010 at 10:41:59PM +0200, Robert Wimmer wrote: > > I've added CONFIG_KALLSYMS and CONFIG_KALLSYMS_ALL > > to my .config. I've uploaded the dmesg output. Maybe it > > helps a little bit: > > > > https://bugzilla.kernel.org/attachment.cgi?id=26138 > > > > - Robert > > That last trace is just saying that the NFSv4 reboot recovery code is crashing (which is hardly surprising if the memory management is hosed). The initial bisection makes little sense to me: it is basically blaming a page allocation problem on a change to the NFSv4 mount code. The only way I can see that possibly happen is if you are hitting a stack overflow. So 2 questions: - Are you able to reproduce the bug when using NFSv3 instead? - Have you tried running with stack tracing enabled? Cheers Trond -- 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
