From: Zhang Fuxin <fxzhang@ict.ac.cn>
To: "linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: 8259 spurious interrupt (IRQ1,IRQ7,IRQ12..)
Date: Tue, 18 Sep 2001 18:33:35 +0800 [thread overview]
Message-ID: <200109181034.f8IAYIe27614@oss.sgi.com> (raw)
hi,all
I have finally been able to get a copy of sgi cvs code:).Now I have
changed my p6032 code to use new[time,pci,irq] code and it seems a
lot cleaner.But still problems.
I keep seeing spurious interrupt when starting xwindows.And
sometimes without x. If the machine is doing heavy io(e.g.,unzip &
untar mozilla source) when I startx,it will probably enter an
endless loop of spurious interrupt or lead to unaligned instruction
access shortly after(with epc=0x1,ra=0x1) and die.
I have seen spurious IRQ1,IRQ7 and IRQ12,and the endless loop case
is IRQ12--ps2 mouse interrupt.
Can somebody give me a clue? What I know is that 8259 may generate
spurious IRQ7 & IRQ15. But how can the others happen,buggy hw?And
what may cause a kernel unaligned instruction access?
My hw is p6032 rev.B eval board with idtRC64474 cpu.
BTW,is that current code has no support for different PCI & CPU
address space?In p6032 default setting,PCI memory address 0 is
CPU physical address 0x10000000,and main memory is 0-0x10000000
for CPU,but 0x80000000-0x90000000 for pci. So I have to change
ioremap,virt_to_bus & bus_to_virt. I think this problem should
exist in many nonpc hw,could you point me a clean way?
Thanks in advance.
Regards
Zhang Fuxin
fxzhang@ict.ac.cn
next reply other threads:[~2001-09-18 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 10:33 Zhang Fuxin [this message]
2001-09-18 12:16 ` 8259 spurious interrupt (IRQ1,IRQ7,IRQ12..) Gleb O. Raiko
2001-09-18 17:09 ` Jun Sun
-- strict thread matches above, loose matches on Subject: below --
2001-09-19 8:37 Zhang Fuxin
2001-09-19 19:39 ` Jun Sun
[not found] <200109191747.KAA12583@messenger.mvista.com>
2001-09-20 17:07 ` Jun Sun
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=200109181034.f8IAYIe27614@oss.sgi.com \
--to=fxzhang@ict.ac.cn \
--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 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.