Follow Slashdot stories on Twitter


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

Operating Systems Upgrades Linux

Linux 2.6.39 Released 76

Posted by timothy
from the domo-arigato dept.
Rainmaker2006 writes "The latest iteration of Linux kernel is out. The kernel 2.6.39 is listed in, ready to be yours!" Linux for Devices has a short overview of what you can expect in the newest kernel; an article at Phoronix (complete with obnoxious pop-out advertising) points out a few bugs, as well.
This discussion has been archived. No new comments can be posted.

Linux 2.6.39 Released

Comments Filter:
  • by feranick (858651) on Thursday May 19, 2011 @08:47PM (#36186876)
    Considering how vocal Linus has been in some very technical issues in the past, I am appalled to see how underplayed the power consumption issue has been. It's a *major* issue, 30% more power consumption is a deal breaker for many users. And instead, what do we see from the kernel list: Nothing. The regressions that lead to these came in since kernel 2.6.38, and they went by in 39. At this point, I seriously doubt about the QA going on at kernel level. For example do they keep track of these kind of regressions in first place? It seems that Phoronix is doing the admirable job, but it seems it's going completely unheard. I am hopeful that 2.6.40 will fix this mess.
  • by nukem996 (624036) on Thursday May 19, 2011 @10:40PM (#36187658)
    The bug will be fixed but its a very very complicated bug. All that is known is that somewhere between 2.6.37 and 2.6.38 some patch or patches caused the kernel to increase machine power usage. Finding the patch or patches that caused this is very difficult and thats just finding the bug. It then has to be debugged and fixed. One bug can't be a show stopper for everything else. Just give them some time.

Live free or die.