From: Hans-Peter Jansen <hpj@urpla.net>
To: root@chaos.analogic.com, Jamie Lokier <jamie@shareable.org>
Cc: Robert_Hentosh@Dell.com, Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: spurious 8259A interrupt
Date: Sun, 21 Mar 2004 18:58:07 +0100 [thread overview]
Message-ID: <200403211858.07445.hpj@urpla.net> (raw)
In-Reply-To: <Pine.LNX.4.53.0403190825070.929@chaos>
On Friday 19 March 2004 14:48, Richard B. Johnson wrote:
>
> The IRQ7 spurious is usually an artifact of a crappy motherboard
> design where the CPU "thinks" it was interrupted, but the
> controller didn't wiggle the CPUs INT line.
Thanks for the nice explanation, Richard.
I even see them on my x86_64 box in 64 bit mode. (K8VT800 based)
Furtunately only occasionally.
I thought, AMD took the chance to fix that kind of crap in the new
architecture, but obviously they failed in this respect :-(
Pete
next prev parent reply other threads:[~2004-03-21 17:58 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 [this message]
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
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=200403211858.07445.hpj@urpla.net \
--to=hpj@urpla.net \
--cc=Robert_Hentosh@Dell.com \
--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