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>] [day] [month] [year] [list]
Message-ID: <d4fb20ca1001201915p59d3c9eal6014c22d449c46e6@mail.gmail.com>
Date:	Wed, 20 Jan 2010 22:15:56 -0500
From:	Gregory Moyer <raven2k@...hr.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: sata_nv times out for BD-ROM iHOS104-08

> > Hmm.... it worked?  Does kernel parameter sata_nv.adma_enabled=0 make
> > any difference?  Can you please attach boot log with the kernel
> > parameter specified?
>
> Think you meant maybe sata_nv.swncq=0 instead - this is an MCP51
> controller so it doesn't support ADMA. I don't imagine SWNCQ would
> make any difference with an ATAPI device, but wouldn't hurt to try.

I tried booting 2.6.32 with both of these options (tried separately)
with no change in behavior. If it helps, sometimes I get an error mask
of 0x4 and sometimes 0x5, though I do not know what either represents.
Also, my controller is MCP55, but I don't know how different that is
from the MCP51 that Cengiz has.

Attached are boot logs from running each option suggested here.

Thanks again.

- Greg

View attachment "boot.2.6.32.adma.disabled.log" of type "text/x-log" (47322 bytes)

View attachment "boot.2.6.32.swncq.disabled.log" of type "text/x-log" (47370 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ