From owner-freebsd-current@FreeBSD.ORG Fri Oct 29 18:44:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD79316A4CF for ; Fri, 29 Oct 2004 18:44:56 +0000 (GMT) Received: from hobbiton.shire.net (hobbiton.shire.net [166.70.252.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81E5043D54 for ; Fri, 29 Oct 2004 18:44:56 +0000 (GMT) (envelope-from chad@shire.net) Received: from [67.161.247.57] (helo=[192.168.99.66]) by hobbiton.shire.net with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.43) id 1CNbk8-000DBk-4b for freebsd-current@freebsd.org; Fri, 29 Oct 2004 12:44:56 -0600 Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <41828B7A.6060708@poptart.org> References: <41828B7A.6060708@poptart.org> Message-Id: <9F14E1D4-29DA-11D9-A439-003065A70D30@shire.net> From: "Chad Leigh -- Shire.Net LLC" Date: Fri, 29 Oct 2004 12:44:53 -0600 To: freebsd-current@freebsd.org X-Mailer: Apple Mail (2.619) X-SA-Exim-Connect-IP: 67.161.247.57 X-SA-Exim-Mail-From: chad@shire.net Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on hobbiton.shire.net X-Spam-Status: No, score=-0.4 required=5.0 tests=AWL,BAYES_50 autolearn=disabled version=3.0.0 X-Spam-Level: X-SA-Exim-Version: 4.1+cvs (built Mon, 23 Aug 2004 08:44:05 -0700) X-SA-Exim-Scanned: Yes (on hobbiton.shire.net) Subject: Re: ATA problems with current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2004 18:44:56 -0000 On Oct 29, 2004, at 12:27 PM, Jake Scott wrote: > FAILURE - ATA_IDENTIFY timed out I am having a similar problem on 5.2-RC1 with a SiI 3114 controller (being used in regular "ultra" disk mode on a Tyan S2882 dual opteron board) with a 200gb SATA disk from WDC. I also have a Promise add-on board with SATA drives on it that seems to work fine in the same machine. Under 5.2-CURRENT (from mid summer) this FAILURE - ATA_IDENTIFY did not happen, though the drive did not work either with this controller... Previous 5.2-CURRENT (as previously reported here) did have the same problem. It appears (I need to do some more testing) that there has been a regression of some sort... best Chad