From owner-freebsd-current@FreeBSD.ORG  Fri Dec 12 07:39:06 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 D312C16A4CE; Fri, 12 Dec 2003 07:39:06 -0800 (PST)
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id A18DE43D2D; Fri, 12 Dec 2003 07:39:04 -0800 (PST)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu
	[152.3.145.30])
	by duke.cs.duke.edu (8.12.10/8.12.10) with ESMTP id hBCFd4qt010003
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 12 Dec 2003 10:39:04 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id hBCFcxvq023018;
	Fri, 12 Dec 2003 10:38:59 -0500 (EST)
	(envelope-from gallatin)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16345.57618.966705.95086@grasshopper.cs.duke.edu>
Date: Fri, 12 Dec 2003 10:38:58 -0500 (EST)
To: sos@freebsd.org
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
cc: current@freebsd.org
Subject: 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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Dec 2003 15:39:06 -0000


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:

atapci0: <Intel ICH UDMA66 controller> port 0xffa0-0xffaf at device 31.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
ata1: at 0x170 irq 15 on atapci0
ata1: [MPSAFE]
<...>
GEOM: create disk ad0 dp=0xc20bc160
ad0: 9779MB <IBM-DPTA-371020> [19870/16/63] at ata0-master UDMA66
acd0: CDROM <ATAPI-CD ROM-DRIVE-56MAX> at ata1-master PIO4
SMP: AP CPU #1 Launched!
ad0: WARNING - READ_DMA UDMA ICRC error (retrying request)
ad0: WARNING - READ_DMA UDMA ICRC error (retrying request)
ad0: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
error=84<ICRC,ABORTED>
ad0: WARNING - READ_DMA UDMA ICRC error (retrying request)
ad0: WARNING - READ_DMA UDMA ICRC error (retrying request)
ad0: FAILURE - READ_DMA status=51<READY,DSC,ERROR>
error=84<ICRC,ABORTED>
Mounting root from ufs:/dev/ad0s1a
setrootbyname failed
ffs_mountroot: can't find rootvp
Root mount failed: 6

Manual root filesystem specification:
  <fstype>:<device>  Mount <device> using filesystem <fstype>
                       eg. ufs:da0s1a
  ?                  List valid disk boot devices
  <empty line>       Abort manual input

mountroot> 


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.

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)


Drew