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: <48052BB3.2090509@gmail.com>
Date:	Wed, 16 Apr 2008 07:26:59 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Paul Collins <paul@...ly.ondioline.org>
CC:	Jeff Garzik <jeff@...zik.org>, linux-kernel@...r.kernel.org
Subject: Re: ata2: SATA link down (SStatus 611 SControl 300)

Hello, Paul.

Paul Collins wrote:
> Tejun Heo <htejun@...il.com> writes:
> 
>>> ata2: XXX about to resume
>>> ata2: SATA link down (SStatus 611 SControl 0)
>> The link is already in slumber mode before the driver doing anything
>> to it.  Is there any related setting in BIOS?
> 
> I found a setting labelled "SATA Power Management".  It was set to
> "Enable".  When I set it to "Disable", 2.6.25-rc9 detected the optical
> drive.

This can't be something changed between 2.6.24 and 2.6.25-rc9.  Can you 
please double check that?

>> Also, can you please give a shot at the attached patch?
> 
> I tried this patch with "SATA Power Management" on both settings.  In
> each case it detected the optical drive.

Good, so it seems later ich's need its SPM fields written or link reset 
to get out of powersave mode.  Inhibiting PM modes via IPM isn't enough, 
which BTW is sane.

Jeff, this one looks like another rationale for favoring hardreset over 
softreset && I don't see how we can fix this for 2.6.25.  We can try to 
write to SPM from link_resume() but the field being newly added in SATA 
2.5, I don't feel comfortable about it.

Thanks.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ