From: Nathan Bryant <nbryant@optonline.net>
To: Chris Wedgwood <cw@f00f.org>
Cc: William Lee Irwin III <wli@holomorphy.com>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] i386 reduce spurious interrupt noise
Date: Thu, 02 Sep 2004 16:13:42 -0400 [thread overview]
Message-ID: <41377EF6.4010902@optonline.net> (raw)
In-Reply-To: <20040902194739.GA6673@taniwha.stupidest.org>
Chris Wedgwood wrote:
> On Thu, Sep 02, 2004 at 12:34:54PM -0700, William Lee Irwin III wrote:
>
>
>>Please check printk_ratelimit().
>
>
> I don't want them displayed by default at *all* --- it wakes up the
> monitor on console machines and that's annoying.
>
> You get about 1 or 2 a day --- rate limiting isn't useful, nor is
> reporting them IMO.
Right, spurious interrupts aren't a big deal on i386. They happen now
and then with some devices because some hardware timing tolerances are a
little too tight. See for example sections 5.7.1.3/5.7.4 of the intel
850 chipset databook
(http://developer.intel.com/design/chipsets/datashts/29068702.pdf) :
"6. Upon receiving the second internally generated INTA# pulse, the PIC
returns the interrupt vector. If no interrupt request is present because
the request was too short in duration, the PIC will return vector 7 from
the master controller."
"In both the edge-triggered and level-triggered modes, the IRQ inputs
must remain active until after the falling edge of the first internal
INTA#. If the IRQ input goes inactive before this time, a default IRQ7
vector will be returned."
>
>
> --cw
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2004-09-02 20:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 19:28 [PATCH] i386 reduce spurious interrupt noise 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 [this message]
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=41377EF6.4010902@optonline.net \
--to=nbryant@optonline.net \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=wli@holomorphy.com \
/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