Date: Sun, 10 Mar 2002 22:40:58 -0500 From: Karl Heller <kheller2@mac.com> To: freebsd-questions@FreeBSD.ORG Subject: SCSI timeouts during dumps to AIT Message-ID: <p05100301b8b1d7ac549c@[192.168.1.9]>
next in thread | raw e-mail | index | archive | help
--============_-1196304390==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
FreeBSD 4.5 Release, custom kernel with external AIT2 SDX-500C drive.
I have an adaptec 2940UW connected to the following:
sa0 at ahc1 bus 0 target 5 lun 0
sa0: <SONY SDX-500C 0108> Removable Sequential Access SCSI-2 device
sa0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit)
da1 at ahc1 bus 0 target 0 lun 0
da1: <SEAGATE ST39173WC 5698> Fixed Direct Access SCSI-2 device
da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled
da1: 8192MB (16777216 512 byte sectors: 255H 63S/T 1044C)
da2 at ahc1 bus 0 target 1 lun 0
da2: <SEAGATE ST32171W 0484> Fixed Direct Access SCSI-2 device
da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled
da2: 2049MB (4197584 512 byte sectors: 255H 63S/T 261C)
The SDX is external with a 3M cable. *Anytime* I do dumps or tar to
the device I get these errors:
sa0:ahc1:0:5:0): SCB 0x18 - timed out
ahc1: Dumping Card State in Data-out phase, at SEQADDR 0x7d
ACCUM = 0x0, SINDEX = 0x8, DINDEX = 0x8f, ARG_2 = 0x6
HCNT = 0x0
SCSISEQ = 0x12, SBLKCTL = 0x2
DFCNTRL = 0x3c, DFSTATUS = 0x6d
LASTPHASE = 0x0, SCSISIGI = 0x14, SXFRCTL0 = 0xa0
SSTAT0 = 0x0, SSTAT1 = 0x2
STACK == 0x99, 0x190, 0x160, 0x0
SCB count = 130
Kernel NEXTQSCB = 42
Card NEXTQSCB = 5
QINFIFO entries: 5 54 11 10
Waiting Queue entries:
Disconnected Queue entries:
OUTFIFO entries:
Sequencer Free SCB List: 9 2 0 12 7 11 10 15 8 6 1 5 4 13 3
Pending list: 10, 11, 54, 5, 24
Kernel Free SCB list: 38 59 1 26 58 44 31 69 20 51 56 39 16 3 66 27 9 6 2 50 47
37 23 4 49 8 21 35 30 17 32 25 19 46 14 22 43 13 28 0 12 15 18 45 68 7 55 34 41
67 53 57 33 29 36 48 40 52 64 120 63 62 61 60 79 78 77 76 75 74 73 72
71 70 89 8
8 87 86 85 84 83 82 81 80 99 98 97 96 95 94 93 92 91 90 109 108 107 106 105 104
103 102 101 100 119 118 117 116 115 114 113 112 111 110 129 128 127 126 125 124
123 122 121 65
Untagged Q(5): 24
sg[0] - Addr 0x4770000 : Length 4096
sg[1] - Addr 0xd2d1000 : Length 4096
sg[2] - Addr 0x1dd2000 : Length 2048
(sa0:ahc1:0:5:0): no longer in timeout, status = 34b
ahc1: Issued Channel A Bus Reset. 5 SCBs aborted
(sa0:ahc1:0:5:0): WRITE FILEMARKS. CDB: 10 0 0 0 2 0
(sa0:ahc1:0:5:0): UNIT ATTENTION asc:29,0
(sa0:ahc1:0:5:0): Power on, reset, or bus device reset occurred
(sa0:ahc1:0:5:0): failed to write terminating filemark(s)
(sa0:ahc1:0:5:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM
command to
clear this state.
I know this tape drive works fine under Solaris 2.7 on an Ultra 5.
Any ideas as to how to correct this problem? I glanced at the news
archives and saw similar problems under heavy disk IO loads with
previous version of FreeBSD from a few years ago.
Please respond to the email address in this post as I do not
subscribe to the list.
Karl
--
--
--============_-1196304390==_ma============
Content-Type: text/html; charset="us-ascii"
<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>SCSI timeouts during dumps to
AIT</title></head><body>
<div><br></div>
<div><br>
FreeBSD 4.5 Release, custom kernel with external AIT2 SDX-500C
drive.<br>
I have an adaptec 2940UW connected to the following:<br>
<br>
sa0 at ahc1 bus 0 target 5 lun 0<br>
sa0: <SONY SDX-500C 0108> Removable Sequential Access SCSI-2
device<br>
sa0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit)</div>
<div>da1 at ahc1 bus 0 target 0 lun 0</div>
<div>da1: <SEAGATE ST39173WC 5698> Fixed Direct Access SCSI-2
device<br>
da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged
Queueing Enabled<br>
da1: 8192MB (16777216 512 byte sectors: 255H 63S/T 1044C)<br>
da2 at ahc1 bus 0 target 1 lun 0<br>
da2: <SEAGATE ST32171W 0484> Fixed Direct Access SCSI-2
device<br>
da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged
Queueing Enabled<br>
da2: 2049MB (4197584 512 byte sectors: 255H 63S/T 261C)<br>
<br>
The SDX is external with a 3M cable. *Anytime* I do dumps
or tar to the device I get these errors:<br>
<br>
sa0:ahc1:0:5:0): SCB 0x18 - timed out<br>
ahc1: Dumping Card State in Data-out phase, at SEQADDR 0x7d<br>
ACCUM = 0x0, SINDEX = 0x8, DINDEX = 0x8f, ARG_2 = 0x6<br>
HCNT = 0x0<br>
SCSISEQ = 0x12, SBLKCTL = 0x2<br>
DFCNTRL = 0x3c, DFSTATUS = 0x6d<br>
LASTPHASE = 0x0, SCSISIGI = 0x14, SXFRCTL0 = 0xa0<br>
SSTAT0 = 0x0, SSTAT1 = 0x2<br>
STACK == 0x99, 0x190, 0x160, 0x0<br>
SCB count = 130<br>
Kernel NEXTQSCB = 42<br>
Card NEXTQSCB = 5<br>
QINFIFO entries: 5 54 11 10<br>
Waiting Queue entries:<br>
Disconnected Queue entries:<br>
OUTFIFO entries:<br>
Sequencer Free SCB List: 9 2 0 12 7 11 10 15 8 6 1 5 4 13 3<br>
Pending list: 10, 11, 54, 5, 24<br>
Kernel Free SCB list: 38 59 1 26 58 44 31 69 20 51 56 39 16 3 66 27 9
6 2 50 47<br>
37 23 4 49 8 21 35 30 17 32 25 19 46 14 22 43 13 28 0 12 15 18 45 68 7
55 34 41<br>
67 53 57 33 29 36 48 40 52 64 120 63 62 61 60 79 78 77 76 75 74 73 72
71 70 89 8<br>
8 87 86 85 84 83 82 81 80 99 98 97 96 95 94 93 92 91 90 109 108 107
106 105 104<br>
103 102 101 100 119 118 117 116 115 114 113 112 111 110 129 128 127
126 125 124<br>
123 122 121 65<br>
Untagged Q(5): 24<br>
sg[0] - Addr 0x4770000 : Length 4096<br>
sg[1] - Addr 0xd2d1000 : Length 4096<br>
sg[2] - Addr 0x1dd2000 : Length 2048<br>
(sa0:ahc1:0:5:0): no longer in timeout, status = 34b<br>
ahc1: Issued Channel A Bus Reset. 5 SCBs aborted<br>
(sa0:ahc1:0:5:0): WRITE FILEMARKS. CDB: 10 0 0 0 2 0<br>
(sa0:ahc1:0:5:0): UNIT ATTENTION asc:29,0<br>
(sa0:ahc1:0:5:0): Power on, reset, or bus device reset occurred<br>
(sa0:ahc1:0:5:0): failed to write terminating filemark(s)<br>
(sa0:ahc1:0:5:0): tape is now frozen- use an OFFLINE, REWIND or MTEOM
command to<br>
clear this state.<br>
<br>
<br>
I know this tape drive works fine under Solaris 2.7 on an Ultra
5.<br>
<br>
Any ideas as to how to correct this problem? I glanced at
the news archives and saw similar problems under heavy disk IO loads
with previous version of FreeBSD from a few years ago.</div>
<div><br></div>
<div><br></div>
<div> Please respond to the email address in this post as I do
not subscribe to the list.</div>
<div><br></div>
<div>Karl</div>
<div><tt>-- </tt></div>
<div><br></div>
<x-sigsep><pre>--
</pre></x-sigsep>
</body>
</html>
--============_-1196304390==_ma============--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05100301b8b1d7ac549c>