From: Jun Sun <jsun@mvista.com>
To: linux-mips@oss.sgi.com
Subject: CoreHI interrupts on Malta
Date: Fri, 19 Jul 2002 15:38:05 -0700 [thread overview]
Message-ID: <3D3894CD.5000609@mvista.com> (raw)
After shuffling some lines of printk(), etc, I suddenly get the following
panics. Anybody knows what they are? They seems to be recursive, BTW.
If the interrupts really shouldn't happen, we probably should just disable IP5.
Jun
Loading modules:
modprobe: Can't open dependencies file /lib/modules/2.4.19-rc1/modules.dep (No )
CoreHI interrupt, shouldn't happen, so we die here!!!
epc : 80108a00
Status: 1000fc03
Cause : 00802000
badVaddr : 00000000
GT_INTRCAUSE = 43e00009
GT_CPU_ERR_ADDR = 0204000028
CoreHi interrupt in malta_int.c::corehi_irqdispatch, line 285:
$0 : 00000000 7fff62e8 00000000 7fff63e8 7fff6308 83ffff28 00000000 83f3c364
$8 : 00000000 00000000 00000000 00000000 00000000 7fff62c8 00000000 00000000
$16: 7fff63c0 00000018 00000000 10013a88 00000000 ffffffff 00000000 10015188
$24: 00000000 00000018 83ffe000 83ffff30 00000008 801089e8
Hi : 00000000
Lo : 00000020
epc : 80108a00 Not tainted
Status: 1000fc03
Cause : 00802000
Process rcS (pid: 32, stackpage=83ffe000)
Stack: ffffffff 7fff6498 7fff6518 00000000 00000001 00000000 00000000 802c0000
00001062 00000000 00000018 7fff62c8 7fff62e8 00000000 0000fc00 2ad44404
00000000 00000000 00000000 7fff64a0 00000000 00000000 00000000 00000020
00000000 10013a88 00000000 ffffffff 00000000 10015188 00000000 2acb0870
00000010 00000000 2ae22db0 7fff62b0 00000008 2acaec84 00000020 00000000
2acb0884 ...
Call Trace:
Code: afa80034 00021023 afa20018 <afa20020> 40086000 00000000 35080001 390
CoreHI interrupt, shouldn't happen, so we die here!!!
....
next reply other threads:[~2002-07-19 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-19 22:38 Jun Sun [this message]
2002-07-22 8:54 ` CoreHI interrupts on Malta Carsten Langgaard
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=3D3894CD.5000609@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