From: Chris Wedgwood <cw@f00f.org>
To: LKML <linux-kernel@vger.kernel.org>, Linus Torvalds <torvalds@osdl.org>
Subject: [PATCH] i386 reduce spurious interrupt noise
Date: Thu, 2 Sep 2004 12:28:20 -0700 [thread overview]
Message-ID: <20040902192820.GA6427@taniwha.stupidest.org> (raw)
i386 hardware can (and does) see spurious interrupts from time to
tome. Ideally I would like the printk removed completely but this is
probably good enough for now.
Singed-of-By: Chris Wedgwood <cw@f00f.org>
===== arch/i386/kernel/apic.c 1.58 vs edited =====
--- 1.58/arch/i386/kernel/apic.c 2004-08-26 23:30:31 -07:00
+++ edited/arch/i386/kernel/apic.c 2004-09-02 12:19:19 -07:00
@@ -1190,7 +1190,7 @@
6: Received illegal vector
7: Illegal register address
*/
- printk (KERN_INFO "APIC error on CPU%d: %02lx(%02lx)\n",
+ printk (KERN_DEBUG "APIC error on CPU%d: %02lx(%02lx)\n",
smp_processor_id(), v , v1);
irq_exit();
}
===== arch/i386/kernel/i8259.c 1.36 vs edited =====
--- 1.36/arch/i386/kernel/i8259.c 2004-08-23 12:48:32 -07:00
+++ edited/arch/i386/kernel/i8259.c 2004-09-02 12:20:49 -07:00
@@ -226,7 +226,7 @@
* lets ACK and report it. [once per IRQ]
*/
if (!(spurious_irq_mask & irqmask)) {
- printk("spurious 8259A interrupt: IRQ%d.\n", irq);
+ printk(KERN_DEBUG "spurious 8259A interrupt: IRQ%d.\n", irq);
spurious_irq_mask |= irqmask;
}
atomic_inc(&irq_err_count);
next reply other threads:[~2004-09-02 19:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 19:28 Chris Wedgwood [this message]
2004-09-02 19:34 ` William Lee Irwin III
2004-09-02 19:47 ` Chris Wedgwood
2004-09-02 19:52 ` William Lee Irwin III
2004-09-02 19:59 ` Chris Wedgwood
2004-09-02 20:13 ` Nathan Bryant
2004-09-02 19:27 ` Alan Cox
2004-09-02 20:32 ` Chris Wedgwood
2004-09-10 21:23 ` Maciej W. Rozycki
2004-09-10 23:10 ` Chris Wedgwood
2004-09-10 22:21 ` Alan Cox
2004-09-10 23:28 ` Chris Wedgwood
2004-09-11 13:36 ` Alan Cox
2004-09-11 0:14 ` Maciej W. Rozycki
2004-09-11 0:17 ` Chris Wedgwood
2004-09-11 0:33 ` Maciej W. Rozycki
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=20040902192820.GA6427@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®