public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David D. Hagood" <wowbagger@sktc.net>
To: AnonimoVeneziano <voloterreno@tin.it>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Spurious 8259A interrupt: IRQ7 ????
Date: Mon, 20 Jan 2003 18:36:51 -0600	[thread overview]
Message-ID: <3E2C9623.60709@sktc.net> (raw)
In-Reply-To: <3E2C8EFF.6020707@tin.it>

AnonimoVeneziano wrote:
> What does it mean this message?
> 
> Of what problem is the signal?

It is most likely a hardware problem.

When a device signals an interrupt, it asserts its interrupt pin. When 
the CPU asks the interrupt controller what device generated the 
interrupt, the interrupt controller tells the CPU.

But if the interrupt line "goes away" before the CPU fetches the vector, 
then the interrupt controller doesn't "know" what IRQ caused the 
interrupt. So the interrupt controller sends an IRQ #7 to the CPU, along 
with setting a bit in the interrupt controller's status register that 
says in effect "this isn't really an IRQ 7, but I have no idea what it 
was. Sorry."

If you have ISA cards in your system, remove them from the system and 
re-insert them (with the power off, of course) - they may have developed 
some oxidization on the card edge connector. You can also try scrubbing 
the card edge with some plain paper (a US dollar bill works even better, 
but you might not have access to dead presidents in Italy.)

Ditto with PCI cards - remove them, polish the connector, then re-insert 
them.



  reply	other threads:[~2003-01-21  0:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-21  0:06 Spurious 8259A interrupt: IRQ7 ???? AnonimoVeneziano
2003-01-21  0:36 ` David D. Hagood [this message]
2003-01-21  1:43   ` Coax
2003-01-21  3:20   ` Alan
2003-01-21  5:22   ` Tupshin Harper
2003-01-21  7:00     ` Paul
2003-01-22 20:06     ` Ville Hallivuori
2003-01-22 20:53       ` Pavel Janík
2003-01-22 21:16       ` AnonimoVeneziano
2003-01-21 13:37   ` AnonimoVeneziano
2003-01-21 13:54     ` Richard B. Johnson
2003-01-21 23:53 ` Tom Vier
2003-01-23 22:14   ` Zsolt Babak
2003-01-23 23:56     ` Herman Oosthuysen
2003-01-24 19:54 ` AnonimoVeneziano
2003-01-24 21:07   ` Herman Oosthuysen

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=3E2C9623.60709@sktc.net \
    --to=wowbagger@sktc.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=voloterreno@tin.it \
    /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