From owner-freebsd-current@FreeBSD.ORG Fri Jan 14 16:44:40 2005 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 E7DC016A4CE for ; Fri, 14 Jan 2005 16:44:40 +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 3F1B643D1D for ; Fri, 14 Jan 2005 16:44:40 +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 j0EGiamU094207; Fri, 14 Jan 2005 17:44:38 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <41E7F6BE.9070308@DeepCore.dk> Date: Fri, 14 Jan 2005 17:43:42 +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: Michael Class References: <41E568CE.9030905@gmx.de> In-Reply-To: <41E568CE.9030905@gmx.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.6 cc: current@freebsd.org Subject: Re: SIL3112 and Maxtor 6Y160M0 SATA Disk: DMA Failure 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, 14 Jan 2005 16:44:41 -0000 Michael Class wrote: > recently I have added a cheap SIL3112 SATA controller in my system. My condolences.. > Unfortunately when I do attach my Maxtor SATA disk to this controller > I do only get DMA errors. This is all on a recent 6.0-CURRENT system > and can be reproduced with a GENERIC kernel. The SiI3112 silicon is so bug ridden its not even funny. I suggest you return that piece of crap to the vendor that sold it to=20 you and get somthing that works. If thats not an option and you have plenty of time, you can try to=20 experiment with all PCI and memory options in your BIOS, maybe you can=20 find a combination that make it work. Beware of silent datacorruption and that sort of thing though... Good luck! -S=F8ren