[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAErSpo4Dw9Bg059scx-YzR=5rpkc65f0hjQnM7STtoprOLXJqw@mail.gmail.com>
Date: Thu, 1 Aug 2013 14:27:29 -0600
From: Bjorn Helgaas <bhelgaas@...gle.com>
To: Pavel Machek <pavel@....cz>
Cc: Greg KH <greg@...ah.com>,
kernel list <linux-kernel@...r.kernel.org>,
Joe Lawrence <joe.lawrence@...atus.com>,
Myron Stowe <myron.stowe@...hat.com>,
Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
Jesse Brandeburg <jesse.brandeburg@...el.com>,
Bruce Allan <bruce.w.allan@...el.com>,
Carolyn Wyborny <carolyn.wyborny@...el.com>,
Don Skidmore <donald.c.skidmore@...el.com>,
Greg Rose <gregory.v.rose@...el.com>,
Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@...el.com>,
Alex Duyck <alexander.h.duyck@...el.com>,
John Ronciak <john.ronciak@...el.com>,
Tushar Dave <tushar.n.dave@...el.com>,
"e1000-devel@...ts.sourceforge.net"
<e1000-devel@...ts.sourceforge.net>
Subject: Re: /sys/module/pcie_aspm/parameters/policy not writable?
On Thu, Aug 1, 2013 at 2:00 PM, Pavel Machek <pavel@....cz> wrote:
> 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 :)
>> 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.
Bjorn
--
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