From owner-freebsd-stable@FreeBSD.ORG Sun May 22 00:36:37 2005 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG 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 163C016A41C; Sun, 22 May 2005 00:36:37 +0000 (GMT) (envelope-from tom.hurst@clara.net) Received: from spork.qfe3.net (spork.qfe3.net [212.13.207.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B19F43D48; Sun, 22 May 2005 00:36:36 +0000 (GMT) (envelope-from tom.hurst@clara.net) Received: from [81.104.55.176] (helo=voi.aagh.net) by spork.qfe3.net with esmtp (Exim 4.50) id 1DZeSI-0003gf-7C; Sun, 22 May 2005 01:36:34 +0100 Received: from freaky by voi.aagh.net with local (Exim 4.44 (FreeBSD)) id 1DZeSH-000MkB-Sw; Sun, 22 May 2005 01:36:33 +0100 Date: Sun, 22 May 2005 01:36:33 +0100 From: Thomas Hurst To: =?iso-8859-1?Q?S=F8ren?= Schmidt Message-ID: <20050522003633.GB57477@voi.aagh.net> Mail-Followup-To: =?iso-8859-1?Q?S=F8ren?= Schmidt , Peter Jeremy , freebsd-stable@FreeBSD.ORG References: <001801c55a14$609720d0$37cba1cd@emerytelcom.com> <20050516195859.GA59189@server.vk2pj.dyndns.org> <042501c55ba7$360fac30$37cba1cd@emerytelcom.com> <20050518194356.GA2129@cirb503493.alcatel.com.au> <08dc01c55d47$d7697100$37cba1cd@emerytelcom.com> <20050520194839.GG2129@cirb503493.alcatel.com.au> <0ce901c55d7d$ee0690b0$37cba1cd@emerytelcom.com> <20050520225230.GJ2129@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Organization: Not much. User-Agent: Mutt/1.5.6i Sender: Thomas Hurst X-RBL-Warning: 81.104.55.176 is in RBL blacklist at dnsbl.sorbs.net cc: Peter Jeremy cc: freebsd-stable@FreeBSD.ORG Subject: Re: 5.4-RC2 freezing - ATA related? 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: Sun, 22 May 2005 00:36:37 -0000 * Søren Schmidt (sos@FreeBSD.ORG) wrote: > No, my only advise is to use the ATA mkIII patches or better yet - > current.. In a similar vein, I'm seeing the same WRITE_DMA timeouts and system lockups using ATA mkIII patches as I did using the standard RELENG_5 driver, on two seperate systems. I'm getting the WRITE_DMA retries on a multi-gmirror Athlon system using a PCI SATA card; the two PATA drives on the system are fine: FreeBSD 5.4-STABLE #0: Thu Apr 28 06:31:53 BST 2005 atapci1: port 0xcc00-0xcc0f,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xbc00-0xbc07 mem 0xe7062000-0xe70621ff irq 11 at device 12.0 on pci0 ad4: 381554MB [775221/16/63] at ata2-master SATA150 ad6: 381554MB [775221/16/63] at ata3-master SATA150 .. ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=401743679 ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=781421759 It seems harmless, but results in writes freezing for several seconds every couple of hundred MB (annoying with 360G of storage as you might imagine). It normally favours a single drive, but seems to bounce between ad4 and 6 for no apparant reason. Replacing the SATA card and cables has no effect. Attempting to drop the drives to PIO with atacontrol doesn't seem to do anything either (they remain at SATA150). The other system where I see the lockups (I used to get READ/WRITE_DMA timeouts with the lockup many moons ago, which seems to have started after a system update, but for the past 6+ months or so I just get the lockup) is an old BP6 (dual Celeron), on two different channels on two different drive: FreeBSD 5.4-STABLE #2: Tue Apr 26 17:59:25 BST 2005 atapci1: port 0xd800-0xd8ff,0xd400-0xd403,0xd000-0xd007 irq 18 at device 19.0 on pci0 atapci2: port 0xe400-0xe4ff,0xe000-0xe003,0xdc00-0xdc07 irq 18 at device 19.1 on pci0 ad4: 76319MB at ata2-master UDMA66 ad6: 114473MB at ata3-master UDMA66 Setting these drives to PIO4 resolves the stability problems (which again only occurs under heavy disk activity, almost always on writes), but makes the system crawl. I'm planning on migrating it to gmirror, which I expect will make it behave more like the Athlon, but obviously I'd like to be able to use DMA reliably without resorting to RAID-1 everywhere. Save me Søren! -- Thomas 'Freaky' Hurst http://hur.st/