From: Russell King <rmk@arm.linux.org.uk>
To: Keith Owens <kaos@ocs.com.au>
Cc: 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 09:08:04 +0100 [thread overview]
Message-ID: <20020810090803.A7235@flint.arm.linux.org.uk> (raw)
In-Reply-To: <8412.1028941782@ocs3.intra.ocs.com.au>; from kaos@ocs.com.au on Sat, Aug 10, 2002 at 11:09:42AM +1000
On Sat, Aug 10, 2002 at 11:09:42AM +1000, Keith Owens wrote:
> 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.
In 2.5, I changed ARM to indicate the last word as the EIP (so we get more
context as Andrew Morton suggests.) However, ksymoops now seems to ignore
the '()' !
At some point I plan to check what happens if its the second to last. I
suspect ksymoops is looking for the strings ' (' and ') ', the second of
which obviously doesn't exist.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-08-10 8:04 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
2002-08-10 8:08 ` Russell King [this message]
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=20020810090803.A7235@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.