Date: Mon, 24 Sep 2001 15:02:31 -0700 (PDT) From: Justin Kolb <jkolb@nutzy.net> To: freebsd-gnats-submit@FreeBSD.org Subject: i386/30801: ata UMDA problem Message-ID: <200109242202.f8OM2VH74080@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 30801 >Category: i386 >Synopsis: ata UMDA problem >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Sep 24 15:10:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Justin Kolb >Release: 4.4 >Organization: >Environment: FreeBSD wakko.nutzy.net 4.4-RELEASE FreeBSD 4.4-RELEASE #0: Tue Sep 18 11:57:08 PDT 2001 murray@builder.FreeBSD.org:/usr/src/sys/compile/GENERIC i386 >Description: ASUS P5A (UDMA 33 support) + Western Digital WD136AA (UDMA 66/33 drive) + 40 PIN cable Large number of ICRC errors followed by a drop down to PIO4 mode. UDMA mode 2 is successfully detected in the bios for the drive during a verbose boot. Attempts to prove it was a hardware/setup problem involved many tests with combinations of the following things: 1.) Switching between AUTO DMA and forced DMA in the BIOS 2.) Setting UDMA 33 on the drive (wasn't set in earlier tests). 3.) Swapping different 40-pin cables 4.) Running full Western Digitial diagnostic suite on drive (all OK) Note I also had this problem under 4.3 (I believe the error message has changed though). >How-To-Repeat: >Fix: Setting sysctl hw.atamodes to force PIO mode at startup, this still results in a few ICRC errors prior to the execution of this command during bootup. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200109242202.f8OM2VH74080>