The Leading Cause Of The Recent Linux Kernel Power Problems

[fewt]

I really shouldn't have had to quote as you should have known what you said previously. You doubt Phoronix's credibility but perhaps you should look in the mirror.

No, it is most likely not a real problem or is a problem for a limited number of devices. The evidence is against it. Those users that are reporting "problems" aren't troubleshooting it well (not their faults).

- My comment on reddit.

[fewt]

Oh my what a short memory you have:

or actually spend time finding the problem
there is NO evidence that it's real.

To the rest of my comments you have quoted out of context, they were correct in their proper context, as the bug didn't exist until it was proven to exist.

For example..

What you fail to realize though is that the burdon of proof is not on me. It is not my responsibility to disprove that the bug exists, it is on Phoronix who initiated and continued these same baseless claims for months. I don't think that it is too much to ask for Phoronix to actually prove their theory after all this time by showing us the commit since the claim was made in the first article that it would be found "quickly".

It is not up to the kernel team to change the running configuration (dynamic tuning), as that would negatively impact a great many things. This function belongs in userland.

Power management on Linux is on par (in some areas) with power management on Windows and OSX once you install Jupiter. Without it, power management on Linux is virtually non-existant.

I don't know that I would call this a kernel regression, as the kernel doesn't dynamically change parameters based on applied power state. That's what you need something like Jupiter for.. - http://phoronix.com/forums/showthrea...gression/page5

I see that the only value you bring to this forum is in the form of personally attacking anyone that disagrees with Michael. A troll as moderator, nice.

[deanjo]

Re-read my comment and try to comprehend my statement this time rather than simply attacking me. I said it probably didn't exist, and that none of my users were impacted. Both statements are still true.

Oh my what a short memory you have:

Are we still beating this dead horse? This power bug doesn't exist, and sadly I'm starting to believe it is being reported on for the sole purpose of driving hits.

No, the sky is not falling. Yes, I have used my netbook for 10 hours with kernel 2.6.39 and yes I still had battery left afterwards.

Time to let it go and move on, or actually spend time finding the problem instead of writing articles about it.

Sorry to be so blunt, but people are actually believing this even though there is NO evidence that it's real.

I agree, however "WorksForMe" isn't at play here, since I have pretty extensive knowledge of power saving techniques on this platform.

Again you make assumptions. I looked at each and every comment in the bug report and discredited nearly all of them almost two weeks ago.

I know you are trying to defend the article, but this is ridiculous. Phoronix was given the benefit of the doubt, and has had plenty of time to "bisect the issue". All this article does is continue to claim that the sky is falling, but if you look outside you will find that the sky is certainly NOT falling.

If it were we would have credible reports and not just one tinfoil hat article, and the resulting bug reports from the paranoia that it caused.

By "theory" you mean practice, practice which happens to be in the realm of Linux power management.

Something that I have deep roots in and years of experience with.

Not to mention the thousands of users of my product that improves power savings .. on the Linux platform. None of which have filed a bug report, or made mere mention of battery life issues with any recent kernel.

Because those issues don't exist.

I also happen to have experience with product testing, and believe me they are all doing it wrong. There is no control group, and the test reports are all over the map. You can't confirm anything by it except that the testing itself is invalid.

Michael has had enough time to find the issue, and he's come up empty. The closest thing we have seen to a "real" power related issue is the patch for the cpuidle bug that was pulled into 2.6.39.1.

Too bad you don't like what I have to say but Phoronix is wrong, get over it.

Unable to replicate it because it does not exist, as I indicated.

As I said, it doesn't exist. Making lame excuses as to why I (and others) haven't seen it doesn't really help.

Unable to replicate across many systems and many use cases, remember I have 0 bug reports and a few thousand users. This in itself is evidence against this "bug".

I really shouldn't have had to quote as you should have known what you said previously. You doubt Phoronix's credibility but perhaps you should look in the mirror.

[fewt]

No, that's not true. You can have a planned regression, or an expected regression. It's still a regression, due to the fact that the new power behavior is worse than it used to be. Even if that fixes other bugs, it's fixes crashes while simultaneously regressing power usage.

Perhaps it is a regression for 1% of the 1% of users that this patch fixed, I would concede that point.

[fewt]

Which is a long ways away from your claim that it didn't even exist based on your "expertise" and "thousands of users".

Re-read my comment and try to comprehend my statement this time rather than simply attacking me. I said it probably didn't exist, and that none of my users were impacted. Both statements are still true.

[V!NCENT]

The entire motherboard chip design is hugely based on the BIOS. Why not just gather another 'standards body/consortium' (like they all like to do), totaly whipe all the crap from the tabel, start out with Coreboot in the 'just load this from here to there and execute and bye-bye'-mode and strip and patch the shit out of the lower kernel layers and... Simply be done with it.

You would think that all these companies would do that anyway, to save some serious licensing and programming money, but appearantly they've something better to do, like putting F4tality1337-uberGamer on the box...

[Xake]

Always interesting to see a thread go from something interesting (which BIOS-devs sucks at their implementations) to something completely unnecessary (whoo, is-it-a-regression-or-not grammar-nazi style, whooo michael-sucks-because-I-really-has-nothing-better-to-say, troll-style ), effectively killing the thread.

Please address your more nasty aggression/mental/inferiority-problems before posting.

From my side, cudos to Michael for instead of just hunting dow one regression taking the time and automating the process.
The only thing I am currently missing is a more automated test-platform for hardware to find what is working according to specs and definitions, something like the BIOS test Intel released earlier this year, but more automated and with the possibility to send it to a central DB for everyone to know how good/shitty products some vendors do. I actually think it would be easier to get hardware-vendors to sign their products with "passes <name-of-hw-check>-<version-of-said-test>" then sign them "works with linux", mostly if Intel and AMD pushes them to use that test to create less shitty BIOSes. Some BIOS-devs would like it too, I think, the possibility to test out features in a easy way before Windows supports said technology.

[smitty3268]

It was dubbed a regression due to a fundamental lack of understanding of the issue.

No, that's not true. You can have a planned regression, or an expected regression. It's still a regression, due to the fact that the new power behavior is worse than it used to be. Even if that fixes other bugs, it's fixes crashes while simultaneously regressing power usage.

[deanjo]

There is plenty of evidence that it only impacted some systems, in past threads here, and elsewhere.

Which is a long ways away from your claim that it didn't even exist based on your "expertise" and "thousands of users".

[AlbertP]

It is called a regression because they at first thought it was.