Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!boingo.med.jhu.edu!haven.umd.edu!eng.ufl.edu!irl.ise.ufl.edu!greg
From: greg@irl.ise.ufl.edu (Greg O'Rear)
Newsgroups: comp.sys.novell
Subject: Re: ISASISK.DSK / lost interrupts
Message-ID: <1991Jun28.193316.22119@eng.ufl.edu>
Date: 28 Jun 91 19:33:16 GMT
References: <1991Jun27.095030.1669@urz.unibas.ch>
Sender: news@eng.ufl.edu
Reply-To: greg@irl.ise.ufl.edu (Greg O'Rear)
Organization: Industrial Research Lab - Univ. of Florida
Lines: 29

In article <1991Jun27.095030.1669@urz.unibas.ch> infocenter@urz.unibas.ch writes:
>...
>However, on the server I get randomly in time (sometimes nothing for ten 
>minutes, sometimes five times a minute, depending what I am doing) the 
>following message:
>
>   "Interrupt controller detected a lost hardware interrupt"
>...
>2. Is there a driver that solves my problem (if everything is ok, I don't 
>   wonna see error messages!)?

We just got a new machine for our server at the same time we are upgrading
from 2.15C to 3.11.  I ran through the install stuff, accepted all defaults,
and got the thing booted up.  Same as you, I got error number 1.1.140 which
said "Primary interrupt controller detected a lost hardware interrupt" (which
of course was not listed in the manual under P for Primary but I for interrupt.)

I called my hardware vendor and he said another customer had the same thing,
they called Novell and were told that it was because of the server's large
disk size not working with the current ISADISK.NLM.  The vendor said that
Novell were sending a new ISADISK immediately; I'm waiting.

It's distressing to hear all those beeps while loading 3.11 floppies,
especially as the drive is an IDE (no chance of a low-level COMPSURF to
magically fix things).  Good luck to us.
--
Greg O'Rear
Industrial and Systems Engineering Department, University of Florida
Address: O'Rear@ise.ufl.edu