public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Paubert <paubert@iram.es>
To: Jamie Lokier <jamie@shareable.org>
Cc: "Richard B. Johnson" <root@chaos.analogic.com>,
	Hans-Peter Jansen <hpj@urpla.net>,
	Robert_Hentosh@Dell.com,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: spurious 8259A interrupt
Date: Wed, 24 Mar 2004 16:50:40 +0100	[thread overview]
Message-ID: <20040324155040.GA3822@iram.es> (raw)
In-Reply-To: <20040324152800.GA5758@mail.shareable.org>

On Wed, Mar 24, 2004 at 03:28:00PM +0000, Jamie Lokier wrote:
> Richard B. Johnson wrote:
> > It isn't CPU-specific. It's motherboard glitch specific. If there
> > is ground-bounce on the motherboard or excessive induced
> > coupling, the CPU may occasionally get hit with a logic-level
> > that it "thinks" is an interrupt, even though no controller
> > actually generated it.
> 
> That doesn't seem plausible on an otherwise reliable computer.
> 
> Why would interrupt lines suffer ground-bounce logic glitches yet all
> the data, address and control lines be fine?

Two reasons at least:
- the data/address lines are always driven by a buffer when there
a transfer is taking place, while the interrupt lines are permanently
monitored but most of the time only held by passive pull-ups of a
much higher impedance.

- board designers know that the timing of data and addresses are
critical and take care during the layout. Interrupt lines come last
and are routed where there is room left, after all these are low
frequency signals...

	Regards,
	Gabriel

  reply	other threads:[~2004-03-24 15:59 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16 20:32 spurious 8259A interrupt Robert_Hentosh
2004-03-19 13:06 ` Jamie Lokier
2004-03-19 13:16   ` Russell King
2004-03-19 13:39     ` Jamie Lokier
2004-03-19 14:04       ` Anton Blanchard
2004-03-19 14:56         ` Jamie Lokier
2004-03-19 13:48   ` Richard B. Johnson
2004-03-19 14:39     ` Jamie Lokier
2004-03-21 17:58     ` Hans-Peter Jansen
2004-03-22  9:12       ` Maciej W. Rozycki
2004-03-22 12:29       ` Richard B. Johnson
2004-03-24 15:28         ` Jamie Lokier
2004-03-24 15:50           ` Gabriel Paubert [this message]
2004-03-24 15:57           ` Richard B. Johnson
2004-03-19 13:28 ` Maciej W. Rozycki
2004-03-19 22:01   ` Guennadi Liakhovetski
2004-03-22  9:02     ` Maciej W. Rozycki
2004-03-22 21:16       ` Guennadi Liakhovetski
2004-03-22 22:13         ` Richard B. Johnson
2004-03-22 23:09           ` Guennadi Liakhovetski
2004-03-22 23:38             ` Richard B. Johnson
2004-03-23 10:32               ` Maciej W. Rozycki
2004-03-23 10:42             ` Maciej W. Rozycki
2004-03-23 21:10               ` Guennadi Liakhovetski
2004-03-23 10:29           ` Maciej W. Rozycki
2004-03-23 10:26         ` Maciej W. Rozycki
  -- strict thread matches above, loose matches on Subject: below --
2004-03-16 18:35 Emmanuel Fleury

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=20040324155040.GA3822@iram.es \
    --to=paubert@iram.es \
    --cc=Robert_Hentosh@Dell.com \
    --cc=hpj@urpla.net \
    --cc=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.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