Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 15 Dec 2003 15:00:48 -0500 (EST)
From:      Andrew Gallatin <gallatin@cs.duke.edu>
To:        sos@FreeBSD.ORG
Cc:        current@FreeBSD.ORG
Subject:   Re: cable detection
Message-ID:  <16350.4848.244536.768751@grasshopper.cs.duke.edu>
In-Reply-To: <200312122347.hBCNldWS061636@spider.deepcore.dk>
References:  <16345.57618.966705.95086@grasshopper.cs.duke.edu> <200312122347.hBCNldWS061636@spider.deepcore.dk>

next in thread | previous in thread | raw e-mail | index | archive | help

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<READY,DSC,ERROR> error=84<ICRC,ABORTED>
# ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request)
ad0: WARNING - WRITE_DMA UDMA ICRC error (retrying request)
ad0: FAILURE - WRITE_DMA status=51<READY,DSC,ERROR> error=84<ICRC,ABORTED>

# 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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16350.4848.244536.768751>