*BSD News Article 20256


Return to BSD News archive

Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!uwm.edu!cs.utexas.edu!asuvax!ennews!mcdphx!udc!dacapo.urbana.mcd.mot.com!tcombs
From: tcombs@urbana.mcd.mot.com (Tim Combs)
Subject: Re: wdc0: extra interrupt
Message-ID: <1993Aug30.194740.12928@urbana.mcd.mot.com>
Sender: tcombs@dacapo.urbana.mcd.mot.com (Tim Combs)
Nntp-Posting-Host: dacapo.urbana.mcd.mot.com
Organization: Motorola Computer Group, Urbana Design Center
References:  <1993Aug30.161403.11735@urbana.mcd.mot.com>
Date: Mon, 30 Aug 1993 19:47:40 GMT
Lines: 14

In article <1993Aug30.161403.11735@urbana.mcd.mot.com>, tcombs@dacapo.urbana.mcd.mot.com (Tim Combs) writes:
>I also got the extra interrupt problem while trying to install netbsd 0.9.  I have an ultrastore ESDI
>controller 12F and a 376 megabyte Maxtor Disk.  It's set at 1412 cylinders, 15 heads and, 36 sectors
>per track.  I turned off drive translation and set my BIOS to the above values.
>During installation all goes well until it reaches the point of making the filesystems on the disk.
>It displays the error message: wdc0:extra interrupt and promptly locks up the system.  After
>waiting 15 minutes or so reading the latest Readers Digest with no response (from the system), 
>I rebooted the system.  My DOS partition wasn't scrozzed so I assume, that wasn't overwritten.  I 
looked at the wd.c code and found the offending error message and it seems to be doing ioctl kinds of things to the disk. Any ideas?

I looked closer at the code (it was kind of late last night) and found the error message in the routine
wdintr.  The interrupt routine.  Apparently it is finding the drive already active.  Any hints?

Tim