linux-kernel - Re: Quick question about libata and hdparm

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]

Date:	Fri, 24 Apr 2009 00:00:50 -0300
From:	Rogério Brito <rbrito@....usp.br>
To:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, Jeff Garzik <jeff@...zik.org>,
	Michael Tokarev <mjt@....msk.ru>, Mark Lord <lkml@....ca>,
	linux-kernel@...r.kernel.org
Subject: Re: Quick question about libata and hdparm

Hi, Bart, Alan & Co.

On 4/23/09, Bartlomiej Zolnierkiewicz <bzolnier@...il.com> wrote:
>  You can try booting with "libata.force=1.00:mwdma2" kernel paramater to
>  force use of "regular" MWDMA2 transfer mode instead of UDMA ones so we are
>  sure that the issue is specific to pata_pdc202xx_old + UDMA.

This *did* work. I see no other error messages, while using multword
dma. So I think that this serves for us to rule out some unknown
variables.

>  Other than that I'm out of ideas, though the hint that the original driver
>  works just fine should help driver's maintainer in fixing this regression.

Well, it worked now. I'm attaching what I see now.


Thanks, Rogério Brito.

P.S.: This is still with kernel 2.6.29, since compiling a new kernel
in this computer takes a lot of time.
-- 
Rogério Brito : rbrito@...ckenzie,ime.usp}.br : GPG key 1024D/7C2CAEB8
http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito
Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org

View attachment "dmesg-2.6.29-with-force-mwdma2.txt" of type "text/plain" (5942 bytes)