linux-kernel - Re: sata_nv times out for BD-ROM iHOS104-08

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-prev] [day] [month] [year] [list]

Message-ID: <d2d378041001231339o1d1b0984y2b2a85b717987d93@mail.gmail.com>
Date:	Sat, 23 Jan 2010 16:39:57 -0500
From:	Cengiz Günay <cgunay@...ry.edu>
To:	Tejun Heo <tj@...nel.org>
Cc:	Robert Hancock <hancockrwd@...il.com>,
	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org
Subject: Re: sata_nv times out for BD-ROM iHOS104-08

Hello,

2010/1/22 Tejun Heo <tj@...nel.org>:
> The parameter isn't being passed to the module loaded by initrd.  You
> probably need to edit modules.conf and then regenerate initrd.  :-(

Ok, you're right. I forgot I had to do that. So now I did it for
ADMA=0, SWNCQ=0 and MSI=1, separately. None worked, and all dmesg
outputs attached.

> Yeah, I was about to suggest trying the patch.  It could be that the
> timeout used by the new TUR code is too aggressive.

Unfortunately that didn't work, either (attached). It kept on changing
DMA modes down to PIO0 and completly failed in the end. Should I try
different sata_nv parameters with this patch if needed?

Thanks,
-- 
Cengiz

View attachment "dmesg-sata_nv-adma_disabled_no_initrd.log" of type "text/x-log" (4224 bytes)

View attachment "dmesg-sata_nv-swncq-disabled_in_initrd.log" of type "text/x-log" (4562 bytes)

View attachment "dmesg-sata_nv-swncq-0-msi-1_in_initrd.log" of type "text/x-log" (4650 bytes)

View attachment "dmesg-sata_nv-disable-clear-ua.log" of type "text/x-log" (40543 bytes)