From owner-freebsd-scsi Thu Dec 3 07:42:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18667 for freebsd-scsi-outgoing; Thu, 3 Dec 1998 07:42:54 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mushi.colo.neosoft.com (mushi.colo.neosoft.com [206.109.6.82]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA18662 for ; Thu, 3 Dec 1998 07:42:52 -0800 (PST) (envelope-from peter@bonkers.taronga.com) Received: (qmail 4560 invoked from network); 3 Dec 1998 15:42:29 -0000 Received: from bonkers.neosoft.com (HELO bonkers.taronga.com) (206.109.2.48) by mushi.colo.neosoft.com with SMTP; 3 Dec 1998 15:42:29 -0000 Received: (from peter@localhost) by bonkers.taronga.com (8.9.1/8.9.1) id IAA01462 for scsi@freebsd.org; Thu, 3 Dec 1998 08:09:59 -0600 (CST) (envelope-from peter) From: Peter da Silva Message-Id: <199812031409.IAA01462@bonkers.taronga.com> Subject: IBM DCHS woes To: scsi@FreeBSD.ORG Date: Thu, 3 Dec 1998 08:09:58 -0600 (CST) Reply-To: nick@Taronga.COM X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (forwarded from a bounce message for a local user) From: nick@Taronga.COM (Nick Danger) Subject: IBM DCHS woes Reply-To: nick@Taronga.COM I've got this oemed IBM DCHS 34550 that is being naughty. It refuses to operate reliably at synchronous transfers rates and does this regardless of what HBA or OS I'm running it off of. If I instruct the HBA to not negiotate for synchronous transfers it runs flawlessly (albeit inefficiently). I'm under the impression it's a firmware problem. I'm only concerned with it being functional on a FreeBSD-current machine (-current as of late last week). These logs are from earlier but the error is the same. Drive is reported as: Nov 19 21:00:56 engylion /kernel: da1 at ahc0 bus 0 target 2 lun 0 Nov 19 21:00:56 engylion /kernel: da1: Fixed Direct Acce ss SCSI2 device Nov 19 21:00:56 engylion /kernel: da1: 40.0MB/s transfers (20.0MHz, offset 8, 16 bit), Tagged Queueing Enabled Nov 19 21:00:56 engylion /kernel: da1: 4340MB (8888543 512 byte sectors: 64H 32S /T 4340C) Errors begin about five minutes later as I start doing a bunch of simultaneous copies to it: /kernel: (da1:ahc0:0:2:0): SCB 0x5 - timed out while id le, LASTPHASE == 0x1, SCSISIGI == 0x0 /kernel: SEQADDR == 0x8 /kernel: SSTAT1 == 0xa /kernel: (da1:ahc0:0:2:0): Queuing a BDR SCB /kernel: (da1:ahc0:0:2:0): Bus Device Reset Message Sent /kernel: (da1:ahc0:0:2:0): no longer in timeout, status = 34b /kernel: ahc0: Bus Device Reset on A:2. 16 SCBs aborted /kernel: (da1:ahc0:0:2:0): SCB 0xc - timed out while id le, LASTPHASE == 0x1, SCSISIGI == 0x0 /kernel: SSTAT1 == 0xa /kernel: (da1:ahc0:0:2:0): Queuing a BDR SCB /kernel: (da1:ahc0:0:2:0): Bus Device Reset Message Sent /kernel: (da1:ahc0:0:2:0): no longer in timeout, status = 34b /kernel: ahc0: Bus Device Reset on A:2. 15 SCBs aborted /kernel: (da1:ahc0:0:2:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SCS ISIGI == 0x0 /kernel: SEQADDR == 0xb /kernel: SSTAT1 == 0xa /kernel: (da1:ahc0:0:2:0): Queuing a BDR SCB /kernel: (da1:ahc0:0:2:0): Bus Device Reset Message Sent /kernel: (da1:ahc0:0:2:0): no longer in timeout, status = 34b /kernel: ahc0: Bus Device Reset on A:2. 14 SCBs aborted /kernel: (da1:ahc0:0:2:0): READ(06). CDB: 8 d ca f0 80 0 /kernel: (da1:ahc0:0:2:0): ABORTED COMMAND asc:1b,0 /kernel: (da1:ahc0:0:2:0): Synchronous data transfer error /kernel: (da1:ahc0:0:2:0): READ(06). CDB: 8 d ca f0 60 0 /kernel: (da1:ahc0:0:2:0): ABORTED COMMAND asc:1b,0 /kernel: (da1:ahc0:0:2:0): Synchronous data transfer error /kernel: (da1:ahc0:0:2:0): SCB 0xd - timed out while idle, LASTPHASE == 0x1, SCS ISIGI == 0x0 /kernel: SEQADDR == 0x8 /kernel: SSTAT1 == 0xa /kernel: (da1:ahc0:0:2:0): Queuing a BDR SCB /kernel: (da1:ahc0:0:2:0): Bus Device Reset Message Sent /kernel: (da1:ahc0:0:2:0): no longer in timeout, status = 34b /kernel: ahc0: Bus Device Reset on A:2. 13 SCBs aborted I've got oodles and oodles of logs of this. Would someone more SCSI-clueful than I mind telling me if this is something I can try to work around with a quirk entry or if I should just write it off? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message