Intrepid and 2.6.27

As I talked about in my last blog post we are considering moving to 2.6.27 for Ubuntu Intrepid Ibex. Ben posted this RFC to the ubuntu-devel list which outlines the rationale and technical benefits. This came late in the Intrepid development cycle and as such comes with risk and lots of questions such as:

• What are the regressions from 2.6.26 upstream and Ubuntu specific?
• Whats the plan "B" or fall back plan? When does it get invoked?
• What new "critical" bugs does 2.6.27 introduce?
• What existing 2.6.26 bugs does 2.6.27 fix?

We have and will continue to issue calls for testing and our QA team has been all over this since day one. We have been tracking all of these issues and then some. For those of you who wish to follow along at home here is my list of links:

• Ubuntu Regressions in 2.6.27 - https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-2.6.27
• New bugs in 2.6.27 - https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=linux-2.6.27
• Ubuntu bugs fixed by 2.6.27 https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=fixed-2.6.27
• Upstream kernel.org 2.6.27 regressions from 2.6.26 http://bugzilla.kernel.org/showdependencytree.cgi?id=11167&hide_resolved=1
  

I published the plan "B" with overlaid decision points here: https://wiki.ubuntu.com/KernelTeam/2.6.27-kernel-plan

As it stands now we shipped 2.6.27rc4 with Intrepid Alpha5. We noticed some big suspend/resume issues with Alpha5. I noticed these issues on the 3 dell notebooks that I have. We will be updating to 2.6.27rc5 shortly which should resolve the issues and fix even more bugs.

Hope folks find this useful...

~pete