From drs@rucus.ru.ac.za  Tue Aug 13 16:09:10 2002
Return-Path: <drs@rucus.ru.ac.za>
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4B23F37B400
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 13 Aug 2002 16:09:10 -0700 (PDT)
Received: from server.rucus.ru.ac.za (server.rucus.ru.ac.za [146.231.115.1])
	by mx1.FreeBSD.org (Postfix) with SMTP id 026B143E6E
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 13 Aug 2002 16:09:06 -0700 (PDT)
	(envelope-from drs@rucus.ru.ac.za)
Received: (qmail 37511 invoked from network); 13 Aug 2002 23:09:02 -0000
Received: from bashir.dsl.ru.ac.za (146.231.113.19)
  by server.rucus.ru.ac.za with SMTP; 13 Aug 2002 23:09:02 -0000
Received: (qmail 3967 invoked by uid 1001); 13 Aug 2002 23:09:02 -0000
Message-Id: <20020813230902.3966.qmail@bashir.dsl.ru.ac.za>
Date: 13 Aug 2002 23:09:02 -0000
From: David "Siebrger" <drs@rucus.ru.ac.za>
Reply-To: David "Siebrger" <drs@rucus.ru.ac.za>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: New FAQ entry explaining UDMA ICRC errors
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         41643
>Category:       docs
>Synopsis:       New FAQ entry explaining UDMA ICRC errors
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Aug 13 16:10:01 PDT 2002
>Closed-Date:    Thu Dec 19 16:56:04 PST 2002
>Last-Modified:  Thu Dec 19 16:56:04 PST 2002
>Originator:     David Siebrger
>Release:        FreeBSD 4.6-STABLE i386
>Organization:
Rhodes University Computer Users Society
>Environment:
System: FreeBSD bashir.dsl.ru.ac.za 4.6-STABLE FreeBSD 4.6-STABLE #11: Tue Aug 6 10:43:06 SAST 2002 drs@bashir.dsl.ru.ac.za:/usr/obj/usr/src/sys/BASHIR i386
>Description:

This is one that I've experienced a few times myself and has come up on
-questions and -hardware many times.

>How-To-Repeat:
>Fix:

--- book.sgml.diff begins here ---
--- doc/en_US.ISO8859-1/books/faq/book.sgml.orig	Wed Aug 14 00:42:32 2002
+++ doc/en_US.ISO8859-1/books/faq/book.sgml	Wed Aug 14 00:58:09 2002
@@ -4363,6 +4363,39 @@
             and connections.</para>
         </answer>
       </qandaentry>
+
+      <qandaentry>
+        <question id="udma-icrc">
+          <para>What are <quote>UDMA ICRC</quote> errors, and how do I
+            fix them?</para>
+        </question>
+
+        <answer>
+          <para>The &man.ata.4; driver reports <quote>UDMA ICRC</quote>
+            errors when a DMA transfer to or from a drive is corrupted.
+            The driver will retry the operation a few times.  Should
+            the retries fail, it will switch from DMA to the slower PIO
+            mode of communication with the device.</para>
+          <para>The problem can be caused by many factors, although
+            perhaps the most common cause is faulty or incorrect
+            cabling.  Check that the ATA cables are undamaged and rated
+            for the Ultra DMA mode in use.  If you're using removable
+            drive trays, they must also be compatible.  Be sure that
+            all connections are making good contact.  Problems have
+            also been noticed when an old drive is installed on the
+            same ATA channel as an Ultra DMA 66 (or faster) drive.
+            Lastly, these errors can indicate that the drive is
+            failing.  Most drive vendors provide testing software for
+            their drives, so test your drive, and, if necessary, back
+            up your data and replace it.</para>
+          <para>The &man.atacontrol.8; utility can be used to show and
+            select the DMA or PIO modes used for each ATA device.  In
+            particular, <command>atacontrol mode
+            <replaceable>channel</replaceable></command> will show the
+            modes in use on a particular ATA channel, where the primary
+            channel is numbered 0, and so on.</para>
+        </answer>
+      </qandaentry>
     </qandaset>
   </chapter>
 
--- book.sgml.diff ends here ---


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: trhodes 
State-Changed-When: Thu Dec 19 16:55:47 PST 2002 
State-Changed-Why:  
Committed!  Thanks for the submission! 

http://www.freebsd.org/cgi/query-pr.cgi?pr=41643 
>Unformatted:
