From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <jbeulich@novell.com>
Cc: "Martin Lorenz" <martin@lorenz.eu.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc3: more DWARFs and strange messages
Date: Tue, 31 Oct 2006 18:28:52 +0100 [thread overview]
Message-ID: <200610311828.52980.ak@suse.de> (raw)
In-Reply-To: <454787AB.76E4.0078.0@novell.com>
On Tuesday 31 October 2006 17:28, Jan Beulich wrote:
> Can you perhaps get us arch/i386/kernel/{entry,process}.o,
> .config, and (assuming you can reproduce the original problem)
> the raw stack dump obtained with a sufficiently high kstack=
> option?
WARN_ON unfortunately doesn't dump the raw stack at all (maybe that
should be fixed)
-Andi
next prev parent reply other threads:[~2006-10-31 17:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-28 20:01 2.6.19-rc3: more DWARFs and strange messages Martin Lorenz
2006-10-31 14:31 ` Andi Kleen
2006-10-31 16:08 ` Martin Lorenz
2006-10-31 16:28 ` Jan Beulich
2006-10-31 17:28 ` Andi Kleen [this message]
2006-11-01 15:27 ` Martin Lorenz
2006-11-02 9:37 ` Jan Beulich
2006-11-02 9:48 ` Martin Lorenz
[not found] ` <20061031170320.GA6227@gimli>
2006-11-02 10:56 ` Jan Beulich
2006-11-08 16:19 ` Jan Beulich
2006-11-06 10:54 ` Adrian Bunk
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=200610311828.52980.ak@suse.de \
--to=ak@suse.de \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@lorenz.eu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.