From: Jeff Angielski <jeff@theptrgroup.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: ppc826x BAD interrupts
Date: 16 Jan 2004 11:02:53 -0500 [thread overview]
Message-ID: <1074268973.4323.13.camel@localhost.localdomain> (raw)
Looking at /proc/interrupts, I see a large number of "BAD" interrups on
both my MPC8260 reference board (2.4.21) and my PPC8266 custom board
(2.4.23). Both use u-boot as the bootloader.
bash-2.05# cat /proc/interrupts
CPU0
24: 0 8260 SIU Edge PCI IRQ demux
33: 2658326944 8260 SIU Edge fenet
40: 32524 8260 SIU Edge uart
41: 0 8260 SIU Edge uart
BAD: 8862006 <<====== this the problem
The source of this count is ppc_spurious_interrupts which is incremented
in the arch/ppc/kernel/irq.c if:
1) there is no interrupt handler installed
2) SIVEC is showing zero (no interrupts pending)
Looking into the problem it would appear that the problem is the later
case and the get_irq() function in ppc8260_pic.c is indeed reading a
zero from the SIVEC.
The questions I have are:
1) Has anybody seen this behavior on their PowerPC platform?
2) Does anybody know why the SIVEC would be showing a zero?
TIA,
Jeff Angielski
The PTR Group
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-01-16 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 16:02 Jeff Angielski [this message]
2004-01-16 16:35 ` ppc826x BAD interrupts Rob Baxter
2004-01-16 20:18 ` Randy Vinson
-- strict thread matches above, loose matches on Subject: below --
2004-01-16 16:29 Muhammad Sarwar
2004-01-16 18:47 ` Jeff Angielski
2004-01-17 3:22 ` Benjamin Herrenschmidt
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=1074268973.4323.13.camel@localhost.localdomain \
--to=jeff@theptrgroup.com \
--cc=linuxppc-dev@lists.linuxppc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).