Re: WD 93c33 trouble

[Michael <macallan%NetBSD.org@localhost>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Feb 17, 2009, at 1:35 PM, Stephen M. Rumble wrote:

> > sd0 at scsibus0 target 1 lun 0: <SGI, IBM DORS-32160, WA6A> disk  
> > fixed
>
> This is a problematic drive - see my changes for revision 1.15 of  
> dev/ic/wd33c93.c for more info. With that workaround it ran fine for  
> me, but I don't recall if I ever used it in a system with multiple  
> targets.

That's the one that came with my Indy.

> It could well be unrelated, but hopefully it's a starting point in  
> where to look.

Yeah, google finds numerous problem reports - maybe ARCS knows  
something we don't (yet).
Umm, after reading your comment - I had a similar problem on macppc  
when mesh(4) didn't support synchronous transfers properly. Some IBM  
drives would start negotiating sync on their own and screw up. Many  
have jumpers labeled something like 'TIS' for 'Target Initiated Sync  
negotiation'. Mine doesn't have one but one's labeled 'reserved'.

That doesn't really sound like the problem I have right now though, we  
hang after probing the 1st drive, no matter which one it is.

have fun
Michael

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iQEVAwUBSZsHhspnzkX8Yg2nAQK05AgAusOX4Pzr4iqnH9pWMjIR32C/6byXy/DK
btbwp3QVT7oC6P7VxmzOxwwjwhaTjfNC5Pn9fmqd4Rbol2hXku5iS8dC21ZRAIcF
XRQwEGY/cGAWTTymKvio2GKFClNliRt+DdTBJJzXHOKMwr/WP2hNoAHFd6Ls5ZJV
UVfkgOpdhdVbkDVKVNH4078CPsgpWqH2634jTo4JCWmHIz6yyZJw3y//qrIwdt5F
00LzD4Paeqjhi8uqyNvFDOKu2mBtQ55suHJVuAoAK4jlO8NmtSk04pKgO2klbrHw
2B/Ke6DGEzxKcLnjddYVCrs4kkoErC/CwsHqMVM6tHApdDCUbc0fDA==
=Ehe3
-----END PGP SIGNATURE-----