From: wael showair <showair2003@yahoo.com>
To: linuxppc-dev@ozlabs.org
Subject: what is /proc/interrupts & /proc/irq/*/spurious mean?
Date: Sun, 7 Jun 2009 23:15:17 -0700 (PDT) [thread overview]
Message-ID: <23918722.post@talk.nabble.com> (raw)
Hi All,
i have a board shipped with Linux kernel 2.6.27.
i have some problems in interrupts but while i was gathering some info about
the interrupts on my board by
cat /proc/interrupts
CPU0
16: 2525 OpenPIC Level enet_tx
17: 5606 OpenPIC Level enet_rx
18: 0 OpenPIC Level enet_error
21: 3 OpenPIC Level fsldma-channel
22: 3 OpenPIC Level fsldma-channel
23: 3 OpenPIC Level fsldma-channel
25: 3 OpenPIC Level fsldma-channel
26: 461 OpenPIC Level serial
27: 0 OpenPIC Level i2c-mpc
48: 4 OpenPIC Level phy_interrupt
50: 0 OpenPIC Edge DSP-A
52: 11 OpenPIC Edge DSP-B
54: 0 OpenPIC Level FPGA
BAD: 0
actually i m interested in IRQ number 52.
from the previous command: it seems to me OpenPIC has received 11 interrupt
from the device namely DSP-B& this interrupt is edge triggered. Is it
correct?
Also i use:
cat /proc/irq/52/spurious
count 11
unhandled 0
last_unhandled 0 ms
but actually i dont understan its meaning?
does it mean that i received 11 spurious interrupt? i expect this because
the name of the file is spurious.
what does the field unhandled mean?
thanks for ur help.
--
View this message in context: http://www.nabble.com/what-is--proc-interrupts----proc-irq-*-spurious-mean--tp23918722p23918722.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.
reply other threads:[~2009-06-08 6:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=23918722.post@talk.nabble.com \
--to=showair2003@yahoo.com \
--cc=linuxppc-dev@ozlabs.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).