*BSD News Article 15140


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!sdd.hp.com!nigel.msen.com!yale.edu!yale!mintaka.lcs.mit.edu!ai-lab!hal.gnu.ai.mit.edu!not-for-mail
From: mycroft@hal.gnu.ai.mit.edu (Charles Hannum)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: strayintr ff
Date: 26 Apr 1993 00:15:48 -0400
Organization: dis
Lines: 26
Message-ID: <1rfnlk$1aen@hal.gnu.ai.mit.edu>
References: <C5yoHF.1uI@raistlin.udev.cdc.com> <1rduhiINNggl@gap.caltech.edu>
NNTP-Posting-Host: hal.ai.mit.edu


In article <1rduhiINNggl@gap.caltech.edu> glt@cco.caltech.edu (Greg
Tanaka) writes:
>
> pbd@runyon.cim.cdc.com (Paul Dokas) writes:
>
>>    ISA strayintr 1ff
>>    ISA strayintr 1ff
>>    ISA strayintr 1ff
>>    ISA strayintr ff
>>    Too many ISA strayintr not logging any more
>
> I didn't get a new mother board, I just upgraded to NetBSD.

As has been mentioned before, this is caused by a controller asserting
an interrupt line and dropping it before the 8259 has processed it; the
message is displayed because there is no device on that interrupt
number.

386BSD dealt with this by simply ignoring it.  NetBSD displays these
messages (for now) to indicate that there is a problem.

-- 
 \  /   Charles Hannum, mycroft@ai.mit.edu
 /\ \   PGP public key available on request.  MIME, AMS, NextMail accepted.
Scheme  White heterosexual atheist male (WHAM) pride!