From owner-freebsd-stable@FreeBSD.ORG Thu Feb 17 14:01:29 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 0041F16A4CE for ; Thu, 17 Feb 2005 14:01:29 +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 46EAA43D1D for ; Thu, 17 Feb 2005 14:01:28 +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 j1HE1JdX060351; Thu, 17 Feb 2005 15:01:21 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <4214A38F.7020706@DeepCore.dk> Date: Thu, 17 Feb 2005 15:00:47 +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: mark@markdnet.demon.co.uk References: <200502171338.j1HDbwO2060046@spider.deepcore.dk> In-Reply-To: <200502171338.j1HDbwO2060046@spider.deepcore.dk> 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: 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:01:29 -0000 mark@markdnet.demon.co.uk wrote: > sos@DeepCore.dk wrote: >=20 >>Marcus Grando wrote: >> >>>My problem persist... >>> >>>Any other patch? or idea? >> >>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 >=20 > Just an observation, but my Promise ATA-100 controller will drive 1 UDM= A-66 and one UDMA-100 disk fine at UDMA-33 with the cable on the wrong wa= y round (oops) using the previous update. Well, the problem with "wrong way around" is that determining what the=20 cable is fails in unpredictable ways, as long as your transfer rates are = reduced there is no problems. However if a higher transferate is used=20 than the cable is spec'd for you get ICRC errors as this was originally=20 about. --=20 -S=F8ren