From: Jun Sun <jsun@mvista.com>
To: linux-mips@oss.sgi.com
Subject: A confusing oops dump ...
Date: Thu, 21 Jun 2001 14:07:48 -0700 [thread overview]
Message-ID: <3B326224.DE937DAA@mvista.com> (raw)
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?
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?
Jun
Unable to handle kernel paging request at virtual address 100096e0, epc ==
10000
Oops in fault.c:do_page_fault, line 172:
$0 : 00000000 100015d4 00000001 81e43160
$4 : 00000001 00000001 00000000 8328a680
$8 : 0000308e 00000000 800ba0dc 00000003
$12: 00000010 2ac45e7c 00000000 82f6e039
$16: 0041393c 10003510 000005f0 00000000
$20: 0000308e 00000000 fffffffc 00409350
$24: 00000000 2ab92f10
$28: 83b18000 7fff77f0 10003510 100096e0
epc : 100096e0
Status: 30017c03
Cause : 00008008
Process (pid: 0, stackpage=7fff6000)
Stack: 100096e0 7fff7800 004036f0 004036d4 10003518 7fff6fec 00000000 6f727020
100096e0 7fff6930 7fff7b04 00004dd1 7fff7920 0fb64798 00000000 00000000
00000000 00000000 0fb94020 00000000 00000000 00000000 0fb600cc 00000000
00000000 00000000 00000000 00000000 00000000 0fb60104 0fb600d4 0fb600dc
0fb600e4 00000000 00000000 00000000 0fb600ec 0fb600f4 00000000 00000000
0fb600cc ...
Call Trace:
Code: (Bad address in epc)
next reply other threads:[~2001-06-21 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-21 21:07 Jun Sun [this message]
2001-06-22 19:58 ` A confusing oops dump Martin Michlmayr
-- strict thread matches above, loose matches on Subject: below --
2001-06-21 20:29 Justin Carlson
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=3B326224.DE937DAA@mvista.com \
--to=jsun@mvista.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