From owner-freebsd-stable Tue Oct 10 1:14:45 2000 Delivered-To: freebsd-stable@freebsd.org Received: from atrn.bpa.nu (CPE-144-132-209-248.nsw.bigpond.net.au [144.132.209.248]) by hub.freebsd.org (Postfix) with ESMTP id 2C57337B66C for ; Tue, 10 Oct 2000 01:14:31 -0700 (PDT) Received: from juju.bsn (juju.bsn [192.168.1.5]) by atrn.bpa.nu (8.9.3/8.9.3) with ESMTP id TAA03211; Tue, 10 Oct 2000 19:16:10 +1000 (EST) (envelope-from andy@ska.bsn) Received: (from andy@localhost) by juju.bsn (8.11.0/8.9.3) id e9A8Fcq36402; Tue, 10 Oct 2000 19:15:38 +1100 (EST) (envelope-from andy) Date: Tue, 10 Oct 2000 19:15:38 +1100 From: Andy Newman To: "Brandon D. Valentine" Cc: Warner Losh , Bill Moran , freebsd-stable@FreeBSD.ORG Subject: Re: Anyone using adaptec 29160 Message-ID: <20001010191538.A36348@juju.bsn> Mail-Followup-To: Andy Newman , "Brandon D. Valentine" , Warner Losh , Bill Moran , freebsd-stable@FreeBSD.ORG References: <200010100158.TAA16674@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from bandix@looksharp.net on Mon, Oct 09, 2000 at 10:53:41PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Oct 09, 2000 Brandon D. Valentine wrote: > On Mon, 9 Oct 2000, Warner Losh wrote: > > >In message <39E25DC9.42D0684C@columbus.rr.com> Bill Moran writes: > >: Anyone using an Adaptec 29160 SCSI controller? > > > >I'm using the 19160, the younger brother of the 29160. It works > >great! > > I'm glad Warner is having better luck. I don't know which variant of > the 29160 you are looking at Bill, but I still don't have my two > controllers working. Just a status update for those in the 29160 saga. I have a machine with Via chipset + 29160 + Cheetah drives. Hit the bad firmware thing and got over it. Had troubles with Vinum's RAID 5 - a few PRs point at the issue - but RAID 0 is okay. CVSup'd yesterday to pick up the U160 support in ahc. Build went fine etc... Try bonnie to get a "bonnie-mark" on the array. Got the following... Significant dmesg output... FreeBSD 4.1.1-STABLE #0: Sun Oct 8 10:32:40 EST 2000 ... ahc0: port 0xec00-0xecff mem 0xe2000000-0xe2000fff irq 10 at device 11.0 on pci0 aic7892: Wide Channel A, SCSI Id=7, 32/255 SCBs ... da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 8750MB (17921835 512 byte sectors: 255H 63S/T 1115C) da3 at ahc0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-3 device da3: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da3: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da2: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) da4 at ahc0 bus 0 target 4 lun 0 da4: Fixed Direct Access SCSI-3 device da4: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da4: 70007MB (143374738 512 byte sectors: 255H 63S/T 8924C) During the "writing intelligently" portion of a bonnie run (which I figure is just good sized block output)... (da2:ahc0:0:2:0): SCB 0x74 - timed out in Message-in phase, SEQADDR == 0x146 sg[0] - Addr 0x132e1000 : Length 4096 sg[1] - Addr 0x165a2000 : Length 4096 sg[2] - Addr 0x14f03000 : Length 4096 sg[3] - Addr 0x133a4000 : Length 4096 sg[4] - Addr 0x12e5000 : Length 4096 sg[5] - Addr 0x1a4c6000 : Length 4096 sg[6] - Addr 0x16ce7000 : Length 4096 sg[7] - Addr 0x14b68000 : Length -2147479552 (da2:ahc0:0:2:0): Other SCB Timeout (da3:ahc0:0:3:0): SCB 0x8c - timed out in Message-in phase, SEQADDR == 0x146 sg[0] - Addr 0x16b69000 : Length 4096 sg[1] - Addr 0x123ea000 : Length 4096 sg[2] - Addr 0x15a6b000 : Length 4096 sg[3] - Addr 0xdeec000 : Length 4096 sg[4] - Addr 0x15eed000 : Length 4096 sg[5] - Addr 0xe48e000 : Length 4096 sg[6] - Addr 0x4d8f000 : Length 4096 sg[7] - Addr 0xebb0000 : Length -2147479552 (da3:ahc0:0:3:0): BDR message in message buffer (da3:ahc0:0:3:0): SCB 0x97 - timed out in Message-in phase, SEQADDR == 0x16c sg[0] - Addr 0x13161000 : Length 4096 sg[1] - Addr 0x166e2000 : Length 4096 sg[2] - Addr 0x145c3000 : Length 4096 sg[3] - Addr 0x14104000 : Length 4096 sg[4] - Addr 0x1f585000 : Length 4096 sg[5] - Addr 0x18a86000 : Length 4096 sg[6] - Addr 0x16b67000 : Length 4096 sg[7] - Addr 0x15f68000 : Length 4096 sg[8] - Addr 0x168c9000 : Length 4096 sg[9] - Addr 0x75aa000 : Length 4096 sg[10] - Addr 0x155eb000 : Length 4096 sg[11] - Addr 0xfcac000 : Length 4096 sg[12] - Addr 0x1724d000 : Length 4096 sg[13] - Addr 0xe4ce000 : Length 4096 sg[14] - Addr 0x692f000 : Length 4096 sg[15] - Addr 0xe9f0000 : Length -2147479552 (da3:ahc0:0:3:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 154 SCBs aborted Also of note is that under load the Ethernet can report... xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 120 bytes xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 180 bytes xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 240 bytes xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 300 bytes xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 360 bytes Which I gather is to do with bus hogging, i.e, the 29160. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message