Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!dsuvax!ghelmer
From: ghelmer@dsuvax.uucp (Guy Helmer)
Newsgroups: comp.os.minix
Subject: Re: WD-1006 RLL controller problem, so do I
Message-ID: <1991Jan4.160013.23876@dsuvax.uucp>
Date: 4 Jan 91 16:00:13 GMT
References: <40441@nigel.ee.udel.edu> <124@gem.stack.urc.tue.nl>
Organization: Dakota State University
Lines: 24

In <124@gem.stack.urc.tue.nl> raymond@gem.stack.urc.tue.nl (Raymond Nijssen) writes:

>D98E%DDATHD21.BITNET@cunyvm.cuny.edu (Peter Lautenschlaeger) writes:
>>> [ my info about my WD-1006 controller causing MINIX to hang ]
>> I have the same problem on NEAT 20Mhz 286 machine, this seems to
>> me a common problem. I dimly remember having heard of timing problems
>> with this controller. But I can't remember the answer.

>Since you don't have 2 drives, and Minix doesn't support overlapped seeks
>(like ISC), this infamous WD1006 bug is not likely to be your problem.

I still haven't figured out an answer to my problem.  Some have suggested
that I try putting my machine in slow mode, but that didn't help at all.
I can consistently hang my machine by doing a "cp /dev/hd4 /dev/null",
so I don't do that anymore :-).  The machine seems to lock up
whenever I do lots of fast sequential i/o.  I wonder if MINIX is sending
commands to the controller before it is ready to accept them?

>-Raymond
-- 
Guy Helmer                           helmer@sdnet.bitnet, uunet!dsuvax!ghelmer
work: DSU Computing Services, Business & Education Institute    (605) 256-5315
play: MidIX System Support Services                             (605) 256-2788
postnews: message content ambiguous; spurious information added as required