From: Pavel Machek <pavel@ucw.cz>
To: "Wyborny, Carolyn" <carolyn.wyborny@intel.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>, Greg KH <greg@kroah.com>,
kernel list <linux-kernel@vger.kernel.org>,
Joe Lawrence <joe.lawrence@stratus.com>,
Myron Stowe <myron.stowe@redhat.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"Allan, Bruce W" <bruce.w.allan@intel.com>,
"Skidmore, Donald C" <donald.c.skidmore@intel.com>,
"Rose, Gregory V" <gregory.v.rose@intel.com>,
"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>,
"Duyck, Alexander H" <alexander.h.duyck@intel.com>,
"Ronciak, John" <john.ronciak@intel.com>,
"Dave, Tushar N" <tushar.n.dave@intel.com>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>
Subject: Re: /sys/module/pcie_aspm/parameters/policy not writable?
Date: Sun, 28 Jul 2013 15:51:03 +0200 [thread overview]
Message-ID: <20130728135103.GC5382@amd.pavel.ucw.cz> (raw)
In-Reply-To: <9BBC4E0CF881AA4299206E2E1412B6264F921872@ORSMSX102.amr.corp.intel.com>
On Wed 2013-07-24 15:19:55, Wyborny, Carolyn wrote:
> > -----Original Message-----
> > From: Bjorn Helgaas [mailto:bhelgaas@google.com]
> [..}
> >
> > We *could* consider something like this, since its scope is limited.
> > But since the problem also occurs with Windows, it's pretty likely that there's a
> > BIOS update to fix it. I notice on the X60 support page that there are several
> > versions newer than what you're running.
> >
> > Bjorn
>
> I believe that some BIOS don't allow user control on this feature, thus we end up unable to disable it from driverspace or from userspace, with the method we use today in this scenario.
>
> I have a patch almost ready that attempts to disable using the pci_disable_link_state() call but then checks again to see if its still enabled and if not, then changes the pci config space on the devices on either side of the pcie link. I plan to send it to this list for Pavel's testing as soon as I have it finished, at worst end of week.
>
If there's patch, I'll gladly try it :-). Thanks,
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-28 13:51 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 1:26 /sys/module/pcie_aspm/parameters/policy not writable? Pavel Machek
2013-07-09 4:13 ` Greg KH
2013-07-09 9:14 ` Pavel Machek
2013-07-09 9:49 ` Pavel Machek
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-10 22:57 ` Bjorn Helgaas
2013-07-11 17:45 ` Wyborny, Carolyn
2013-07-11 17:45 ` Wyborny, Carolyn
2013-07-12 11:52 ` Pavel Machek
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 [this message]
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=20130728135103.GC5382@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--cc=alexander.h.duyck@intel.com \
--cc=bhelgaas@google.com \
--cc=bruce.w.allan@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=donald.c.skidmore@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--cc=gregory.v.rose@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=joe.lawrence@stratus.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myron.stowe@redhat.com \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=tushar.n.dave@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.