From: "Jan Beulich" <jbeulich@novell.com>
To: "Martin Lorenz" <martin@lorenz.eu.org>
Cc: "Andi Kleen" <ak@suse.de>, <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.19-rc3: more DWARFs and strange messages
Date: Wed, 08 Nov 2006 17:19:15 +0100 [thread overview]
Message-ID: <45521193.76E4.0078.0@novell.com> (raw)
In-Reply-To: <20061031170320.GA6227@gimli>
>>> Martin Lorenz <martin@lorenz.eu.org> 31.10.06 18:03 >>>
>On Tue, Oct 31, 2006 at 05:28:11PM +0100, 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?
>
>config and the requested .o files are attached
>...hoping I diden't loose track of my kernel bilds
>stacktrace will follow ASAP
I'm unable to find anything pointing out the reason for this
misbehavior, and I continue to be unable to reproduce it on my
test systems.
Short of somebody else wanting to try to debug this, perhaps
the only way to get more insight is to add some more debug
printing to the unwinder and/or its callers, which I don't have
time to do immediately.
Jan
next prev parent reply other threads:[~2006-11-08 16:18 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
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 [this message]
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=45521193.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=ak@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox