Re: Is there still sufficient reason for hw.ata.atapi_dma being 0 by default?

From: Chuck Swiger (cswiger_at_mac.com)
Date: 07/30/04

  • Next message: Gleb Smirnoff: "Re: PPPoE problems with latest -CURRENT"
    Date: Fri, 30 Jul 2004 15:02:48 -0400
    To: Søren Schmidt <sos@DeepCore.dk>
    
    

    Søren Schmidt wrote:
    > Maxim Sobolev wrote:
    >> Since high-speed CD-RW/DVD-RW recorders (32x - 52x) are commodity now
    >> IMO it makes sense to review hw.ata.atapi_dma default of 0, since
    >> apparently PIO mode can't support necessary sustained data transfer
    >> rates anymore. For example I had had problems burning RWs on 16-24x
    >> with several drives in PIO mode, which gone when I've switched to DMA.

    Before CD burners became common, having this sysctl default to zero was almost
    entirely harmless: people would simply read from CD-ROM drives slower than
    optimal. If we change the default to one, people with fast burners will no
    longer generate coasters by default too. In other words, Maxim has provided a
    pretty good reason for changing the default of atapi_dma, I think. :-)

    > Hmm, things are still messy, but most drives that support UDMA33 can do
    > ATAPI dma. However, that is only part of the equation, the chipset has
    > its hands in there as well, and unfortunatly there seems to be no good
    > way to detect when it works and when it doesnt.

    If the chipset is broken, why doesn't it default to using PIO4 rather than
    UDMA? :-) Anyway, doesn't there exist fallback code in dev/ata/ata-disk.c:

             /* if this is a UDMA CRC error, reinject request */
    [ ... ]
                     printf(" falling back to PIO mode\n");

    ...which will switch a device generating errors from UDMA mode to PIO? Can
    this check also turn off using atapi_dma (if using PIO doesn't already imply
    not using DMA)?

    -- 
    -Chuck
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
    

  • Next message: Gleb Smirnoff: "Re: PPPoE problems with latest -CURRENT"

    Relevant Pages

    • Re: Drive shows up as PIO mode only
      ... >> drives in ultra dma modes. ... >> a PIO mode drive, I know it won't be able to handle it. ...
      (microsoft.public.windowsxp.general)
    • Re: Silent errors when reading CDs
      ... That's while there were no corruption on burning in DMA or PIO mode. ... DMA mode on an ATAPI device might be the root of the evil. ... a lot of ATA controllers have bugs there. ... If your drives work OK with a different ATA ...
      (freebsd-hackers)
    • Re: DMA mode
      ... First, the current transfer rate ... may be at DMA 5, but the maximum is DMA 6. ... PIO Mode since they are capable of much more data throughput. ... What exactly are your optical drives? ...
      (microsoft.public.windowsxp.hardware)
    • Re: Panic during install on Sparc64 - Only with large HDD
      ... Perhaps also a proper solution would be to report attached drives on it in DMA ... > On 14/08/2005, at 20:16, Chris Gilbert wrote: ... >> Will continue looking into the chipset docs and FreeBSD driver... ... > A workaround in ATA could be to use PIO mode when crossing the ...
      (freebsd-current)
    • ATA kablooie
      ... After an upgrade, it started spewing out ... the arduous effort of spawning off 'sh' for single-user ... I tried using the loader variable to force the drives to PIO mode to ...
      (freebsd-current)