Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!crdgw1!sixhub!davidsen
From: davidsen@sixhub.UUCP (Wm E. Davidsen Jr)
Newsgroups: comp.unix.sysv386
Subject: Re: ESIX and RLL contollers
Message-ID: <2255@sixhub.UUCP>
Date: 8 Nov 90 02:55:55 GMT
References: <1990Nov6.234606.5162@thyme.jpl.nasa.gov> <1990Nov7.032130.23769@metro.ucc.su.OZ.AU>
Reply-To: davidsen@sixhub.UUCP (bill davidsen)
Organization: *IX Public Access UNIX, Schenectady NY
Lines: 17

In article <1990Nov7.032130.23769@metro.ucc.su.OZ.AU> glenn@suphys.physics.su.OZ.AU (Glenn Geers) writes:

| I have had no trouble over the last few weeks with my WD1006vsr2 RLL controller.
| I've just added a second drive (an old - from my XT clone - 20 Mb Miniscribe)
| and this is now causing the main drive to lock up. 

  SCO has this same problem, and released a fix for it (although they
labeled it for 1007). I haven't had a lockup in months, so I call it
fixed. Call the vendor and tell them that the setup will run with SCO.
The problem was (reported to me) that when the o/s started a seek on one
drive and a read on the other, that when the interrupt came back the
kernel got confused about which operation was complete.
-- 
bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen)
    sysop *IX BBS and Public Access UNIX
    moderator of comp.binaries.ibm.pc and 80386 mailing list
"Stupidity, like virtue, is its own reward" -me