From owner-freebsd-stable@FreeBSD.ORG Wed Dec 1 03:35:53 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 8B4D516A4CE for ; Wed, 1 Dec 2004 03:35:53 +0000 (GMT) Received: from vscan01.westnet.com.au (vscan01.westnet.com.au [203.10.1.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1394F43D55 for ; Wed, 1 Dec 2004 03:35:53 +0000 (GMT) (envelope-from christopher@nu.org) Received: from localhost (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 679564FE3F for ; Wed, 1 Dec 2004 11:35:51 +0800 (WST) Received: from vscan01.westnet.com.au ([127.0.0.1]) by localhost (vscan01.westnet.com.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02900-19 for ; Wed, 1 Dec 2004 11:35:51 +0800 (WST) Received: from anembo.nu.org (dsl-202-173-130-73.nsw.westnet.com.au [202.173.130.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by vscan01.westnet.com.au (Postfix) with ESMTP id 03AD96BE37 for ; Wed, 1 Dec 2004 11:35:50 +0800 (WST) Received: from anembo.nu.org (localhost [127.0.0.1]) by anembo.nu.org (8.13.1/8.13.1) with ESMTP id iB13ZkLE064637; Wed, 1 Dec 2004 14:35:46 +1100 (EST) (envelope-from christopher@nu.org) Received: (from cjsv@localhost) by anembo.nu.org (8.13.1/8.13.1/Submit) id iB13ZkC6064636; Wed, 1 Dec 2004 14:35:46 +1100 (EST) (envelope-from christopher@nu.org) Date: Wed, 1 Dec 2004 14:35:46 +1100 (EST) Message-Id: <200412010335.iB13ZkC6064636@anembo.nu.org> X-Authentication-Warning: anembo.nu.org: cjsv set sender to christopher@nu.org using -f From: Christopher Vance To: freebsd-stable@freebsd.org Subject: 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 03:35:53 -0000 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. -- Frustrated in Sydney