From owner-freebsd-stable@FreeBSD.ORG Thu Feb 17 14:38:05 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8027816A4CE for ; Thu, 17 Feb 2005 14:38:05 +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 B911C43D53 for ; Thu, 17 Feb 2005 14:38:04 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [192.168.252.2] (dhcp150.deepcore.dk [194.192.25.150] (may be forged)) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id j1HEbphq060796; Thu, 17 Feb 2005 15:37:53 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <4214AC1F.8040101@DeepCore.dk> Date: Thu, 17 Feb 2005 15:37:19 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 1.0 (X11/20050116) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Marcus Grando References: <42028F29.1030801@DeepCore.dk> <420A1792.900@DeepCore.dk> <421464C3.2030308@DeepCore.dk> <4214964C.1040103@corp.grupos.com.br> <421497CA.2020904@DeepCore.dk> <4214A99D.4060601@corp.grupos.com.br> In-Reply-To: <4214A99D.4060601@corp.grupos.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.7 cc: "freebsd-stable@freebsd.org" Subject: Re: UPDATE2: ATA mkIII first official patches - please test! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Feb 2005 14:38:05 -0000 Marcus Grando wrote: > Hi >=20 > S=F8ren Schmidt wrote: >=20 >> Hmm, does it work without apic ? without ACPI ? >> And your cabling is correct and spec conformant ? >> The 686A' I have in the lab works just dandy... >=20 > I test all combinations (with/without apic | with/without ACPI), and=20 > problems persist. OK. > It will be that the problem is not with the compatibility of the=20 > controller with my HD? Have you tried other disks on this board ? Have you tried this disk on another board ? Is the disk in a drawer/enclosure of sorts ? > I changed 3 times the cable. I don't think that cable is problem. Depends, you need proper 80 conductor cables no longer than 45cm's, the=20 blue connector goes at the controller end, and the black/grey goes on=20 the master/slave device. ICRC errors are because the checksum on the data does match, which means = that the communication path between disk and controller is=20 malfunctioning. The usual suspect is the cable, but it can also be bad=20 or loose connectors, or a flaky/unstable PSU. --=20 -S=F8ren