From owner-freebsd-stable@FreeBSD.ORG Wed Dec 1 04:52:40 2004 Return-Path: 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 8CA9616A4CE for ; Wed, 1 Dec 2004 04:52:40 +0000 (GMT) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6E6E43D49 for ; Wed, 1 Dec 2004 04:52:39 +0000 (GMT) (envelope-from Mykel@mWare.ca) Received: from [10.100.104.31] (unknown [66.96.18.6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ox.eicat.ca (Postfix) with ESMTP id 14DDFC941; Tue, 30 Nov 2004 23:52:39 -0500 (EST) Message-ID: <41AD4E00.5060707@mWare.ca> Date: Tue, 30 Nov 2004 23:52:16 -0500 From: Mykel User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040618 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christopher Vance References: <200412010335.iB13ZkC6064636@anembo.nu.org> In-Reply-To: <200412010335.iB13ZkC6064636@anembo.nu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: FAILURE - WRITE_DMA timed out X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Dec 2004 04:52:40 -0000 Christopher Vance wrote: >When I use SATA disks heavily on a 5.3-R machine (Athlon) with the >SiI3512 disk controller, I get frequent (sometimes one every 1-5 >minutes) WRITE_DMA timed out messages (with different blocks and both >disks). > >It also panics with more than one kind of panic, and sometimes doesn't >even get to finish the background fsck from the previous panic before >dying again. > >Given that both disks get the WRITE_DMA messages, and the one with the >OS on didn't have any problems when used with a VIA controller in a >different machine, I tend to think it's either the controller or the >software driving it. > >Would I have any joy upgrading along 5-STABLE, perhaps after I move >the disk back to the machine that works, or won't that make any >difference? (As in, are there any relevant ata changes since then?) > >I've already tried setting both hw.ata.ata_dma and hw.ata.wc to 0, but >I still get these timeouts. > I don't have any solutions for you, but I'm curious to know what kind of drives you're using... apparently SiI 3114s aren't so good with bridged (PATA<->SATA) connections, and Seagates are mostly native... On my setup (SiI3112+Seagate), I get WRITE_DMA timeo's a few times a day. Never had panics as result of the SATA tho. atapci1@pci0:13:0: class=0x018001 card=0x02509005 chip=0x31121095 rev=0x02 hdr=0x00 vendor = 'Silicon Image Inc (Was: CMD Technology Inc)' device = 'SiI 3112 SATARaid Controller' class = mass storage ATA channel 2: Master: ad4 ATA/ATAPI rev 6 Slave: no device present I don't even use it very heavily, it's *just* for my .oggs. Nothing else. It sucks. We're presently looking at 3Ware and others for a heavy duty network setup we're doing... hoping we can make the SiIs work instead of dropping a few grand on 3Wares... :\ but I'm not confident the SiIs are good for anything important. Myke