From: Chris Wedgwood <cw@f00f.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] i386 reduce spurious interrupt noise
Date: Fri, 10 Sep 2004 16:28:26 -0700 [thread overview]
Message-ID: <20040910232826.GA3302@taniwha.stupidest.org> (raw)
In-Reply-To: <1094854872.18282.29.camel@localhost.localdomain>
On Fri, Sep 10, 2004 at 11:21:26PM +0100, Alan Cox wrote:
> On a lot of 2.4 boxes they aren't harmless but thats 2.4 IPI
> messsage handling bugs. People sometimes assume an IPI is delivered
> once - but its not its delivered "at least once" and when you get a
> checksum error like on old dual celerons you get replays.
it sounds like leaving it as KERN_DEBUG is the right thing to do then
> > > > - printk("spurious 8259A interrupt: IRQ%d.\n", irq);
> > > > + printk(KERN_DEBUG "spurious 8259A interrupt: IRQ%d.\n", irq);
> This should really go.
do we want counters for this? what about the APIC case?
next prev parent reply other threads:[~2004-09-10 23:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 19:28 Chris Wedgwood
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 [this message]
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=20040910232826.GA3302@taniwha.stupidest.org \
--to=cw@f00f.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.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®