Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!doc.ic.ac.uk!uknet!pipex!sunic!isgate!veda.is!adam From: adam@veda.is (Adam David) Newsgroups: comp.os.386bsd.bugs Subject: pk0.2.4 wd driver hangs with light on Message-ID: <CCA9Bt.p3@veda.is> Date: 24 Aug 93 21:35:38 GMT Organization: Veda Systems, Iceland Lines: 25 Seagate IDE disk (341+ million bytes), ST-07A IDE controller. disklabel, newfs, fsck were all run correctly and ran without error. Three stray irq7 interrupts are reported each time the machine boots. After mounting the disk I tried ftp'ing a large file to it and after nearly 5 MB it seemed to hang. I tried a few other commands referring to the wd disk (ls, cd, ...) and they all hung and became unkillable. Eventually the whole machine hung after I disconnected the hung sessions and reconnected new sessions a few times via telnet. I had to physically reboot the machine, still all commands referring to the wd disk hung and left the disk light on (ps showed a D+ STAT), except for 'disklabel' and 'newfs'. Three extra stray irq7 interrupts were reported before each time the wd driver hung. OK, so I just newfs'd the disk and started again. Obviously such behaviour is totally unacceptable, so is this fixed anywhere yet? The pk0.2.4 wd.c is supposed to avoid this kind of lockup by using a timeout of 10 seconds. What now? If this is already fixed in NetBSD 0.9 or FreeBSD, is it possible to simply replace the wd.c file from either of these, or is it more complicated than that? -- adam@veda.is