From owner-freebsd-current@FreeBSD.ORG Fri Dec 12 15:49:15 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 1936416A4CE; Fri, 12 Dec 2003 15:49:15 -0800 (PST) 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 224E543D32; Fri, 12 Dec 2003 15:49:12 -0800 (PST) (envelope-from sos@spider.deepcore.dk) Received: from spider.deepcore.dk (localhost [127.0.0.1]) by spider.deepcore.dk (8.12.10/8.12.10) with ESMTP id hBCNldtx061637; Sat, 13 Dec 2003 00:47:39 +0100 (CET) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.10/8.12.10/Submit) id hBCNldWS061636; Sat, 13 Dec 2003 00:47:39 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200312122347.hBCNldWS061636@spider.deepcore.dk> In-Reply-To: <16345.57618.966705.95086@grasshopper.cs.duke.edu> To: Andrew Gallatin Date: Sat, 13 Dec 2003 00:47:39 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 X-mail-scanned: by DeepCore Virus & Spam killer v1.3 cc: current@FreeBSD.ORG cc: sos@FreeBSD.ORG Subject: Re: cable detection 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, 12 Dec 2003 23:49:15 -0000 It seems Andrew Gallatin wrote: > > I have a junky machine with a UDMA-33 cable between a UDMA-66 > controller and drives. Using a year old -current, the ATA driver > complains that the cables aren't capable of UDMA66 operation, and > throttles things back to UDMA33. > > Using -current from ~1 week ago, this no longer happens and I get: Hmm, thats because that now I ask the controller for cable info (it should know best) and that apparently fails here... > I realize that this is not a whole lot to go on, but it seems to be > wedged here, and the machine is 3000 miles away, so a verbose boot > will have to wait for people to arrive at the office in CA. :) well, I do have experimental code that throttle back DMA on errs... > I was just wondering if this was a known issue, or if there was a way > to make things gracefully fall back to UDMA33 (aside from disabling > DMA at in the loader, and then using atacontrol to enable it after boot) No, I was under the impression that it worked on the ICH, I'll check docs and code again... -Søren .. but it works under windows!!