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: <1328434946@msgid.manchmal.in-ulm.de>
Date:	Sun, 5 Feb 2012 11:20:48 +0100
From:	Christoph Biedl <linux-kernel.bfrz@...chmal.in-ulm.de>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [0/1] 3.0.20-stable review

Greg KH wrote...

> Please let me know if anyone has any problems with it as soon as possible.

After two tests without any visible change in neither power
consumption nor system stability: How do I identify computers where
that patch _might_ change things? Does for example

    ACPI _OSC control for PCIe not granted, disabling ASPM

indicate that box isn't worth any efforts? Does this patch void a
"pcie_aspm=force" kernel parameter, should or even must that one be
given?

And another question, what are "any problems" likely to be? Obvious
things like crashes, or rather nasty things like slowly eating data on
the disks?

I bet there are some documents around about that, so pointers will do.
There's <Documentation/kernel-parameters.txt> and
<https://wiki.ubuntu.com/Kernel/PowerManagementASPM> but these don't
answer my questions.

> Responses should be made by Monday, February 6, 2012, 20:00:00 UTC.
> Anything received after that time might be too late.

Having said that, no appearent effect found on (DMI string from
dmesg):

- D945GCLF2, BIOS LF94510J.86A.0278.2010.0414.2000 04/14/2010
- M4A88T-V EVO, BIOS 0405 12/15/2010

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