From: erich@wubios.wustl.edu (Erich Schraer)
Subject: Exabyte problem on 4.1.2
Organization: Division of Biostatistics, WUMS, St. Louis, MO
Date: Wed, 7 Oct 1992 13:48:35 GMT

I accidentally sent this to the wrong newgroup yesterday, so if you
already saw it, I apologize.

I recently attempted to upgrade our Sun 4/360 from SunOS 4.1.1 to 4.1.2.
Unfortunately after I did this, and reconfigured the kernel, I found
that our Exabyte EXB-8200 tape drive had stopped working.  Each time an
attempt was made to access it, the computer would ultimately crash, not
always immediately, but usually within a few minutes.

The first time the crash happened was the next time a daily backup was
done, two days later.  The daily backup is performed by a crontab script
in the wee hours of the morning.  These messages were displayed.

    Sep 29 00:00:07 wubios vmunix: st1:  format change failed
    Sep 29 01:05:59 wubios vmunix: st1:  I/O request timeout
    Sep 29 01:05:59 wubios vmunix:  csr= 0x140f  bcr= 0  tcr= 0x4
    Sep 29 01:05:59 wubios vmunix:  cbsr= 0x0 (BUS FREE)  cdr= 0x0  mr= 0x0  bsr= 0x0
    Sep 29 01:05:59 wubios vmunix:  target= 4, lun= 0    DMA addr= 0x0  count= 0 (0)
    Sep 29 01:05:59 wubios vmunix:  cdb=    19  1  0  0  0  0
    Sep 29 01:05:59 wubios vmunix:  last phase= 0x8d (Cmd complete MSG)   0
    Sep 29 01:05:59 wubios vmunix:  last phase= 0xc (STATUS)   0
    Sep 29 01:05:59 wubios vmunix:  last phase= 0x82 (Identify MSG)   0   0
    Sep 29 01:05:59 wubios vmunix:  last phase= 0x8b (Reselect)   0
    Sep 29 01:05:59 wubios vmunix:  last phase= 0x8c (Disconnect MSG)   0
    Sep 29 01:05:59 wubios vmunix:  last phase= 0x83 (Save ptr MSG)   0   57344
    Sep 29 01:05:59 wubios vmunix:  last phase= 0x40 (DATA OUT)   8192
    Sep 29 01:05:59 wubios vmunix:  last phase= 0x8 (COMMAND)   10
    Sep 29 01:05:59 wubios vmunix: panic: iinactive
    . . . crash and reboot messages . . .

Each subsequent time I attempted to use the Exabyte, the `st1:  format
change failed' message, though not the others, was displayed before the
computer crashed.

This Sun 4/360 has two SCSI host adapters, an onboard SCSI-ESP host
adapter (sm0) and a SCSI-3 host adapter (si8):

    controller      sm0 at obio ? csr 0xfa000000 priority 2
    . . .
    controller      si8 at vme24d16 ? csr 0x204000 priority 2 vector siintr 0x41

The Exabyte (st1) is on the second controller, si8, along with 3 disk
drives and a CD-ROM drive:

    tape            st1 at si8 drive 32 flags 1 # si8 - Target: 4, Unit: 0

As a result of this and some other problems, I had to quickly restore
the old operating system, where the Exabyte functions again.  However I
am planning on trying to upgrade again, so I would like to find out why
the Exabyte seems to be incompatible with 4.1.2, and what I can do to
fixe the problem.  If anyone has any insight into this, their input would
be greatly appreciated.  Thanks.

				--Erich
--
  / Erich Schraer                               St. Louis, MO  63110 \
 /  Division of Biostatistics                 erich@wubios.wustl.edu  \
 \  Washington University School of Medicine    Voice: (314)362-3681  /
  \ 660 S. Euclid Ave., Box 8067                  Fax: (314)362-2693 /