Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!decwrl!nic.hookup.net!swrinde!cs.utexas.edu!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!rwwa.com!not-for-mail From: witr@rwwa.com (Robert Withrow) Newsgroups: comp.os.386bsd.questions Subject: Re: The Stray Interrupt Problem (7) under NetBSD ? Date: 2 Feb 1994 11:32:51 -0500 Organization: R.W. Withrow Associates Lines: 19 Message-ID: <2iokjj$he5@meatball.rwwa.com> References: <1994Jan28.222149.12886@sifon.cc.mcgill.ca> <MYCROFT.94Jan30231828@duality.gnu.ai.mit.edu> <2ilr1i$6fl@hrd769.brooks.af.mil> Reply-To: witr@rwwa.com NNTP-Posting-Host: meatball.rwwa.com In article <2ilr1i$6fl@hrd769.brooks.af.mil>, burgess@hrd769.brooks.af.mil (Dave Burgess) writes: |> It seems to me that it is a complete red herring. It is, from everything |> I have ever seen here, a completely bogus warning and should be set by |> a define in the kernel source (IMHO). Again, verily so, again and again, I say, yet again.... This problem is caused by buggy driver code, code that causes the hardware to assert and then remove an irq incorrectly, without the appropriate arbitration, etc.. This can either be *Fixed*, by fixing the code that does this, or *Ignored*, since it is basically a benign problem. But do not be confused that the latter is the same as fixing the problem. -- Robert Withrow, Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM R.W. Withrow Associates, 21 Railroad Ave, Swampscott MA 01907-1821 USA