The Linux Kernel Power Issues Continues To Bite Users

[smitty3268]

@Michael
Have you found both of the regressions, then, or just one of them?
Also, will the fix be something that could be tacked into Linux 3.0, or is it large enough we'll probably have to wait for 3.1?

[ioannis]

http://www.phoronix.com/vr.php?view=15943 plus more coming...

Thanks Michael!

[allquixotic]

Is this bug eventually going to find its way into Android smartphones and tablets or is the kernel over there so far branched off the main path that it'd be unlikely to pick up this problem?

Android is still using 2.6.32 as far as I'm aware. 2.6.32 has a special place in a lot of big business' hearts. It just so happens that basically all the big players in the Linux ecosystem have at least one high-dollar product that is sitting on 2.6.32 with no sign of moving:

RHEL: 2.6.32 (with a few sensible backports from 2.6.37)
Ubuntu 10.04 LTS: 2.6.32
Android 2.2/2.3: 2.6.32 (plus a tremendous amount of Android-specific work)
Debian Stable: 2.6.32
SUSE Enterprise 11 SP1: 2.6.32
MeeGo: OK, they're using 2.6.37 in their git repo, but that doesn't mean 2.6.32 won't get picked up for product releases...


Since 2.6.32 preceded this power regression, I don't think the big enterprise customers really care at this point. Sure, it affects the enthusiast distros like Fedora, but the money making product (RHEL) isn't affected. Same with Android. You can go to a Verizon or AT&T store today and buy a top of the line Android phone, and it'll be running a heavily hacked 2.6.32.

Honestly, I'm more worried that we might start to see a very significant divergence in the kernel development community. The enterprise / embedded guys might decide they want to stick with 2.6.32 indefinitely, and just keep patching it until it looks nothing like vanilla 2.6.32, and is completely unmergeable between their fork and upstream. There's definitely a large enough pool of developers chasing money-making products built off of 2.6.32, and we are starting to see a decline in significant contributions to kernel upstream.

Ever wonder why Linus keeps enjoying an "uneventful RC"? I want them to be eventful. Submit huge patches! Contribute big features! We want them! But sadly, it isn't happening lately. Even the merges during the merge window are becoming more and more conservative.

[Michael]

Michael,

Do you have any results on older kernels, like 2.6.24 for instance. This was the kernel on Hardy Haron 8.04 and also the one used by WebOS until now (recently switched to 2.6.29).

Why? Just curious

http://www.phoronix.com/vr.php?view=15943 plus more coming...

[johnc]

Is this bug eventually going to find its way into Android smartphones and tablets or is the kernel over there so far branched off the main path that it'd be unlikely to pick up this problem?

[ioannis]

2.6.24

Michael,

Do you have any results on older kernels, like 2.6.24 for instance. This was the kernel on Hardy Haron 8.04 and also the one used by WebOS until now (recently switched to 2.6.29).

Why? Just curious

[Michael]

What has Red Hat got to do with it? Did you find a power issue in RHEL? Nope, you found or at least claim to have found a power issue in Ubuntu.

So if you have reported it it's up to Canonical or the Ubuntu community to fix this Ubuntu issue. Of course we all know this isn't going to happen because the whole business model of Canonical is based on freeloading.

So yes you are on your own, but since you didn't pay for Ubuntu you have no reason to complain anyway.

Fedora 15 is affected.

[Otus]

I understand waiting on publishing the article, but I really hope he's immediately given the info to those who need it to fix bugs!

[AnonymousCoward]

These problems have been hitting many users now in released distributions, yet the problem still isn't resolved. In fact, Canonical, Red Hat, or other ISV/IHVs haven't even inquired about the work I've been doing to narrow down the issue...

What has Red Hat got to do with it? Did you find a power issue in RHEL? Nope, you found or at least claim to have found a power issue in Ubuntu.

So if you have reported it it's up to Canonical or the Ubuntu community to fix this Ubuntu issue. Of course we all know this isn't going to happen because the whole business model of Canonical is based on freeloading.

So yes you are on your own, but since you didn't pay for Ubuntu you have no reason to complain anyway.

[HokTar]

@Michael:
Thanks for your hard work! All mobile users are indebted to you.

@ for the rest:
Interesting how you can't see the irony in the "revenue" thing.
I believe he is trying to piss off and get ahead of the trolls who would come and write that he's not yet releasing the cause for the regression but writing one more article just to gain a few more cents. While the real reason is probably that
a) he still needs to do more tests to be able to say that "that commit is the culprit"
b) as he noted on twitter he (and possibly others) are working on a patch to address the problem, hence he's planning to tell everything in one article.

Of course I can't rule out that he means what he says but I honestly doubt that.