Xref: utzoo comp.unix.xenix:8695 comp.unix.i386:1388 comp.sys.ibm.pc:38718
Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!eru!luth!sunic!tut!santra!hutcs.hut.fi!hsu
From: hsu@hutcs.hut.fi (Heikki Suonsivu)
Newsgroups: comp.unix.xenix,comp.unix.i386,comp.sys.ibm.pc
Subject: Re: WD1006V-SR2 update
Keywords: WD1006V-SR2
Message-ID: <1989Nov24.114457.27093@santra.hut.fi>
Date: 24 Nov 89 11:44:57 GMT
References: <111056@nstar.UUCP>
Sender: news@santra.hut.fi (Cnews - USENET news system)
Reply-To: hsu@hutcs.hut.fi ()
Organization: Helsinki University of Technology, Finland
Lines: 15

In article <111056@nstar.UUCP> larry@nstar.UUCP (Larry Snyder) writes:
>IO flew compared against the 2372B.   I started having system lockups where
>the LED on the second drive stayed on - and the hard drives appeared "frozen"
>but I could still bring up the shell on the consoles - but nothing else.

If drivers are alive and processes don't hang until they do disk access,
this is same problem I had with 386-2.2L-Microport. This seems to happen
when one hits to a bad block.

Microport 3.0e does work.

-
 Heikki Suonsivu @ 2:504/1 Kuutamokatu 5 A 7/02210 Espoo/FINLAND
..!mcvax!santra!hutcs!hsu  hsu@hutcs.hut.fi
v22bis +358-0-8031121