From owner-freebsd-stable Fri Jul 12 17: 1:16 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1504F37B400 for ; Fri, 12 Jul 2002 17:01:14 -0700 (PDT) Received: from pc1-cove2-4-cust33.bir.cable.ntl.com (pc1-cove2-4-cust33.bir.cable.ntl.com [80.4.78.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FEB343E72 for ; Fri, 12 Jul 2002 17:01:13 -0700 (PDT) (envelope-from ianjhart@ntlworld.com) Received: from ntlworld.com (alpha.private.lan [192.168.0.2]) by pc1-cove2-4-cust33.bir.cable.ntl.com (8.12.3/8.12.3) with ESMTP id g6D01BgA031805 for ; Sat, 13 Jul 2002 01:01:11 +0100 (BST) (envelope-from ianjhart@ntlworld.com) Message-ID: <3D2F6DC6.A5392FF7@ntlworld.com> Date: Sat, 13 Jul 2002 01:01:10 +0100 From: ian j hart X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: "stable@FreeBSD.ORG" Subject: ATA tags and stuff Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I can reproduce the "tags problem", RELENG_4 built today. Also noticed some weird secondary IDE stuff. Are there any ATA patches I don't know about? Is it worth trying CURRENT? Will do anything (legal) to help solve the problem. I've borrowed the box for the weekend, so fire away. Three IBM-DTLA-307075 rescued from backup duties plus one new IC35L080AVVA07-0. [shown with tags off here] ad0: 78533MB [159560/16/63] at ata0-master UDMA100 ad1: 73308MB [148945/16/63] at ata0-slave UDMA100 ad2: 73308MB [148945/16/63] at ata1-master UDMA100 ad3: 73308MB [148945/16/63] at ata1-slave UDMA100 First tried a LEX BN630LT M/B. Installed 4.6-RELEASE, upgraded to STABLE. Set up vinum RAID10 volume. While formating I had systat -vmstat running. Noticed that while the "load" appeared the same on all four disks, ad0 and ad1 were at ~5% busy, ad2 and ad3 were at ~50% busy. I posted somthing similar before (20010807). I've swapped the cables around, same result. Tried different cables, same result. All cables are spec length, don't have any shorter. This is a new board - could be a design fault. So I tried a recent gigabyte board, same result. Set tags on. As soon as I load the vinum volume I get [snip time /kernel] ad2: READ command timeout tag=0 serv=0 - resetting ad2: invalidating queued requests ad2: timeout waiting for cmd=00 s=d0 e=04 ad2: flush queue failed ata1: resetting devices .. ad2: invalidating queued requests ad2: DMA limited to UDMA33, non-ATA66 cable or device ad3: invalidating queued requests done ad2: no request for tag=0 ad2: invalidating queued requests So far only ad2 and ad3 fail. A thought occurs. There could be a master/slave problem with the firmware in the DTLA drives, which is fixed in the IC35. I'll swap the IDE cables on the M/B and see what happens. Maybe I'd better sleep first, I'm rambling. BTW, this is NOT a vinum problem. I get the same problem on normal volumes (but only on ad2 ad3). This is just a *neat* way of loading the drives. -- ian j hart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message