From: Pavel Machek <pavel@ucw.cz>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Greg KH <greg@kroah.com>,
kernel list <linux-kernel@vger.kernel.org>,
Joe Lawrence <joe.lawrence@stratus.com>,
Myron Stowe <myron.stowe@redhat.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Bruce Allan <bruce.w.allan@intel.com>,
Carolyn Wyborny <carolyn.wyborny@intel.com>,
Don Skidmore <donald.c.skidmore@intel.com>,
Greg Rose <gregory.v.rose@intel.com>,
Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>,
Alex Duyck <alexander.h.duyck@intel.com>,
John Ronciak <john.ronciak@intel.com>,
Tushar Dave <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: Fri, 2 Aug 2013 03:02:59 +0200 [thread overview]
Message-ID: <20130802010259.GA4779@amd.pavel.ucw.cz> (raw)
In-Reply-To: <CAErSpo4Dw9Bg059scx-YzR=5rpkc65f0hjQnM7STtoprOLXJqw@mail.gmail.com>
Hi!
> >> > 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.
> >>
> >> Do you have any interest in trying a newer BIOS to see if it's fixed
> >> there? If not, I understand; BIOS updates are a hassle at best.
> >> You're running BIOS 2.14, and it looks like the current BIOS for an
> >> X60 1709 7HU is 2.19 (from http://support.lenovo.com).
> >
> > I'm lost at the lenovo pages :-(. And frankly I'd prefer not to touch
> > the BIOS.
>
> I tried to provide a complete link, but the web site isn't amenable to
> that. I found it by selecting the "Drivers & Software" section,
> entering "X60" as the machine type, selecting "ThinkPad X60 (1709)"
> and going to the "BIOS" section. I was surprised how easy it was :)
Ok, got it, the web pages are horible.
> >> Carolyn's patch will likely work, at least most of the time, but I
> >> think there's a small possibility that it could cause a conflict
> >> between the BIOS and the OS over ASPM control, so I'm not 100% in
> >> support of that approach. A conflict may not happen on your
> >> machine,
> >
> > Can we base it on DMI whitelist?
>
> I don't think we can know a priori whether a machine (even your
> machine) is susceptible to a conflict. But if Carolyn forcibly
> disables it in the driver, she can structure that with a whitelist or
> whatever she thinks is best.
Well, there's only one way to find out: try it. I was running with the
"enable ASPM so we can disable it" one-liner for a while, and seen no
ill effects.
Anyway, if you don't hear from me again, it means that I have a brick
(and not a notebook) and am desperately trying to get replacement
X60. Will try to flash it in few minutes.
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-08-02 1:03 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
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 [this message]
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=20130802010259.GA4779@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 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®