Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!sgi!shinobu!odin!anchor!olson
From: olson@anchor.esd.sgi.com (Dave Olson)
Newsgroups: comp.sys.sgi
Subject: Re: Connecting Fuji 2266S
Message-ID: <1991Apr10.054541.16625@odin.corp.sgi.com>
Date: 10 Apr 91 05:45:41 GMT
References: <1991Apr8.220521.1111@utstat.uucp> <4824@dftsrv.gsfc.nasa.gov>
Sender: news@odin.corp.sgi.com (Net News)
Organization: Silicon Graphics, Inc.  Mountain View, CA
Lines: 17

In <4824@dftsrv.gsfc.nasa.gov> merritt@iris613.gsfc.nasa.gov (John H Merritt) writes:

(stuff about explict jumper settings and changes to get the drive to work)

| SC0:Unexpected info phase, state 4F phase 20
| SC0,6:Resetting SCSI bus: stray interrupt error, phase 0x20, state 0x4F

This sounds very much like a bug fixed for 4.0.  There were some sync
mode negotition failures that weren't handled correctly.  It sounds like
the sync mode was disabled, and the driver couldn't handle the way the
drive was saying 'I don't support scsi sync mode'.

--

	Dave Olson

Life would be so much easier if we could just look at the source code.