From owner-freebsd-scsi Mon Apr 3 6:53: 4 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id 1BA3C37B640 for ; Mon, 3 Apr 2000 06:52:54 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.10.0/8.10.0/Kp) with ESMTP id e32F0Rx00372 for ; Sun, 2 Apr 2000 16:00:27 +0100 (BST) Message-ID: <38E76085.9E5BE928@tdx.co.uk> Date: Sun, 02 Apr 2000 16:00:21 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.7 [en-gb] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: scsi@freebsd.org Subject: Problems with 4.0 - CAM when 3.4 was OK? (long post) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi All, I've recently upgraded my 3.4-STABLE box to 4.0-STABLE. The upgrade went fine, except something seems to have gone awry with my SCSI set-up... The machine has 3 x 2940's in it, and one 1542 (not actually used for anything yet). Under 3.4 the system would boot, and run fine... I've got data on most the SCSI drives, I used to backup my NT workstation to them across a 100Mb/FDX link and get good performance (~4-5Mb/sec), and no errors... I'm very sure all the drives etc. are terminated OK - after having spent a lot of money getting decent cables, active termination etc. If I boot a 4.0-STABLE kernel, I get heaps of: " Waiting 4 seconds for SCSI devices to settle de0: enabling 10baseT port (probe15:ahc1:0:0:0): SCB 0xe - timed out in Message-in phase, SEQADDR == 0x157 (probe15:ahc1:0:0:0): Other SCB Timeout (probe16:ahc1:0:1:0): SCB 0xd - timed out in Message-in phase, SEQADDR == 0x157 (probe16:ahc1:0:1:0): BDR message in message buffer (probe16:ahc1:0:1:0): SCB 0xd - timed out in Message-in phase, SEQADDR == 0x157 (probe16:ahc1:0:1:0): no longer in timeout, status = 34b ahc1: Issued Channel A Bus Reset. 15 SCBs aborted Timedout SCB handled by another timeout (probe18:ahc1:0:3:0): SCB 0xd - timed out while idle, SEQADDR == 0xa (probe18:ahc1:0:3:0): Queuing a BDR SCB (probe18:ahc1:0:3:0): no longer in timeout, status = 35b Timedout SCB handled by another timeout (probe15:ahc1:0:0:0): SCB 0xc - timed out while idle, SEQADDR == 0x4a (probe15:ahc1:0:0:0): SCB 12: Immediate reset. Flags = 0x4040 (probe15:ahc1:0:0:0): no longer in timeout, status = 34b ahc1: Issued Channel A Bus Reset. 13 SCBs aborted Timedout SCB handled by another timeout (probe21:ahc1:0:6:0): SCB 0xc - timed out while idle, SEQADDR == 0x9 (probe21:ahc1:0:6:0): Queuing a BDR SCB (probe21:ahc1:0:6:0): no longer in timeout, status = 35b " The box doesn't get any further than this... I've left it for 1/2 an hour before "on the offchance" it would get past all the timeouts, and at least continue with no SCSI drives / missing drives, but it doesn't. I use a 'wired-down' SCSI config (included below), dmesg under 4.0-STABLE shows all the Adaptecs being found OK, " ahc0: port 0xe400-0xe4ff mem 0xffafd000-0xffafdfff irq 17 at device 18.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: port 0xe800-0xe8ff mem 0xffafe000-0xffafefff irq 16 at device 19.0 on pci0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc2: port 0xec00-0xecff mem 0xffaff000-0xffafffff irq 19 at device 20.0 on pci0 ahc2: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs " This happens in SMP or non-SMP mode... The previous 3.4-STABLE config would instead of spewing out the above errors find: " Mar 31 09:26:38 caladan /kernel: Waiting 2 seconds for SCSI devices to settle Mar 31 09:26:38 caladan /kernel: SMP: AP CPU #1 Launched! Mar 31 09:26:38 caladan /kernel: de0: enabling 10baseT port Mar 31 09:26:39 caladan /kernel: da0 at ahc0 bus 0 target 0 lun 0 Mar 31 09:26:39 caladan /kernel: da0: Fixed Direct Access SCSI-2 device Mar 31 09:26:39 caladan /kernel: da0: 10.000MB/s transfers (10.000MHz, offset 8) Mar 31 09:26:39 caladan /kernel: da0: 1042MB (2134305 512 byte sectors: 64H 32S/T 1042C) Mar 31 09:26:39 caladan /kernel: da1 at ahc0 bus 0 target 1 lun 0 Mar 31 09:26:39 caladan /kernel: da1: Fixed Direct Access SCSI-2 device Mar 31 09:26:39 caladan /kernel: da1: 10.000MB/s transfers (10.000MHz, offset 8) Mar 31 09:26:39 caladan /kernel: da1: 1042MB (2134305 512 byte sectors: 64H 32S/T 1042C) Mar 31 09:26:39 caladan /kernel: da2 at ahc0 bus 0 target 2 lun 0 Mar 31 09:26:39 caladan /kernel: da2: Fixed Direct Access SCSI-2 device Mar 31 09:26:39 caladan /kernel: da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled Mar 31 09:26:39 caladan /kernel: da2: 1003MB (2055096 512 byte sectors: 64H 32S/T 1003C) Mar 31 09:26:39 caladan /kernel: da8 at ahc2 bus 0 target 0 lun 0 Mar 31 09:26:39 caladan /kernel: da8: Fixed Direct Access SCSI-2 device Mar 31 09:26:39 caladan /kernel: da8: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled Mar 31 09:26:39 caladan /kernel: da8: 4148MB (8496960 512 byte sectors: 255H 63S/T 528C) Mar 31 09:26:39 caladan /kernel: da9 at ahc2 bus 0 target 1 lun 0 Mar 31 09:26:39 caladan /kernel: da9: Fixed Direct Access SCSI-2 device Mar 31 09:26:39 caladan /kernel: da9: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled Mar 31 09:26:39 caladan /kernel: da9: 4148MB (8496960 512 byte sectors: 255H 63S/T 528C) Mar 31 09:26:39 caladan /kernel: da3 at ahc0 bus 0 target 3 lun 0 Mar 31 09:26:39 caladan /kernel: da3: Fixed Direct Access SCSI-2 device Mar 31 09:26:39 caladan /kernel: da3: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled Mar 31 09:26:39 caladan /kernel: da3: 1003MB (2055096 512 byte sectors: 64H 32S/T 1003C) Mar 31 09:26:39 caladan /kernel: da4 at ahc0 bus 0 target 5 lun 0 Mar 31 09:26:40 caladan /kernel: da4: Fixed Direct Access SCSI-2 device Mar 31 09:26:40 caladan /kernel: da4: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled Mar 31 09:26:40 caladan /kernel: da4: 1021MB (2091144 512 byte sectors: 64H 32S/T 1021C) Mar 31 09:26:40 caladan /kernel: da5 at ahc0 bus 0 target 6 lun 0 Mar 31 09:26:40 caladan /kernel: da5: Fixed Direct Access SCSI-2 device Mar 31 09:26:40 caladan /kernel: da5: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled Mar 31 09:26:40 caladan /kernel: da5: 1021MB (2091144 512 byte sectors: 64H 32S/T 1021C) Mar 31 09:26:40 caladan /kernel: da6 at ahc1 bus 0 target 0 lun 0 Mar 31 09:26:40 caladan /kernel: da6: Fixed Direct Access SCSI-2 device Mar 31 09:26:40 caladan /kernel: da6: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled Mar 31 09:26:40 caladan /kernel: da6: 4148MB (8496960 512 byte sectors: 64H 32S/T 4148C) " Before anyone jumps and says "Hmmm.. Seagate ST34371W with firmware 0202 isn't tested / is known 'rogue'" - I know... I've argued with Seagate who refuse to do anything for me with these drives, so I'm stuck with them... They worked fine under 3.4, I'd expect them to under 4.0 as well :) The kernel config I use to wire down the above is: " device ahc device ahc0 device ahc1 device ahc2 device scbus0 at ahc0 device scbus1 at ahc1 device scbus2 at ahc2 device da0 at scbus0 target 0 device da1 at scbus0 target 1 device da2 at scbus0 target 2 device da3 at scbus0 target 3 device da4 at scbus0 target 5 device da5 at scbus0 target 6 device da6 at scbus1 target 0 device da7 at scbus1 target 1 device da8 at scbus2 target 0 device da9 at scbus2 target 1 " Any help / info or suggestions gratefully received, as it is - I can only use the machine with the IDE's (under the new 'ad' drivers) - but these work fine, as did the SCSI once :) Regards, Karl Pielorz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message