From owner-freebsd-current@FreeBSD.ORG Sun Dec 28 19:48:19 2003 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 5E59D16A4CE for ; Sun, 28 Dec 2003 19:48:19 -0800 (PST) Received: from moof.zeroth.org (moof.zeroth.org [203.117.131.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id A286643D49 for ; Sun, 28 Dec 2003 19:48:17 -0800 (PST) (envelope-from jclark@metaparadigm.com) Received: from metaparadigm.com (neon.zeroth.org [203.117.131.24]) (authenticated bits=0) by moof.zeroth.org (8.12.9/8.12.9) with ESMTP id hBT3mECg051905; Mon, 29 Dec 2003 11:48:15 +0800 (SGT) (envelope-from jclark@metaparadigm.com) Message-ID: <3FEFA3F9.3040609@metaparadigm.com> Date: Mon, 29 Dec 2003 11:48:09 +0800 From: Jamie Clark User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031107 Debian/1.5-3 X-Accept-Language: en MIME-Version: 1.0 To: Lanny Baron References: <86u14cwqrf.wl@bougainvillea.FromTo.Cc> <3FEF882E.6080800@metaparadigm.com> <3FEF960E.5050906@FreeBSDsystems.COM> In-Reply-To: <3FEF960E.5050906@FreeBSDsystems.COM> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 28 Dec 2003 19:51:16 -0800 cc: current@freebsd.org Subject: Re: SATA disks on 5.2-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: Mon, 29 Dec 2003 03:48:19 -0000 Lanny Baron wrote: > Hi, > What SATA Hard Disks are you using? A pair of Maxtor 6Y160M0 (don't have the exact revision and probe message at hand). I also tried a Seagate ( ATA/ATAPI rev 6 ) with a PATA/SATA dongle. The dongle has sunlink chip - which I think is same as Sil3611. The Seagate was a complete dead duck under -CURRENT - boot hanging with the "missing interrupt" messages. The Maxtors seemed a bit happier but still got the same spurious failure messages during and after boot. I never tried to build a filesystem on them. I can confirm that all of the above devices were happy under Windows (copied about 20 gigs each way for a test) so I guess it is not *completely* broken hardware, although it may fall short of the spec that the BSD drivers expect. I never tried legacy mode with the two SATA channels enabled so I can't comment on that. -Jamie