From: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [0/1] 3.0.20-stable review
Date: Sun, 5 Feb 2012 11:20:48 +0100 [thread overview]
Message-ID: <1328434946@msgid.manchmal.in-ulm.de> (raw)
In-Reply-To: <20120203220745.GA3459@kroah.com>
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
next prev parent reply other threads:[~2012-02-05 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 22:07 [0/1] 3.0.20-stable review Greg KH
2012-02-03 22:01 ` [1/1] PCI: Rework ASPM disable code Greg KH
2012-02-05 10:20 ` Christoph Biedl [this message]
2012-02-05 10:59 ` [0/1] 3.0.20-stable review Willy Tarreau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1328434946@msgid.manchmal.in-ulm.de \
--to=linux-kernel.bfrz@manchmal.in-ulm.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox