From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question regarding ERR in /proc/interrupts.
Date: Wed, 12 Jan 2005 11:31:24 -0800 [thread overview]
Message-ID: <41E57B0C.30905@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0501121410360.11524@p500>
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
Justin Piszcz wrote:
> Is there anyway to log each ERR to a file or way to find out what caused
> each ERR?
>
> For example, I know this is the cause of a few of them:
> spurious 8259A interrupt: IRQ7.
>
> But not all 20, is there any available option to do this?
Are you sure about that?
MOTD: what kernel version?
2.6.10 (and probably all) prints such message one time for each
"spurious" IRQ, sets a flag for that IRQ, and then doesn't
print such message for that IRQ any more (i.e., so that
log isn't spammed). Each distinct spurious IRQ should be
logged (one time). If you want more, you'll need to patch
a source file and rebuild the kernel (attached, for i8259
PIC, not for APIC, since that's what you seem to have).
> $ cat /proc/interrupts
> CPU0
> 0: 887759057 XT-PIC timer
> 1: 3138 XT-PIC i8042
> 2: 0 XT-PIC cascade
> 5: 5811 XT-PIC Crystal audio controller
> 9: 265081861 XT-PIC ide4, eth1, eth2
> 10: 9087912 XT-PIC ide6, ide7
> 11: 837707 XT-PIC ide2, ide3
> 12: 13854 XT-PIC i8042
> 14: 63373075 XT-PIC eth0
> NMI: 0
> ERR: 20
--
~Randy
[-- Attachment #2: irq_err_msg.patch --]
[-- Type: text/x-patch, Size: 749 bytes --]
linux-2610-bk13
Print all spurious IRQs. (!)
Signed-off-by: Randy Dunlap <rddunlap@osdl.org>
diffstat:=
arch/i386/kernel/i8259.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
diff -Naurp ./arch/i386/kernel/i8259.c~irq_err ./arch/i386/kernel/i8259.c
--- ./arch/i386/kernel/i8259.c~irq_err 2004-12-24 13:35:28.000000000 -0800
+++ ./arch/i386/kernel/i8259.c 2005-01-12 11:28:44.233785256 -0800
@@ -225,7 +225,7 @@ spurious_8259A_irq:
* At this point we can be sure the IRQ is spurious,
* lets ACK and report it. [once per IRQ]
*/
- if (!(spurious_irq_mask & irqmask)) {
+ /* if (!(spurious_irq_mask & irqmask)) */ {
printk(KERN_DEBUG "spurious 8259A interrupt: IRQ%d.\n", irq);
spurious_irq_mask |= irqmask;
}
next prev parent reply other threads:[~2005-01-12 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 19:12 Question regarding ERR in /proc/interrupts Justin Piszcz
2005-01-12 19:31 ` Randy.Dunlap [this message]
2005-01-12 19:52 ` Justin Piszcz
2005-01-12 20:11 ` Randy.Dunlap
2005-01-12 20:16 ` linux-os
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=41E57B0C.30905@osdl.org \
--to=rddunlap@osdl.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.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