From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Ian Kent <raven@themaw.net>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Pointer to info on decoding oops messages
Date: Wed, 26 Nov 2003 07:17:09 -0800 [thread overview]
Message-ID: <20031126071709.2a0b43c8.rddunlap@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0311262140230.3356-100000@raven.themaw.net>
On Wed, 26 Nov 2003 21:41:18 +0800 (WST) Ian Kent <raven@themaw.net> wrote:
|
| The subject says it all.
|
| Any suggestions please.
Unless the instruction pointer register is scrogged, you get
some registers, some stack data, the code bytes at the next
instruction pointer, and some backtrace symbols.
These are mostly self-explanatory.
However, I'm guessing that you want help with the _cause_ of
an oops, not just with decoding the oops messages.
Anyway, here's where I pointed out some basic info recently:
http://marc.theaimsgroup.com/?l=linux-kernel&m=106433590230743&w=2
and
http://marc.theaimsgroup.com/?l=linux-kernel&m=106434159306658&w=2
--
~Randy
MOTD: Always include version info.
next prev parent reply other threads:[~2003-11-26 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 13:41 Pointer to info on decoding oops messages Ian Kent
2003-11-26 15:17 ` Randy.Dunlap [this message]
2003-11-26 15:39 ` Pat LaVarre
2003-11-27 1:36 ` Ian Kent
2003-11-30 20:33 ` Randy.Dunlap
2003-12-01 5:51 ` Ian Kent
2003-11-27 1:54 ` Ian Kent
2003-12-01 15:12 ` Randy.Dunlap
2003-12-02 1:20 ` Ian Kent
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=20031126071709.2a0b43c8.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=raven@themaw.net \
/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