From: Keith Owens <kaos@ocs.com.au>
To: Chris Wedgwood <cw@f00f.org>
Cc: Chris Wright <chrisw@osdl.org>,
Coywolf Qi Hunt <coywolf@gmail.com>, Ali Akcaagac <aliakc@web.de>,
linux-kernel@vger.kernel.org
Subject: Re: Kernel OOOPS in 2.6.11.6
Date: Tue, 29 Mar 2005 12:27:01 +1000 [thread overview]
Message-ID: <7326.1112063221@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 28 Mar 2005 18:06:08 PST." <20050329020608.GA4675@taniwha.stupidest.org>
On Mon, 28 Mar 2005 18:06:08 -0800,
Chris Wedgwood <cw@f00f.org> wrote:
>On Mon, Mar 28, 2005 at 04:24:15PM -0800, Chris Wright wrote:
>
>> Imperfect stack trace decoding.
>
>Is this with CONFIG_4K_STACKS? does it happen w/o it?
i386 needs unwind data plus a kernel unwinder to get accurate
backtraces. Without the data and an unwinder, i386 backtraces are best
guess. They often contain spurious addresses, from noise words that
were left on the kernel stack. Nothing to do with CONFIG_4K_STACKS.
next prev parent reply other threads:[~2005-03-29 2:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 11:09 Kernel OOOPS in 2.6.11.6 Ali Akcaagac
2005-03-28 22:44 ` Chris Wright
2005-03-28 22:57 ` Coywolf Qi Hunt
2005-03-28 23:04 ` Chris Wright
2005-03-29 0:12 ` Coywolf Qi Hunt
2005-03-29 0:24 ` Chris Wright
2005-03-29 2:06 ` Chris Wedgwood
2005-03-29 2:27 ` Keith Owens [this message]
2005-03-29 3:12 ` Chris Wedgwood
2005-03-29 0:28 ` Ali Akcaagac
2005-03-29 6:30 ` Nathan Scott
2005-03-29 16:55 ` Christoph Hellwig
2005-03-29 16:59 ` Chris Wright
2005-03-29 17:01 ` Christoph Hellwig
2005-04-01 21:08 ` Ali Akcaagac
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=7326.1112063221@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=aliakc@web.de \
--cc=chrisw@osdl.org \
--cc=coywolf@gmail.com \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.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