From owner-freebsd-current@FreeBSD.ORG Wed Dec 1 18:28:42 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 CA4B516A4CE for ; Wed, 1 Dec 2004 18:28:42 +0000 (GMT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 053EC43D1F for ; Wed, 1 Dec 2004 18:28:42 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id iB1ISU7V023665; Wed, 1 Dec 2004 19:28:32 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <41AE0D42.6070503@DeepCore.dk> Date: Wed, 01 Dec 2004 19:28:18 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Erik Trulsson References: <3BE1BF5E-4249-11D9-9F7A-000A95A9A574@nordahl.net> <20041201153946.GA16872@bewilderbeast.blackhelicopters.org> <20041201164134.GA58263@falcon.midgard.homeip.net> In-Reply-To: <20041201164134.GA58263@falcon.midgard.homeip.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: freebsd-current@freebsd.org cc: 'Frode Nordahl' cc: Daniel Eriksson Subject: Re: Got rid of my SiI3112A 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: Wed, 01 Dec 2004 18:28:42 -0000 Erik Trulsson wrote: > On Wed, Dec 01, 2004 at 10:39:46AM -0500, Michael W. Lucas wrote: >=20 >>On Mon, Nov 29, 2004 at 10:40:41PM +0100, Daniel Eriksson wrote: >> >>>Frode Nordahl wrote: >>> >>> >>>>But as things are today, I think it would be best to remove=20 >>>>support for=20 >>>>SiI3112A. Especially since the general attitude towards it is=20 >>>>"it's too=20 >>>>broke, we don't want to waste any more time on it". >>>> >>>>Attempting to use it in a 5.3-RELEASE or 6-CURRENT system will most=20 >>>>likelly make your system crash and burn, and make your data=20 >>>>unrecoverable beyond repair. >>> >>>I will have to agree with Frode on this one. I recently put -CURRENT o= n a >>>machine with an ASUS mobo that had a SiL 3112 controller. Hooking up t= wo >>>250GB WD discs to it quickly resulted in timeouts, followed by some st= range >>>messages from geom_stripe (used it to stripe the two discs), followed = by >>>filesystem corruption and panics. >> >>Does anyone know if Soren has one of these controllers? >> >>Getting him a poorly-supported controller is the first step towards >>getting it fixed. >=20 >=20 > He probably has one. Otherwise I don't think he would write > commit-messages like this one for sys/dev/ata/ata-chipset.c: > ---- > revision 1.50 > date: 2003/12/08 09:22:20; author: sos; state: Exp; lines: +3 -1 > More errata fixing for the SiI3112A disaster chip: >=20 > Serialize access to the SATA channels, the chip messes up if > both channels are used at the same time. >=20 > The SiI3112 hereby takes the price as the most crappy SATA chip in > existance by a significant amount. >=20 > My advise to our userbase is to avoid this chip like the plague... > ---- >=20 >=20 > I take it that it is not so much a matter of this controller being > poorly supported, as of this being a poor controller. BINGO!! --=20 -S=F8ren