Re: spurious 8259A interrupt: IRQ7

Thanks. That makes a lot of sense. My machine is a Compaq ProLient 330 G2 server...the nic onboard uses the eepro100 module with redhat. I noticed this build of the eepro module is from '99. I suspect Compaq may have an updated version for use with this server. I will check it out. This is what I think happened. I haven't seen this error until I loaded the Compaq Event Logging Driver & Advanced Server Manager modules. I think since they load during boot, one of them is using the expected NIC interrupt. Here's the log:

Oct 26 12:55:57 staff kernel: cevt:   Compaq Event Logging Driver (rev 3.0.0-CUSTOM)
Oct 26 12:55:57 staff kernel: casm:   Compaq Advanced Server Management Driver (rev 3.0.0-CUSTOM)
Oct 26 12:55:57 staff kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html
Oct 26 12:55:57 staff kernel: eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw saw sw com sg> and oth$
Oct 26 12:55:57 staff kernel: divert: allocating divert_blk for eth0
Oct 26 12:55:57 staff kernel: eth0: OEM i82557/i82558 10/100 Ethernet, 00:08:02:47:D4:06, IRQ 10.
Oct 26 12:55:57 staff kernel:   Board assembly 010101-034, Physical connectors present: RJ45
Oct 26 12:55:57 staff kernel:   Primary interface chip i82555 PHY #1.
Oct 26 12:55:57 staff kernel:   General self-test: passed.
Oct 26 12:55:57 staff kernel:   Serial sub-system self-test: passed.
Oct 26 12:55:57 staff kernel:   Internal registers self-test: passed.
Oct 26 12:55:57 staff kernel:   ROM checksum self-test: passed (0x04f4518b).
Oct 26 12:56:47 staff kernel: spurious 8259A interrupt: IRQ7.

It seems as though the error isn't generated until nearly a minute after the actual module for the nic loads. I will try updating eepro100 and see if the message goes away.

Thx again -

Jim F.

----- Original Message -----

From: Kenneth Goodwin

To: enigma-list redhat com

Sent: Saturday, October 26, 2002 2:03 PM

Subject: RE: spurious 8259A interrupt: IRQ7

A device with part number 8259A, which is a programmable interrrupt controller used with many devices to

interface with the system bus, has generated a unexpected Interrrupt. Asked for service without a real request.

ie. Noise.........

what lies around this line in the log file may give you a clue as to what device is actually generating the

interrrupt. If it only happens at boot time, it is possible that the device driver has a bug in it's

initialization routine that generates a spurious interrrupt to the OS. It should be reported appropriately.

If it happens all the time while the system is running, you have a bad hardware problem or something is

loose or improperly connected. First ID the real source of the interrupt. The 8259A could be on many devices

or it may be on the MB. (more than one present.)

Kenneth Goodwin

Director of IT Operations

Datamark Technology, Inc.

-----Original Message-----
From: enigma-list-admin redhat com [mailto:enigma-list-admin redhat com]On Behalf Of Jim
Sent: Saturday, October 26, 2002 12:06 PM
To: enigma-list redhat com
Subject: spurious 8259A interrupt: IRQ7

Weird.

I'm getting this error on boot and in my kernel log:

Oct 26 10:51:42 staff kernel: spurious 8259A interrupt: IRQ7.

Can someone explain just what this means and how I should go about fixing it?

Thanks,

Jim