From owner-freebsd-current@FreeBSD.ORG Sat Nov 29 23:00:52 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 E9BF116A4CE for ; Sat, 29 Nov 2003 23:00:52 -0800 (PST) Received: from sirius.firepipe.net (sirius.firepipe.net [69.13.116.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F5ED43FE0 for ; Sat, 29 Nov 2003 23:00:52 -0800 (PST) (envelope-from will@csociety.org) Received: by sirius.firepipe.net (Postfix, from userid 1000) id B96F4177C5; Sun, 30 Nov 2003 02:00:51 -0500 (EST) Date: Sun, 30 Nov 2003 02:00:51 -0500 From: Will Andrews To: current@freebsd.org Message-ID: <20031130070051.GN431@sirius.firepipe.net> Mail-Followup-To: current@freebsd.org References: <20031130045604.GM431@sirius.firepipe.net> <1070174954.68747.162.camel@shumai.marcuscom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1070174954.68747.162.camel@shumai.marcuscom.com> User-Agent: Mutt/1.4.1i Subject: Re: Western Digital WD360GD SATA disk on -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: Sun, 30 Nov 2003 07:00:53 -0000 On Sun, Nov 30, 2003 at 01:49:14AM -0500, Joe Marcus Clarke wrote: > I have a host controller with the same chipset. I was having frequent > data corruption problems, so I asked about it on current@ a few days > ago. so@ offered a patch (which has now been comitted), but it didn't > help. Bottom line, he said to get a Promise SATA card. Since I don't > want to mess around with this anymore, I went to Amazon, and ordered > one. In looking at this output, I doubt the patch would even affect you > since you're using the new hardware revision. > > For more details, check the archives for current@ for a thread with the > subject, "Recent ATA drivers giving problems with SATA." Yeah, that's what I figured. When I looked at the change, the fix only appears to affect rev 0x00, but my SiI3112A is 0x02. :( Well, I can tell you that people aren't gonna be happy when their brand new motherboard that comes with SiI SATA builtin doesn't work with their SATA disks (or well, just this one?). Since SiI's are so cheap (and fairly common), I'd consider this a showstopper as far as SATA goes. This thing used to work, it should be fixed. Besides, I simply don't have the money to spend on another SATA controller for my main workstation just so it can run up-to-date -CURRENT. :( Regards, -- wca