From owner-freebsd-stable@FreeBSD.ORG Thu Jun 2 08:49:02 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 4984716A41F for ; Thu, 2 Jun 2005 08:49:02 +0000 (GMT) (envelope-from freebsd-current@byrnehq.com) Received: from schubert.byrnehq.com (dsl-33-12.dsl.netsource.ie [213.79.33.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A64F43D48 for ; Thu, 2 Jun 2005 08:49:00 +0000 (GMT) (envelope-from freebsd-current@byrnehq.com) Received: from localhost (mauer.directski.com. [212.147.140.194]) by schubert.byrnehq.com (8.13.3/8.13.3) with ESMTP id j529lLmT076834; Thu, 2 Jun 2005 09:47:23 GMT (envelope-from freebsd-current@byrnehq.com) Date: Thu, 2 Jun 2005 09:48:55 +0100 From: Tony Byrne Organization: ByrneHQ X-Priority: 3 (Normal) Message-ID: <1436791778.20050602094855@byrnehq.com> To: Tony Byrne In-Reply-To: <1148797372.20050601182156@byrnehq.com> References: <1117573047.3095.24.camel@klotz.local> <1684114034.20050601135752@byrnehq.com> <1117645070.1846.8.camel@klotz.local> <1148797372.20050601182156@byrnehq.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ByrneHQ-SA-Hits: 1.455 X-Scanned-By: MIMEDefang 2.51 on 192.168.10.254 Cc: FreeBSD Stable , Tony Byrne , Martin Subject: Re[3]: ATA DMA timeouts X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tony Byrne List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2005 08:49:02 -0000 Martin, TB> We're now at 2 hours uptime and there is no sign of the ATA TB> timeouts. With the newer kernels the first timeout would appear TB> within 5 to 10 minutes of rebooting. I can't see any changes to TB> the ATA code in the interim so I'm curious as to what could have TB> caused this issue. TB> My hardware is Intel ICH5 based with a Western Digital SATA hard-disk. Well it was too good to last. I came in this morning to find a handful of "ad0: TIMEOUT - ..." in the messages file. It looks like the nightly cron jobs trigger it even for kernel and world prior to May 9th. I get the sense that there are less timeouts with the older kernel, but it could be wishful thinking. If your timeouts have really gone away then it's possible that our problem has a different cause to yours. Can anyone else shed some light on this issue? Regards, Tony. -- Tony Byrne