Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!news.uoknor.edu!ns1.nodak.edu!netnews.nwnet.net!news.clark.edu!spool.mu.edu!olivea!decwrl!decwrl!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.questions Subject: Re: The Stray Interrupt Problem (7) under NetBSD ? Date: 1 Feb 1994 18:47:41 GMT Organization: Montana State University - Bozeman MT Lines: 46 Message-ID: <2im84d$ahk@pdq.coe.montana.edu> References: <1994Jan28.222149.12886@sifon.cc.mcgill.ca> <MYCROFT.94Jan30231828@duality.gnu.ai.mit.edu> <2ilr1i$6fl@hrd769.brooks.af.mil> NNTP-Posting-Host: bsd.coe.montana.edu In article <2ilr1i$6fl@hrd769.brooks.af.mil>, Dave Burgess <burgess@hrd769.brooks.af.mil> wrote: >It this example, I would think that a much more likely culprit than random >lpt interrupts would be that the cable in this case was bad/marginal. The interrupt 7's are caused by interrupts that are sent but not received. So, if the wd driver sends out an interrupt but some other driver (or itself) blocks interrupts for too long a time then a stray interrupt is generrated. (It's a stray because no-one claimed it) >For the uninitiated, the only reason that you don't see the stray interrupt >7 warnings when you are using the lpt (versus lpa) driver is because the >lpt driver eats them. That is correct. The lpt driver assumes those interrupts are for it and so it processes the strays. >We could add exactly the same code to the lpa >driver and lose the warnings. No, the lpa driver is the interruptless driver so it doesn't accept interupts. Heck, lately *I've* been getting stray interrupts due to some code that turns off interrupts in the FreeBSD kernel which seem to be fixed now. >This would eliminate a lot of these "My >system is broke because of Stray Interrupts" messages. Stray interrupts are bad things in general because it said you either sent something but blocked it, or should be expecting something you aren't. Most/All of the stray interrupts caused by the WD driver are now fixed in the driver in FreeBSD-current. Bruce Evans worked hard at getting the driver to have the correct timings, and although I didn't test it as thoroughly as I would like (kind of difficult when your main development machine is a SCSI box) Nate -- nate@bsd.coe.montana.edu | FreeBSD core member and all around tech nate@cs.montana.edu | weenie. work #: (406) 994-4836 | Graduating May '94 with a BS in EE home #: (406) 586-0579 | - looking for work in CS/EE field.