From: "Justin Carlson" <carlson@sibyte.com>
To: linux-mips@oss.sgi.com
Subject: Re: A confusing oops dump ...
Date: Thu, 21 Jun 2001 13:29:31 -0700 [thread overview]
Message-ID: <01062113294906.00778@plugh.sibyte.com> (raw)
On Thu, 21 Jun 2001, you wrote:
> I got the following oops dump during a stress load, which I cannot make any
> sense out of it. The most confusing part is that the status register
> indicates program was running in kernel (KSU bits) while the $epc points to a
> userland address. How could this be ever possible at hardware level?
It's very possible at the hardware level...kernel mode enables access to
several segments; it doesn't disable mapped accesses. I don't think it should
ever happen in linux, but there's nothing in the hardware that prevents this.
>
> The only possible explanation is perhaps those saved registers were corrupted
> between when the exception happens and core dumps, but so unlikely .... *sigh*
>
> Any insight?
You've got a TLBL exception, and va doesn't match epc, so
presumably the processor thinks it was a load and not an ifetch that triggered
this. It also follows that the processor thinks it found a valid instruction
at 0x10000. If this is reproducable and the chip allows it, try dumping out
the icache when you hit this, see if 0x10000 really appears in there...
-Justin
next reply other threads:[~2001-06-21 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 20:29 Justin Carlson [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-21 21:07 A confusing oops dump Jun Sun
2001-06-22 19:58 ` Martin Michlmayr
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=01062113294906.00778@plugh.sibyte.com \
--to=carlson@sibyte.com \
--cc=linux-mips@oss.sgi.com \
/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