Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!aplcen!uakari.primate.wisc.edu!uwm.edu!rpi!brutus.cs.uiuc.edu!psuvax1!rutgers!mcdchg!ddsw1!karl
From: karl@ddsw1.MCS.COM (Karl Denninger)
Newsgroups: comp.unix.i386
Subject: Re: ISC disk driver bug?
Summary: FIX for ISC driver "bug" enclosed!  WD1006V users READ THIS!
	Thanks to dougp@ico (Doug Pintar)
Message-ID: <1989Dec21.204403.2326@ddsw1.MCS.COM>
Date: 21 Dec 89 20:44:03 GMT
References: <654400003@cdp> <6700047@adaptex> <258C899B.28434@paris.ics.uci.edu> <1926@crdos1.crd.ge.COM> <258D393B.1670@paris.ics.uci.edu> <6404@turnkey.gryphon.COM>
Reply-To: karl@mcs.MCS.COM (Karl Denninger)
Organization: Macro Computer Solutions, Inc. - Mundelein, IL
Lines: 46

In article <6404@turnkey.gryphon.COM> jackv@turnkey.gryphon.COM writes:
>In article <258D393B.1670@paris.ics.uci.edu> baxter@ics.uci.edu (Ira Baxter) writes:
> 
>[ ..... discussion of controller problem deleted....]
>
>>..... W1-1,2, handling "latched" mode (unfortunately, the
>>docs *don't* say what this does), and W1-5-6, which disables cache
>>control.  If the cure is disabling the cache, then the point of buying
>>the controller was wasted.  I'm waiting for WD to tell me what
>>"latched" mode does.
> 
>No need to wait for WD, latched mode doesn't do much of anything. It controls
>whether the drive select signal is "latched" or not. For instance, on a 1003 I
>think it is hardwired (not sure but any of them I've seen were set up that
>way). The visible evidence of this mode is that the drive select light on
>the drive last selected will stay on, whereas when its off and no drive is
>selected no drive light will be on.
>
>Exciting, right :-}?

I talked to one of the Interactive Guru's this AM.  He gave me a fix --
which WORKED.  Try this one on for size if you are having problems with 2
drives on a WD1006 series board (specific symptoms - random errors on BOTH
drives during the verify of the second disk):

	In /etc/conf/pack.d/dsk/space.c there is a line which reads:
	
	(CCAP_RETRY | CCAP_ERRCOR), /* capabilities */

Modify this to read:
	
	(CCAP_RETRY | CCAP_ERRCOR | CCAP_NOSEEK), /* capabilities */

Relink your kernel, and reboot.  Presto -- problem solved.

Thanks go to dougp@ico (Doug Pintar); he was the one that put me onto this.

If we can keep getting this kind of good, hard information from ISC we just 
might have to admit that we're impressed with the support.  They certainly
solved this problem for me.  :-)

--
Karl Denninger (karl@ddsw1.MCS.COM, <well-connected>!ddsw1!karl)
Public Access Data Line: [+1 708 566-8911], Voice: [+1 708 566-8910]
Macro Computer Solutions, Inc.		"Quality Solutions at a Fair Price"