Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!snorkelwacker.mit.edu!stanford.edu!leland.Stanford.EDU!elaine18.Stanford.EDU!dhinds
From: dhinds@elaine18.Stanford.EDU (David Hinds)
Newsgroups: comp.sys.sgi
Subject: Re: (none)
Message-ID: <1991Apr5.181825.24858@leland.Stanford.EDU>
Date: 5 Apr 91 18:18:25 GMT
References: <9104050443.aa04455@VGR.BRL.MIL>
Sender: news@leland.Stanford.EDU (Mr News)
Organization: Stanford University - AIR
Lines: 21

In article <9104050443.aa04455@VGR.BRL.MIL> UNM10B@DBNRHRZ1.BITNET (Rainer Kleinrensing) writes:
>Some messages from our SYSLOG are:
>Apr  2 23:15:00 gt unix: sc0: Unexpected info phase, state 4F phase 36
>Apr  2 23:15:00 gt unix: sc0,4: Resetting SCSI bus: stray interrupt error, phase
>Apr  2 23:15:00 gt grcond[296]: CIO: sc0: Unexpected info phase, state 4F phase
>Apr  2 23:15:00 gt grcond[296]: CIO: sc0,4: Resetting SCSI bus: stray interrupt
>Unfortunately, we didn't receive any user's manual with the exabyte
>drive (we didn't buy it from SGI), so we don't know whether we should
>move a jumper or something similar.

This probably is not your specific problem, but something similar happened
to us when we installed our SGI 8mm drive.  We started getting occasional SCSI
bus errors - I don't think they were the same as yours, though.  Our problem
turned out to be with our SCSI hard drive - there was nothing wrong with the
tape drive.  In our case, doing an "hinv" showed that the SCSI drive thought
it should respond to requests to, I think, 4 different device numbers, but
this hardware problem never showed up until we actually had another SCSI
device.  Was your SCSI drive an SGI product, or did you install it yourself?

 -David Hinds
  dhinds@cb-iris.stanford.edu