linux-kernel - Re: 2.6.23.17 & 2.6.24.5 and maybe earlier: pata_marvell: need to disable DMA to get rid of '(ATA bus error)', 'ata7.00: status: { DRDY ERR }', 'ata7.00: error: { ICRC ABRT }'

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 02 May 2008 20:42:53 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Jan Engelhardt <jengelh@...ozas.de>,
	Martin MOKREJŠ 
	<mmokrejs@...osome.natur.cuni.cz>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.23.17 & 2.6.24.5 and maybe earlier: pata_marvell: need to
 disable DMA to get rid of '(ATA bus error)', 'ata7.00: status: { DRDY ERR }',
 'ata7.00: error: { ICRC ABRT }'

Alan Cox wrote:
>>> libata.dma=3 will stop DMA being used for CF devices (except those that
>>> decide to pretend to be ATA classes). This one comes up a lot as many CF
>>> adapters are simply not adequate for UDMA.
>> Perhaps the kernel could do this automatically once it sees the
>> status code?
> 
> We then hurt all the people with perfectly good working UDMA CF devices.
> The kernel will eventually fall back from UDMA to PIO but it favours
> working hardware by default.

I suspect they meant fall back on seeing the ABRT/ICRC error combination 
- which it does, eventually. Falling back on one occurrence would be too 
aggressive, though, as they can happen once in a blue moon, so there's 
little reason to slow down a working setup forever because of it..
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/