From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at /usr/src/linux-2.5.30/include/linux/dcache.h:261!
Date: Sat, 10 Aug 2002 11:09:42 +1000 [thread overview]
Message-ID: <8412.1028941782@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Fri, 09 Aug 2002 14:00:37 MST." <3D542D75.7FEA9DDF@zip.com.au>
On Fri, 09 Aug 2002 14:00:37 -0700,
Andrew Morton <akpm@zip.com.au> wrote:
>It would be much more useful if the oops code were to dump the
>text preceding the exception EIP rather than after it, actually.
>I think Keith said that ksymoops supports that.
Not only does ksymoops support it but some architectures already do
this. Mind you, they are not consistent :(
Alpha: Code: 44220001 f4200003 46520400 <a77d9c38> 6b9b4a40 a44803a8 42425401 42c10403 40603401
Arm: Code: e7973108 e1a02423 (e5c42001) e5c43000 e1a02823
If any instruction in the code line is enclosed in <> or () then
ksymoops assumes that the first byte is EIP. Otherwise the first byte
of the line is EIP. Anybody want to update i386/ia64/mips/... oops code
to dump context around the failing instruction? Maximum of 64 bytes in
the code line please.
next prev parent reply other threads:[~2002-08-10 1:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 17:32 kernel BUG at /usr/src/linux-2.5.30/include/linux/dcache.h:261! Badari Pulavarty
2002-08-09 20:54 ` Dave Hansen
2002-08-09 21:00 ` Andrew Morton
2002-08-09 21:22 ` Andries Brouwer
2002-08-09 21:47 ` Patrick Mochel
2002-08-10 1:09 ` Keith Owens [this message]
2002-08-10 8:08 ` Russell King
2002-08-10 8:44 ` Keith Owens
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=8412.1028941782@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--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