From: "Jan Beulich" <jbeulich@novell.com>
To: "Andi Kleen" <ak@suse.de>
Cc: "Martin Bligh" <mbligh@mbligh.org>,
"Andrew Morton" <akpm@osdl.org>,
"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.17-rc1-mm3 dies in LTP on amd64
Date: Thu, 20 Apr 2006 11:41:03 +0200 [thread overview]
Message-ID: <4447734F.76E4.0078.0@novell.com> (raw)
In-Reply-To: <200604181911.13012.ak@suse.de>
>Not very useful. Something double faulted, but it's not on the stack
>[I wonder if the stack walker over double faults is broken. Jan - did you
>ever test that after you redid the walker?]
Maybe not specifically for a double fault, but I'm certain I checked it for some of the IST ones; looking at the code I
also can't see anyting obviously wrong. But clearly, a double fault has its most likely reason being a bad kernel stack
pointer prior to a page (or other) fault. It would therefore be necessary to know the value of the stack pointer as
retrieved from the double fault stack, which with the current display logic is not possible.
Jan
prev parent reply other threads:[~2006-04-20 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 16:59 2.6.17-rc1-mm3 dies in LTP on amd64 Martin Bligh
2006-04-18 17:11 ` Andi Kleen
2006-04-20 9:41 ` Jan Beulich [this message]
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=4447734F.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.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