Originally posted by mistvieh
View Post
Announcement
Collapse
No announcement yet.
The Leading Cause Of The Recent Linux Kernel Power Problems
Collapse
X
-
Originally posted by krazy View PostI'd just like to say, however, that calling this a "Kernel Regression" seems fairly disingenuous. This is a BIOS bug, only seen in machines with a buggy BIOS.
Comment
-
Originally posted by krazy View PostThanks for your work in figuring out what is going on here Michael.
I'd just like to say, however, that calling this a "Kernel Regression" seems fairly disingenuous. This is a BIOS bug, only seen in machines with a buggy BIOS. And I'd be interested to know how common this problem even is, since none of my machines have exhibited the issue.
Arguments on the high or low moral ground of the kernel carrying workarounds isn't going to solve this for anyone.
In this situation, there are a few options,
1. revert the change (which we had been carrying for some before hand)
2. Understand the interaction more fully (obviously the systems work de-facto or de-jure under Windows so there should be some system behavior that allows it to work).
3. Keep the change and add one more to the list of workarounds for BIOSes and hope that vendors improve in the future.
I'd personally opt for 2, with either 1 or 3 being up to the developer - erring on the side of 1.
Comment
-
For me it's now clear that is a hardware/firmware vendor failure. If the BIOS reports that the system does'n support ASPM, logic here says not to enable it.
If the kernel developers decide to implement some other logic to enable it even when no support is reported, we can only be grateful with them.
Comment
-
My mother's Acer Aspire overheated when running 2.6.38, but my HP Pavilion dv6700 doesn't suffer much from the power problems; HP has always been friendly to Linux and after a BIOS update (and sometimes even right out-of-the-box) they seem to have proper FADT tables on quite some models.
Comment
-
Originally posted by Cyborg16 View PostRe: hardware, it looks like several models of Lenovo Thinkpad are affected (my T410 is, and I've seen a W520 mentioned here as well as Michael's T61).
.
Comment
-
Originally posted by krazy View PostThanks for your work in figuring out what is going on here Michael.
I'd just like to say, however, that calling this a "Kernel Regression" seems fairly disingenuous. This is a BIOS bug, only seen in machines with a buggy BIOS. And I'd be interested to know how common this problem even is, since none of my machines have exhibited the issue.Originally posted by smitty3268 View PostIt would be interesting if everyone with the problem could post their what BIOS they are using and the MB manufacturer. To see if there's a common theme.
I'm sorry but I can't help you with that, because none of my machines are affected by this problem either.
Comment
-
Originally posted by Rabauke View PostSo, how do we Thinkpad users handle this? Stick together and talk to Lenovo? I mean, if only one talks to them claiming new tables they will simply laugh at you.
Comment
Comment