Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:1387 comp.os.386bsd.questions:5035 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!doc.ic.ac.uk!uknet!mcsun!sun4nl!fwi.uva.nl!vdlinden From: vdlinden@fwi.uva.nl (Frank van der Linden) Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions Subject: Re: ISA strayintr 7 Date: 12 Sep 1993 18:41:50 GMT Organization: FWI, University of Amsterdam Lines: 26 Distribution: world Message-ID: <26vqhe$chk@mail.fwi.uva.nl> References: <25ufhsINNj6n@charnel.ecst.csuchico.edu> <1993Sep1.162615.5053@prepress.com> NNTP-Posting-Host: carol.fwi.uva.nl To come back on this (old by now) thread: because was backing up my HD, and repartitioning, I decided to give NetBSD 0.9 a try (I used to run 0.1 + pk 0.2.??). It gave me some ISA strayintr 7 too, and always the 'wdc0: extra interrupt' during startup. Now, the messages in itself don't scare me, but it happened twice in two days, that NetBSD hung after a strayintr message. The HD light was on constantly, and it hung. Or no, actually, I could still type some shell internal commands, but as soon as the HD was needed, it was all over. The problem must be in the wd-driver or something. I never had any problems with 386bsd 0.1. I might try FreeBSD next, guess that will work (because it is closer to 0.1 + patchkit). I'll have to find enough floppies to put it on, though.. Apropos bug: there's been some discussion on the com-driver in NetBSD 0.9. I haven't installed any comm-program yet, but I did notice that I had to switch my machine on and off (after halting the system) if I wanted to use the serial ports in DOS, after running NetBSD. Frank -- +----------------------------------------------------------------------------+ | I am not sure what a .signature is for, but my mom told me to make one. | | Frank van der Linden, vdlinden@fwi.uva.nl | +----------------------------------------------------------------------------+