Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!hpg30a.csc.cuhk.hk!saimiri.primate.wisc.edu!sdd.hp.com!cs.utexas.edu!utnut!utcsri!newsflash.concordia.ca!sifon!homer.cs.mcgill.ca!fox From: fox@cs.mcgill.ca (Colin BRADLEY) Newsgroups: comp.os.386bsd.questions Subject: Re: The Stray Interrupt Problem (7) under NetBSD ? Date: 3 Feb 1994 17:49:01 GMT Organization: SOCS, McGill University, Montreal, Canada Lines: 23 Message-ID: <2irded$aq1@homer.cs.mcgill.ca> References: <MYCROFT.94Jan30231828@duality.gnu.ai.mit.edu> <2ilr1i$6fl@hrd769.brooks.af.mil> <2iokjj$he5@meatball.rwwa.com> NNTP-Posting-Host: binkley In article <2iokjj$he5@meatball.rwwa.com> witr@rwwa.com writes: [stuff deleted] > >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. > Ahrrrm. I think my original problem was a little more than *benign*, since it rendered the machine useless, having effectively hung up the boot cycle when the strayint was found. I suspect you are referring to the _conventional_ problem, in which (I've heard) just writes messages now and then..... Anyhow.... Cheers, Colin. -- Colin Bradley fox@binkley.cs.mcgill.ca Some assembly required.