From owner-freebsd-stable@FreeBSD.ORG Fri Jul 1 16:12:18 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 5A92A16A443 for ; Fri, 1 Jul 2005 16:12:18 +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 B5B0B43D48 for ; Fri, 1 Jul 2005 16:12:17 +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 j61HBmva032419; Fri, 1 Jul 2005 17:11:49 GMT (envelope-from freebsd-current@byrnehq.com) Date: Fri, 1 Jul 2005 17:12:13 +0100 From: Tony Byrne Organization: ByrneHQ X-Priority: 3 (Normal) Message-ID: <1148375339.20050701171213@byrnehq.com> To: Dominic Marks In-Reply-To: <200507011700.14321.dom@goodforbusiness.co.uk> References: <200507011534.BBK31161@C2bthomr05.btconnect.com> <200507011700.14321.dom@goodforbusiness.co.uk> 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: alan@cyclopsvision.co.uk, freebsd-stable@freebsd.org Subject: Re[2]: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350 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: Fri, 01 Jul 2005 16:12:18 -0000 Hello Dominic, DM> Do you see them with ATA mkIII as well? I tried the ATA mkIII patches a few weeks ago on one of servers, which was suffering DMA TIMEOUTs, but they made no difference. This problem may only occur with certain combinations of controller and SATA hard drive. For example, I have a workstation with an ICH5 controller which had been frequently emitting TIMEOUT messages when it had a 80Gb 7200k Seagate Barracuda SATA drive installed. As a test this afternoon, I swapped out the Seagate for a new 250Gb Western Digital SATA drive, and installed 5.4 RELEASE. The machine is now in the process of building world, and I've yet to see any TIMEOUTs. Regards, Tony. -- Tony Byrne