From: Pavel Machek <pavel@ucw.cz>
To: Greg KH <greg@kroah.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
joe.lawrence@stratus.com, myron.stowe@redhat.com,
bhelgaas@google.com
Subject: Re: /sys/module/pcie_aspm/parameters/policy not writable?
Date: Tue, 9 Jul 2013 11:49:06 +0200 [thread overview]
Message-ID: <20130709094906.GA3870@amd.pavel.ucw.cz> (raw)
In-Reply-To: <20130709041321.GA30555@kroah.com>
On Mon 2013-07-08 21:13:21, Greg KH wrote:
> On Tue, Jul 09, 2013 at 03:26:11AM +0200, Pavel Machek wrote:
> > Hi!
> >
> > My thinkpad has rather high ping latencies... and perhaps it is due to
> > PCIE ASPM.
>
> Why would that be the problem? The odds that the PCIE bus is the issue
> seems strange to me.
Aha: I guess that's why the file is not writable:
pavel@amd:~$ dmesg | grep -i aspm
ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
e1000e 0000:02:00.0: Disabling ASPM L0s L1
pavel@amd:~$ cat /sys/module/pcie_aspm/parameters/policy
[default] performance powersave
pavel@amd:~$
root@amd:~# echo -n performance >
/sys/module/pcie_aspm/parameters/policy
-su: echo: write error: Operation not permitted
root@amd:~#
But:
1) it should not list unavailable options
2) operation not permitted seems like wrong error code for
operation not supported.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2013-07-09 9:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 1:26 Pavel Machek
2013-07-09 4:13 ` Greg KH
2013-07-09 9:14 ` Pavel Machek
2013-07-09 9:49 ` Pavel Machek [this message]
2013-07-09 10:10 ` Pavel Machek
2013-07-09 16:25 ` Bjorn Helgaas
2013-07-10 13:29 ` Pavel Machek
2013-07-10 19:57 ` Bjorn Helgaas
2013-07-10 22:21 ` Wyborny, Carolyn
2013-07-10 22:57 ` Bjorn Helgaas
2013-07-11 17:45 ` Wyborny, Carolyn
2013-07-12 11:52 ` Pavel Machek
2013-07-12 11:03 ` Pavel Machek
2013-07-12 11:11 ` Pavel Machek
2013-07-19 17:46 ` Bjorn Helgaas
2013-07-24 15:19 ` Wyborny, Carolyn
2013-07-28 13:51 ` Pavel Machek
2013-08-01 14:55 ` Wyborny, Carolyn
2013-08-01 15:55 ` Wyborny, Carolyn
2013-08-02 0:39 ` Pavel Machek
2013-08-02 14:58 ` Wyborny, Carolyn
2013-07-31 23:53 ` Bjorn Helgaas
2013-08-01 14:57 ` Wyborny, Carolyn
2013-08-01 19:33 ` Bjorn Helgaas
2013-08-01 20:00 ` Pavel Machek
2013-08-01 20:27 ` Bjorn Helgaas
2013-08-02 1:02 ` Pavel Machek
2013-08-02 2:13 ` Pavel Machek
2013-08-02 13:48 ` Bjorn Helgaas
2013-08-01 6:19 ` Jeff Kirsher
2013-07-09 16:37 ` Greg KH
2013-07-09 17:15 ` Pavel Machek
2013-07-10 4:24 ` Robert Hancock
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=20130709094906.GA3870@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=bhelgaas@google.com \
--cc=greg@kroah.com \
--cc=joe.lawrence@stratus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myron.stowe@redhat.com \
/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
all inboxes | Powered by JetHome®