Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 30 May 2013 16:17:02 GMT
From:      "Majdi S. Abbas" <msa@latt.net>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   misc/179113: ATA DMA does not fall back on systems that misreport capability
Message-ID:  <201305301617.r4UGH2ZT023889@oldred.FreeBSD.org>
Resent-Message-ID: <201305301620.r4UGK0Li099199@freefall.freebsd.org>

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

>Number:         179113
>Category:       misc
>Synopsis:       ATA DMA does not fall back on systems that misreport capability
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu May 30 16:20:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator:     Majdi S. Abbas
>Release:        9.1-RELEASE/i386
>Organization:
Lattice, L.L.C.
>Environment:
FreeBSD procyon.latt.net 9.1-RELEASE FreeBSD 9.1-RELEASE #2: Wed May 29 16:01:42 UTC 2013     msa@procyon.latt.net:/usr/src/sys/i386/compile/NET4801  i386
>Description:
The system in question is a Soekris NET4801, running from a Kingston CF card.  This CF card reports DMA capability, which the internal PATA/CF adapter does not support.

As a result, when the kernel is booting, it will sit there and retry UDMA_66 access to the drive indefinitely.  It claims to timeout after the 5th retry, but will, in fact, retry continuously.
>How-To-Repeat:
Attempt to boot (or access media) on any system that has an PATA-CF adapter that does not have the two additional pins required to support DMA.
>Fix:
While disabling DMA by handing hw.ata.ata_dma=0 to the loader works, NetBSD has an interesting approach here that requires no user intervention.

I installed NetBSD 6.1/i386 on the same machine as a test, and the NetBSD kernel will attempt UDMA_66 3 times, and then fall back to UDMA_33, attempt 3 times, and then fall back to PIO mode.  Something like this may make sense for FreeBSD, as it will reduce failures to boot or access media.

>Release-Note:
>Audit-Trail:
>Unformatted:



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