Have seen this problem with a motherboard with a bad PCI slot, too.
happened with a pci network card in the slot...
CornerNet System Administration
On Mon, 20 Jan 2003, David D. Hagood wrote:
> 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
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to firstname.lastname@example.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jan 23 2003 - 22:00:25 EST