From: Robert Wimmer <kernel@tauceti.net>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Avi Kivity <avi@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, bugzilla-daemon@bugzilla.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>, Mel Gorman <mel@csn.ul.ie>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 15709] New: swapper page allocation failure
Date: Mon, 26 Apr 2010 22:25:41 +0200 [thread overview]
Message-ID: <4BD5F6C5.8080605@tauceti.net> (raw)
In-Reply-To: <1272284154.4252.34.camel@localhost.localdomain>
>>> 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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-04-26 20:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15709-10286@https.bugzilla.kernel.org/>
2010-04-08 19:34 ` Andrew Morton
2010-04-08 19:39 ` Avi Kivity
2010-04-08 20:04 ` Michael S. Tsirkin
2010-04-09 10:15 ` Robert Wimmer
2010-04-11 11:03 ` Michael S. Tsirkin
2010-04-12 9:25 ` Robert Wimmer
2010-04-12 11:23 ` Michael S. Tsirkin
2010-04-12 13:50 ` Robert Wimmer
2010-04-12 13:52 ` Michael S. Tsirkin
2010-04-13 8:51 ` Robert Wimmer
2010-04-19 12:55 ` Robert Wimmer
2010-04-19 13:17 ` Michael S. Tsirkin
2010-04-21 11:23 ` kernel
2010-04-21 9:42 ` Michael S. Tsirkin
2010-04-22 11:31 ` kernel
2010-04-22 10:03 ` Michael S. Tsirkin
2010-04-23 5:26 ` Robert Wimmer
2010-04-25 9:18 ` Michael S. Tsirkin
2010-04-25 20:41 ` Robert Wimmer
2010-04-25 20:49 ` Michael S. Tsirkin
2010-04-26 12:15 ` Trond Myklebust
2010-04-26 20:25 ` Robert Wimmer [this message]
2010-04-26 21:04 ` Trond Myklebust
2010-04-26 22:18 ` Robert Wimmer
2010-04-26 23:28 ` Trond Myklebust
2010-04-27 22:56 ` Robert Wimmer
2010-05-03 8:11 ` kernel
2010-05-06 21:19 ` Robert Wimmer
2010-05-06 21:30 ` Trond Myklebust
2010-05-13 21:08 ` Robert Wimmer
2010-05-13 21:13 ` Trond Myklebust
2010-05-14 5:42 ` Robert Wimmer
2010-05-20 7:39 ` kernel
2010-05-25 20:01 ` Robert Wimmer
2010-06-02 11:56 ` kernel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BD5F6C5.8080605@tauceti.net \
--to=kernel@tauceti.net \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=mst@redhat.com \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox