Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 18 Mar 1996 19:31:48 -0800 (PST)
From:      Mostyn/Annabella <mrl@teleport.com>
To:        gibbs@freefall.freebsd.org
Cc:        current@freebsd.org, mrl@teleport.com
Subject:   SCSI death in -current with DAT
Message-ID:  <199603190331.TAA04150@linda.teleport.com>

next in thread | raw e-mail | index | archive | help
Hi,

Under current, an ARCHIVE Python DAT (Conner - a modern one, a couple
of months old, is detected to have "variable blocks" and times out
bringing an Adaptec 2940UW to its knees.  Afterwards, the machine
won't even see a disk on reboot (via the reset button) and needs a
power-cycle to reset the controller.

Under 2.1R, the DAT is identified as having fixed 512-byte blocks and
works perfectly!

The DAT is on the non-wide cable on the 2940UW and a wide disk is the
subject of a tar.

A tar cf /dev/rst0 usr was used and the syslog messages during "death"
,using current, are -

st0(ahc0:0:0): timed out in dataout phase, SCSISIGI = 0x48
st0(ahc0:0:0): BUS DEVICE RESET message queued.
st0(ahc0:0:0): timed out in command phase, SCSISIGI = 0x84
ahc0: Issued Channel A Bus Reset #1. 1 SCBs aborted
sd0(ahc0:5:0): UNIT ATTENTION asc:29.2
, retries: 4
st0(ahc0:0:0): timed out in dataout phase, SCSISIGI = 0x0
ahc0: Issued Channel A Bus Reset #2. 1 SCBs aborted
st0(ahc0:0:0): timed out in dataout phase, SCSISIGI = 0x0
ahc0: Issued Channel A Bus Reset #2. 1 SCBs aborted

DEATH

can escape to ddb but nothing else - power cycle required.

This, with a St. Patrick's Day -current.


--> -current boot messages -

 ahc0 <Adaptec 2940 Ultra SCSI host adapter> rev 0 int a irq 11 on pci0:12
 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs
 ahc0 waiting for scsi devices to settle
 (ahc0:0:0): "ARCHIVE Python 28388-XXX 5.45" type 1 removable SCSI 2
 st0(ahc0:0:0): Sequential-Access density code 0x0, variable blocks, write-enabled
						    ^^^^^^^^^^^^^^^
 (ahc0:1:0): "TOSHIBA CD-ROM XM-3701TA 3055" type 5 removable SCSI 2
 cd0(ahc0:1:0): CD-ROM 
 cd0(ahc0:1:0): NOT READY asc:3a,0 Medium not present
 can't get the size
 (ahc0:5:0): "Quantum XP32150W 81HB" type 0 fixed SCSI 2
 sd0(ahc0:5:0): Direct-Access 2050MB (4199760 512 byte sectors)
 sd0(ahc0:5:0): with 3907 cyls, 10 heads, and an average 107 sectors/track
 (ahc0:6:0): "Quantum XP32150W 81HB" type 0 fixed SCSI 2
 sd1(ahc0:6:0): Direct-Access 2050MB (4199760 512 byte sectors)
 sd1(ahc0:6:0): with 3907 cyls, 10 heads, and an average 107 sectors/track

--> 2.1R boot messages -

 ahc0 <Adaptec 2940 Ultra SCSI host adapter> rev 0 int a irq 11 on pci0:12
 de0: enabling 10baseT/UTP port
 ahc0: aic7870 Ultra Wide Channel, SCSI Id=7, aic7870, 255 SCBs
 ahc0 waiting for scsi devices to settle
 (ahc0:0:0): "ARCHIVE Python 28388-XXX 5.45" type 1 removable SCSI 2
 st0(ahc0:0:0): Sequential-Access density code 0x13, 512-byte blocks, write-enabled
						     ^^^^^^^^^^^^^^^
 (ahc0:1:0): "TOSHIBA CD-ROM XM-3701TA 3055" type 5 removable SCSI 2
 cd0(ahc0:1:0): CD-ROM 
 cd0(ahc0:1:0): NOT READY asc:3a,0 Medium not present
 can't get the size
 
 (ahc0:5:0): "Quantum XP32150W 81HB" type 0 fixed SCSI 2
 sd0(ahc0:5:0): Direct-Access 2050MB (4199760 512 byte sectors)
 (ahc0:6:0): "Quantum XP32150W 81HB" type 0 fixed SCSI 2
 sd1(ahc0:6:0): Direct-Access 2050MB (4199760 512 byte sectors)

I could force fixed blocks by hand in st.c but I'd prefer a genuine fix.

Mostyn Lewis



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603190331.TAA04150>