🚀 go-pugleaf

One of our fileservers is getting the error message:

Primary interrupt controller detected lost hardware interrupt.

The Message manual indicates that this is due to a board asserting an
interrupt and then deasserting it before the microprocessor gets
around to responding (I don't understand how the operating system
could capture an interrupt after the microprocessor lost it, but
that's OK).  It also suggested that we had a card causing the problem.

This problem occurred for a while each time ISADISK would load.  Then
it would only occur when SYS was mounted (we were loading ISADISK 
manually).  Now it waits until the LAN card driver (WDPLUSSV in this
case) loads.  Currently it happens everytime WDPLUSSV loads, at the
same point in the load.  Sometimes WDPLUSSV won't load the first time
(apparently due to the lost interrupt) but it will always load on the
second try.   We don't suspect that the card is a problem because the
same thing happens with an Accton Ethernet card (and different driver,
of course).

Is there a likely failure mechanism of the PC itself that would cause
this problem?  Is there a way to find what interrupt is being lost?

Michael McGinnis                Internet: mcginnis@kuhub.cc.ukans.edu
Academic Computing Center         Bitnet: mcginnis@ukanvax
University of Kansas               Voice: (913)864-0413
Lawrence, KS  66045                  FAX: (913)864-0485

Rust never sleeps.