linux-kernel - Re: pata_amd dropping to PIO on resume

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <45D6436C.4060209@garzik.org>
Date:	Fri, 16 Feb 2007 18:51:08 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Robert Hancock <hancockr@...w.ca>
CC:	Tobias Diedrich <ranma+kernel@...edrich.de>,
	Linux Kernel ML <linux-kernel@...r.kernel.org>,
	linux-ide@...r.kernel.org, Alan <alan@...rguk.ukuu.org.uk>
Subject: Re: pata_amd dropping to PIO on resume

Robert Hancock wrote:
> Tobias Diedrich wrote:
>> Possibly a known issue:
>>
>> After resume pata_amd drops from UDMA/33 to PIO on my system.
>> Reloading the module puts both attached optical drives (master and
>> slave) back to UDMA/33.
>>
>> AFAICS "simplex DMA is claimed by other device, disabling DMA" seems
>> to be causing it to drop to PIO (but only after a suspend/resume
>> cycle, not on boot or module load).
>>
>> Burning a DVD with 6x speed using PIO makes heavy use of burnproof
>> and makes the whole system quite sluggish. :)
> 
> Yes, the fact that it's going into simplex mode is the problem, it 
> wasn't in simplex to start with. It looks like pata_amd does an 
> ata_pci_clear_simplex only for certain chip models, maybe this model 
> needs it as well?
> 

Deleting the ata_pci_clear_simplex() call, then adding 
ATA_FLAG_IGN_SIMPLEX to the ata_port_info info[] array, is also worth 
trying.

	Jeff


-
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/