From owner-freebsd-current@FreeBSD.ORG Mon Dec 15 12:00:55 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 5637016A4F0; Mon, 15 Dec 2003 12:00:55 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id E876B43D2D; Mon, 15 Dec 2003 12:00:53 -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 hBFK0rqt027191 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Dec 2003 15:00:53 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id hBFK0mGn030582; Mon, 15 Dec 2003 15:00:48 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16350.4848.244536.768751@grasshopper.cs.duke.edu> Date: Mon, 15 Dec 2003 15:00:48 -0500 (EST) To: sos@FreeBSD.ORG In-Reply-To: <200312122347.hBCNldWS061636@spider.deepcore.dk> References: <16345.57618.966705.95086@grasshopper.cs.duke.edu> <200312122347.hBCNldWS061636@spider.deepcore.dk> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: current@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: Mon, 15 Dec 2003 20:00:55 -0000 Soren Schmidt writes: > > > 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... OK, it wasn't pilot error. A correctly built kernel also fails to operate in UDMA33 mode on this box. If I enable DMA, I get tons of UDMA errors when writing. Reading seems fine: # atacontrol mode 0 UDMA33 PIO4 Master = UDMA33 Slave = BIOSPIO # dd if=/boot/kernel.new/kernel of=/dev/null bs=64k 88+1 records in 5770939 bytes transferred in 0.323945 secs (17814568 bytes/sec) # mount /usr ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) ad0: FAILURE - WRITE_DMA status=51 error=84 # ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request) ad0: FAILURE - WRITE_DMA status=51 error=84 # atacontrol mode 0 PIO4 PIO4 Master = PIO4 Slave = BIOSPIO # # umount /usr # fsck /usr <...> Verbose dmesg at http://www.myri.com/staff/gallatin/atadmesg Like I said before, this box is a peice of junk cobbled together from spare parts. Its possible that a jumper is set incorrectly on the disk or something. Howeever, it worked perfectly with the old kernel, as of last January. Drew