>>> 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? > I've tried with NFSv3 now. With v4 the error normally occur within 5 minutes. The VM is now running for one hour and no soft lockup so far. So I would say it can't be reproduced with v3. > - Have you tried running with stack tracing enabled? > Can you explain this a little bit more please? CONFIG_STACKTRACE=y was already enabled. I've now enabled CONFIG_USER_STACKTRACE_SUPPORT=y CONFIG_NOP_TRACER=y CONFIG_HAVE_FTRACE_NMI_ENTER=y CONFIG_HAVE_FUNCTION_TRACER=y CONFIG_HAVE_FUNCTION_GRAPH_TRACER=y CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST=y CONFIG_HAVE_DYNAMIC_FTRACE=y CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y CONFIG_HAVE_FTRACE_SYSCALLS=y CONFIG_FTRACE_NMI_ENTER=y CONFIG_CONTEXT_SWITCH_TRACER=y CONFIG_GENERIC_TRACER=y CONFIG_FTRACE=y CONFIG_FUNCTION_TRACER=y CONFIG_FUNCTION_GRAPH_TRACER=y CONFIG_FTRACE_SYSCALLS=y CONFIG_STACK_TRACER=y CONFIG_KMEMTRACE=y CONFIG_DYNAMIC_FTRACE=y CONFIG_FTRACE_MCOUNT_RECORD=y CONFIG_HAVE_MMIOTRACE_SUPPORT=y and run echo 1 > /proc/sys/kernel/stack_tracer_enabled But the output is mostly the same in dmesg/ var/log/messages. Can you please guide me how I can enable the stack tracing you need? Thanks! Robert -- 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
