From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 2 23:57:51 2007 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FD2D16A417; Fri, 2 Nov 2007 23:57:51 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from spider.deepcore.dk (cpe.atm2-0-70484.0x50a6c9a6.abnxx16.customer.tele.dk [80.166.201.166]) by mx1.freebsd.org (Postfix) with ESMTP id 04EC913C48E; Fri, 2 Nov 2007 23:57:45 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from ws.local (ws.deepcore.dk [194.192.25.137]) by spider.deepcore.dk (8.13.8/8.13.8) with ESMTP id lA2M3DJf075881; Fri, 2 Nov 2007 23:03:13 +0100 (CET) (envelope-from sos@deepcore.dk) Message-ID: <472B9EA1.6060205@deepcore.dk> Date: Fri, 02 Nov 2007 23:03:13 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: "Arno J. Klaassen" References: <472A548B.50406@lxnt.info> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Cc: Thierry Herbelot , freebsd-hackers@FreeBSD.ORG, Alexander Sabourenkov , "Matthew D. Fuller" , sos@FreeBSD.ORG Subject: Re: Patch RFC: Promise SATA300 TX4 hardware bug workaround. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 23:57:51 -0000 Arno J. Klaassen wrote: > definitely an improvement, but not sufficient (for my setup ) : > > amd64-releng_6 on an ASUS A8V UP (box ran rock-stable > for years i386-releng_5 with same hardware apart TX4 and > drives) > > from dmesg : > > atapci0: port 0xe000-0xe07f,0xd80= 0-0xd8ff mem 0xfbb00000-0xfbb00fff,0xfba00000-0xfba1ffff irq 18 at device= 13.0 on pci0 > ata2: on atapci0 > ata3: on atapci0 > ata4: on atapci0 > ata5: on atapci0 > atapci1: port 0xd400-0xd407,0xd000-0xd003= ,0xc800-0xc807,0xc400-0xc403,0xc000-0xc00f,0xb800-0xb8ff irq 20 at device= 15.0 on pci0 > ata6: on atapci1 > ata7: on atapci1 > atapci2: port 0x1f0-0x1f7,0x3f6,0x170-0x1= 77,0x376,0xfc00-0xfc0f at device 15.1 on pci0 > ata0: on atapci2 > ata1: on atapci2 > > [ ... ] > > ad0: 38166MB at ata0-master UDMA100 > ad6: 476940MB at ata3-master SATA300 > ad12: 305245MB at ata6-master SATA150 > > booting from ad0 and simple gconcat over ad6 and ad12. > > Improvement : I now can fsck /dev/concat/data without > ad6 being detached > > Persistent problem : when I rsync an nfs-mounted disk to /dev/concat/da= ta, > I get after about some Gigs of data have been transfered : > > Nov 2 16:39:55 charlotte kernel: ad6: WARNING - WRITE_DMA UDMA ICRC er= ror (retrying request) LBA=3D268435392 > Nov 2 16:40:50 charlotte kernel: ad6: WARNING - SETFEATURES SET TRANSF= ER MODE taskqueue timeout - completing request directly > Nov 2 16:40:50 charlotte kernel: ad6: WARNING - SETFEATURES SET TRANSF= ER MODE taskqueue timeout - completing request directly > Nov 2 16:40:50 charlotte kernel: ad6: WARNING - SETFEATURES ENABLE RCA= CHE taskqueue timeout - completing request directly > Nov 2 16:40:50 charlotte kernel: ad6: WARNING - SETFEATURES ENABLE WCA= CHE taskqueue timeout - completing request directly > Nov 2 16:40:50 charlotte kernel: ad6: WARNING - SET_MULTI taskqueue ti= meout - completing request directly > Nov 2 16:40:50 charlotte kernel: ad6: TIMEOUT - WRITE_DMA retrying (0 = retries left) LBA=3D268435392 > Nov 2 16:40:50 charlotte kernel: ad6: FAILURE - WRITE_DMA status=3Dff<= BUSY,READY,DMA_READY,DSC,DRQ,CORRECTABLE,INDEX,ERROR> error=3Dff LBA=3D268435392 > Nov 2 16:40:50 charlotte kernel: g_vfs_done():concat/data[WRITE(offset= =3D137438920704, length=3D131072)]error =3D 5 > Nov 2 16:40:50 charlotte kernel: ad6: TIMEOUT - WRITE_DMA48 retrying (= 1 retry left) LBA=3D268435648 > Nov 2 16:40:50 charlotte kernel: ad6: WARNING - WRITE_DMA48 UDMA ICRC = error (retrying request) LBA=3D268435648 > Nov 2 16:40:50 charlotte kernel: ad6: WARNING - SETFEATURES SET TRANSF= ER MODE taskqueue timeout - completing request directly > Nov 2 16:40:50 charlotte kernel: ad6: WARNING - SETFEATURES SET TRANSF= ER MODE taskqueue timeout - completing request directly > Nov 2 16:40:50 charlotte kernel: ad6: WARNING - SETFEATURES ENABLE RCA= CHE taskqueue timeout - completing request directly > Nov 2 16:40:50 charlotte kernel: ad6: WARNING - SETFEATURES ENABLE WCA= CHE taskqueue timeout - completing request directly > Nov 2 16:40:50 charlotte kernel: ad6: WARNING - SET_MULTI taskqueue ti= meout - completing request directly > Nov 2 16:40:50 charlotte kernel: ad6: FAILURE - WRITE_DMA48 timed out = LBA=3D268435648 > Nov 2 16:40:50 charlotte kernel: g_vfs_done():concat/data[WRITE(offset= =3D137439051776, length=3D131072)]error =3D 5 > > ... > > I will test again with "#define PDC_MAXLASTSGSIZE 32*4" (just to see > if that makes a difference) > =20 One thing to try is to loose any geom raid, if raid needed use ataraid=20 instead. I'm shuffeling boards and controllers here to try to reproduce, so far=20 no luck it "just works(tm)", it seems to depend quite heavily on the=20 "right" combination of possibly marginal HW.... -S=F8ren