14.04.x HWE Stack EOL Notification
Hi, In an effort to support a wider variety of hardware within the Ubuntu 14.04 LTS release, the 14.04.2 and newer point releases shipped with hardware enablement stacks composed of updated kernels and graphics stacks. The intention has always been for these hardware enablement stacks to only remain supported until the introduction of the kernel and graphics stack derived from 16.04. On August 4, 2016, the 5th and final point release for 14.04 (ie. 14.04.5) will deliver the kernel and graphics stack derived from 16.04. At that time, security updates and bug fixes for older hardware enablement stacks will no longer be provided. All users of older hardware enablement stacks will be encouraged to update to the 16.04 hardware enablement stack or fully upgrade to the Ubuntu 16.04 LTS release. Instructions for updating will be provided in the 14.04.5 release notes and added to the following wiki as we approach the 14.04.5 point release. https://wiki.ubuntu.com/Kernel/LTSEnablementStack Thanks, The Ubuntu Kernel Team -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
12.04.x HWE Stack EOL Notification
Hi, In an effort to support a wider variety of hardware within the 12.04 Ubuntu LTS release, the 12.04.2 and newer point releases in Precise shipped with hardware enablement stacks composed of updated kernels and graphics stacks. The intention has always been for these hardware enablement stacks to only remain supported until the introduction of the kernel and graphics stack derived from 14.04. On August 7, 2014, the 5th and final point release for 12.04 (ie. 12.04.5) will deliver the kernel and graphics stack derived from 14.04. At that time, security updates and bug fixes for older hardware enablement stacks will no longer be provided. All users of older hardware enablement stacks will be encouraged to update to the 12.04.5 hardware enablement stack or fully upgrade to 14.04 proper. For any 12.04 HWE stack users interested in making this migration prior to the August 7, 2014 deadline, we have provided a mechanism to assist with this process. First, please ensure your system is up to date with the latest package updates for Precise. Then, run the command below and follow the instructions which are output: hwe-support-status --verbose For further information and details, please see: https://wiki.ubuntu.com/1204_HWE_EOL Thanks, Leann Ogasawara -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Ubuntu 14.04 Kernel Version and Configuration
Hi All, As we enter Kernel Freeze for the Ubuntu Trusty Tahr 14.04 release, the Ubuntu Kernel Team felt this would be an appropriate time to officially confirm the Ubuntu 14.04 kernel will be based on the upstream v3.13 Linux kernel [1]. For those seeking the specific details of all the changes provided in the Ubuntu 14.04 kernel, please refer to the ubuntu-trusty kernel git repository [2]. We have also categorized the Ubuntu specific changes in our TrustyKernelDeltaReview wiki for anyone interested [3]. We also want to take this time to advertise what we intend to be the final kernel configurations for the main distro kernel flavors as well. The purpose is to expose the main configuration changes and provide pointers to the full configurations for those who are interested. To aid in the comparison of kernel config changes from Ubuntu 13.10 (Saucy) to Ubuntu 14.04 (Trusty), we have generated a kernel configuration comparison report [4]. We have also posted the full Ubuntu 14.04 configurations for each arch and flavor [5]. Thanks, The Ubuntu Kernel Team [1] https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.13.tar.gz [2] http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-trusty.git;a=summary [3] https://wiki.ubuntu.com/KernelTeam/Specs/TrustyKernelDeltaReview [4] https://wiki.ubuntu.com/Kernel/Configs/SaucyToTrusty [5] http://kernel.ubuntu.com/~kernel-ppa/configs/trusty -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: [RFC] 12.04.5
On Sun, Feb 9, 2014 at 5:50 AM, Philipp Kern pk...@ubuntu.com wrote: On Fri, Feb 07, 2014 at 08:00:12AM -0800, Leann Ogasawara wrote: As many are aware, recent 12.04.x point releases have shipped with a newer kernel and X stack by default for hardware enablement purposes. Maintainers of these enablement stacks have agreed to support these until a Trusty based enablement stack is supported in Precise. Once a Trusty enablement stack is supported, all previous enablement stacks would EOL and be asked to migrate to the final Trusty based enablement stack which would continue to be supported for the remaining life of Precise. When would they EOL? When the new one lands in -updates? Or after the point release including it (w/ installer support)? We intended for them to EOL around the 14.04.1 time frame. I think it now seems reasonable to EOL them after 12.04.5 has released. Additionally, we would want to purposely avoid clashing the 14.04.1 and 12.04.5 release dates and would suggest releasing 14.04.1 first and 12.04.5 after (exact date TBD). What would the rough date for the Precise point release be then? August? The point releases have roughly held a 6 month release cadence and I don't believe that should change for 12.04.5. Since 12.04.4 released in February, August sounds like a reasonable estimate assuming we can avoid clashing with the 14.04.1 release. It might be more realistic to push 12.04.5 to September, but I'll leave that to the discretion of the Ubuntu Release Team. Thanks, Leann -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[RFC] 12.04.5
Hi All, With 12.04.4 having just released, I wanted to propose the idea of having a 12.04.5 point release for Precise. As many are aware, recent 12.04.x point releases have shipped with a newer kernel and X stack by default for hardware enablement purposes. Maintainers of these enablement stacks have agreed to support these until a Trusty based enablement stack is supported in Precise. Once a Trusty enablement stack is supported, all previous enablement stacks would EOL and be asked to migrate to the final Trusty based enablement stack which would continue to be supported for the remaining life of Precise. Currently, 12.04.4 is our final point release for Precise. 12.04.4 shipped with a Saucy enablement stack by default. This Saucy enablement stack in Precise will eventually EOL in favor of the Trusty enablement stack. Once that happens, our final point release for Precise will be delivering an EOL'd enablement stack. This seems unfortunate and inappropriate. I would like to propose having a 5th point release for Precise which would deliver the Trusty enablement stack for Precise. Providing a 12.04.5 point release will add no additional maintenance burden upon teams supporting enablement stacks in Precise. It would require some extra effort on part of the Canonical Foundations Team as well as the Ubuntu Release Team to spin up an additional set of images and testing coordination etc. However, I informally discussed this with a few members of each of those teams and the tentative agreement was that 12.04.5 was a reasonable request which could be accommodated. Collectively we could find no compelling reason to not provide 12.04.5. We also discussed that a 12.04.5 release should be optional for the Flavors to participate in. Additionally, we would want to purposely avoid clashing the 14.04.1 and 12.04.5 release dates and would suggest releasing 14.04.1 first and 12.04.5 after (exact date TBD). What are other's thoughts here? Does anyone have a compelling reason for not providing a 12.04.5 point release? Thanks, Leann -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Ubuntu 13.10 Kernel Version and Configuration
Hi All, Now that we are past the Ubuntu Saucy Salamander 13.10 Kernel Freeze, the Ubuntu Kernel Team felt this would be an appropriate time to officially confirm the Ubuntu 13.10 kernel will be based on the upstream v3.11 Linux kernel [1]. For those seeking the specific details of all the changes provided in the Ubuntu 13.10 kernel, please refer to the ubuntu-saucy git repository [2]. We have also categorized the Ubuntu specific changes in our SaucyKernelDeltaReview wiki for anyone interested [3]. We also want to take this time to advertise what we intend to be the final kernel configurations for the main distro kernel flavors as well. The purpose is to expose the main configuration changes and provide pointers to the full configurations for those who are interested. To aid in the comparison of kernel config changes from Ubuntu 13.04 (Raring) to Ubuntu 13.10 (Saucy), we have generated a kernel configuration comparison report [4]. We have also posted the full Ubuntu 13.10 configurations for each arch and flavor [5]. Thanks, The Ubuntu Kernel Team [1] https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.11.tar.gz [2] http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-saucy.git;a=summary [3] https://wiki.ubuntu.com/KernelTeam/Specs/SaucyKernelDeltaReview [4] https://wiki.ubuntu.com/Kernel/Configs/RaringToSaucy [5] http://kernel.ubuntu.com/~kernel-ppa/configs/saucy/ -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Ubuntu 13.04 Kernel Configuration
Hi All, Now that we are past the Ubuntu Raring Ringtail 13.04 Kernel Freeze, the Ubuntu Kernel Team felt this would also be an appropriate time to advertise what we intend to be the final kernel configurations for the main distro kernel flavors. The purpose is to expose the main configuration changes and provide pointers to the full configurations for those who are interested. To aid in the comparison of kernel config changes from Ubuntu 12.10 (Quantal) to Ubuntu 13.04 (Raring), we have generated a kernel configuration comparison report [1]. We have also posted the full Ubuntu 13.04 configurations for each arch and flavor. Thanks, The Ubuntu Kernel Team [1] https://wiki.ubuntu.com/Kernel/Configs/QuantalToRaring [2] http://kernel.ubuntu.com/~kernel-ppa/configs/raring/ -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Let's Discuss Interim Releases (and a Rolling Release)
On 02/28/2013 12:49 PM, David Henningsson wrote: On 02/28/2013 05:09 PM, Martin Pitt wrote: * Keep doing daily quality and keep improving our daily quality. Big +1. I'm particularly looking forward to integrating our automatic package tests with britney. The QA work done in -proposed has increased the productivity for the rest of us, no doubt about that. But still, a word of caution here. Every piece of code even remotely related to the hardware, not only the Linux kernel but also most of the plumbing layer, is quite difficult (or even impossible) to automate testing for. Even if we would set up robots in our lab looking at the screen for artifacts, talking into the microphone and so on, we wouldn't cover the world's hardware. Hardware becomes increasingly complex, diverse, and so testing it takes a lot of time. You can't go test thousands of machines to see if their headphone outputs stopped working every single day. Do we have a plan to deal with those types of bugs? Somewhat related, I'm also wondering about the backport kernels we recently started working with. E g, in the development release we've been uploading 3.8-rc kernels rather than waiting until they're stable, this allows us to catch regressions and fix them early. Then we stay for a while and skip a kernel version or two - this helps us make a more stable backport kernel, and the six months cycle give some natural points for testing hardware too. What's the kernel's upload policy going to be for the rolling release? Do we upload kernels in the beginning of rc cycle, middle of rc cycle, at the stable release, or...? Hi David, I've also scheduled a UDS blueprint [1] for this very discussion. At the session I want to address all the questions you've raised above as well as some additional items. Please feel free to subscribe to that blueprint and participate. We'd very much value your input. Thanks, Leann [1] https://blueprints.launchpad.net/ubuntu/+spec/client-1303-rolling-kernel-maintenance = Why Now? = There are two answers for this. 1. Because of Convergence 2. Because we can You forgot the One True Reason for Why Now?: I'm sure that it was never meant to be a Raring Ringtail, but always a Rolling Release! We couldn't do it at any other point in time. The real reason is of course that we're running out of letters; this way we're slowing down our letter consumption by a factor 4, this buys us like, 12 more years or so! -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Ubuntu 12.10 Kernel Version
Hi All, Now that we are past the Ubuntu Quantal Quetzal 12.10 Kernel Freeze, the Ubuntu Kernel Team felt this would be an appropriate time to officially confirm and announce that the Ubuntu 12.10 kernel will be based on the upstream v3.5 Linux kernel [1]. Going forward, we'll continue to update the Ubuntu 12.10 kernel with the latest upstream v3.5.y Linux stable kernel releases. For those seeking the specific details of all the changes provided in the Ubuntu 12.10 kernel, please refer to the ubuntu-quantal git repository [2]. We've also categorized the Ubuntu specific changes in our QKernelDeltaReview wiki for anyone interested [3]. Thanks, The Ubuntu Kernel Team [1] http://www.kernel.org/pub/linux/kernel/v3.x/linux-3.5.tar.gz [2] http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-quantal.git;a=summary [3] https://wiki.ubuntu.com/KernelTeam/Specs/QKernelDeltaReview -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Ubuntu 12.10 Kernel Configuration
Hi All, Now that we are past the Ubuntu Quantal Quetzal 12.10 Kernel Freeze, the Ubuntu Kernel Team felt this would also be an appropriate time to advertise what we intend to be the final kernel configurations for all the main distro and ports kernel flavors. The purpose is to expose the main configuration changes and provide pointers to the full configurations for those who are interested. To aid in the comparison of kernel config changes from Ubuntu 12.04 (Precise) to Ubuntu 12.10 (Quantal), we have generated a kernel configuration comparison report [1]. We have also posted the full Ubuntu 12.04 and Ubuntu 12.10 configurations for each flavor [2]. Thanks, The Ubuntu Kernel Team [1] https://wiki.ubuntu.com/Kernel/Configs/PreciseToQuantal [2] http://kernel.ubuntu.com/~kernel-ppa/configs -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: LTS Enablement Stack
On 08/10/2012 02:05 PM, Leann Ogasawara wrote: Hi Everyone, At UDS-Q we began discussions for how we will provide enablement stack offerings in the Precise 12.04 LTS release, eg. provide the 12.10 Kernel and X.org in 12.04 beginning with the 12.04.2 point release. We captured plenty of feedback during these discussions and noted numerous areas which still needed sorting as we move through the Quantal devel cycle [A,B,C]. Logistics regarding support time frames, image seeding, and upgrade paths/policies were all of specific concern. With the Quantal devel cycle well under way and the 12.04.2 point release a few months away, I've been attempting to drive many of the remaining areas of concern to a resolution. I thought I would take this opportunity to share a current status of where we are. Please note I've marked some items [TBD] as they are still undergoing review and discussion: 1. For the 12.04.2 CD's, we will default to the new Quantal enablement stack. Due to size limitations we are unable to provide options for both the Quantal enablement stack and the original Precise stack. 2. [TBD] For the 12.04.2 DVD's, we will default to the new Quantal enablement stack but are also actively investigating the possibility of providing an option to allow users to remain on the original Precise stack. 3. The 12.04.0 and 12.04.1 point releases will be archived and available at old-releases.ubuntu.com. 4. For the 12.04.2 CD's (and possibly the 12.04.2 DVD's if we are unable to provide an option to remain on the original Precise stack for the DVD's), we will message that anyone installing and wishing to remain on the original 12.04 stack to please install from the 12.04.0 or 12.04.1 media and update. Just expanding on item #4 with some additional details which were just discussed on #ubuntu-devel: * For the 12.04.2 point release, https://help.ubuntu.com/ and http://www.ubuntu.com/download/desktop should be updated to message/notify users that they do have the option to install with the 12.04.1 media as an alternative to remain on the original Precise stack. A link to the 12.04.1 media which will be archived at old-releases.ubuntu.com should also be referenced in this message. Thanks, Leann 1. We only intend to support enablement stack package combinations in 12.04 which are derived from the same release, eg. the 12.10 X.org must be used in conjunction with the 12.10 kernel and vice versa. Intermixing a 12.10 enablement kernel with the 12.04 X.org stack or a 12.10 enablement X.org stack with a 12.04 kernel will not be officially tested nor supported. 2. Anyone running with the original Precise stack will not be automatically updated to the new Quantal enablement stack. Users can electively choose to install the Quantal (or newer) enablement stack meta package if they wish to do so. 3. Additionally, anyone upgrading to Precise will not be automatically upgraded to the new Quantal enablement stack. Again, they can electively choose to do so by manually installing the appropriate meta package. 4. The original 12.04 stack in Precise will remain supported for the usual 5yr life cycle of the LTS release. 5. Anyone running with the newer Quantal enablement stack will remain on that stack until the following 14.04 LTS enablement stack is available and supported in 12.04. Users will *not* be automatically rolled forward to interim non-LTS enablement stack offerings. * If anyone is interested in updating to newer enablement stack offerings in Precise as they become available, we will provide series specific meta packages which they can manually choose to install. We will also provide a rolling release meta package for those who do want to roll forward automatically. Again, this will be an elective package install and not mandatory. 6. When an interim non-LTS enablement stack offering (ie Q|R|S enablement stack in P) reaches it's EOL, users will be automatically rolled forward to the 14.04 LTS enablement stack, eg 12.10 enablement stack users will be automatically upgraded to the 14.04 enablement stack in Precise upon the 12.10 enablement stack reaching it's EOL. This will ensure a continuous line of support. See item 11 below for follow on discussions. 7. [TBD] The interim non-LTS enablement stacks (ie Q|R|S enablement stacks in P) will only be supported in Precise from the time they appear in a point release through the remainder of their natural release life cycle, eg the 12.10 enablement stack will be supported for 15mo in Precise due to the 3mo offset between 12.10's official release and the 12.04.2 point release. * There are concerns that 12.10 will EOL at the same time 14.04 is released. Some are in favor
LTS Enablement Stack
Hi Everyone, At UDS-Q we began discussions for how we will provide enablement stack offerings in the Precise 12.04 LTS release, eg. provide the 12.10 Kernel and X.org in 12.04 beginning with the 12.04.2 point release. We captured plenty of feedback during these discussions and noted numerous areas which still needed sorting as we move through the Quantal devel cycle [A,B,C]. Logistics regarding support time frames, image seeding, and upgrade paths/policies were all of specific concern. With the Quantal devel cycle well under way and the 12.04.2 point release a few months away, I've been attempting to drive many of the remaining areas of concern to a resolution. I thought I would take this opportunity to share a current status of where we are. Please note I've marked some items [TBD] as they are still undergoing review and discussion: 1. For the 12.04.2 CD's, we will default to the new Quantal enablement stack. Due to size limitations we are unable to provide options for both the Quantal enablement stack and the original Precise stack. 2. [TBD] For the 12.04.2 DVD's, we will default to the new Quantal enablement stack but are also actively investigating the possibility of providing an option to allow users to remain on the original Precise stack. 3. The 12.04.0 and 12.04.1 point releases will be archived and available at old-releases.ubuntu.com. 4. For the 12.04.2 CD's (and possibly the 12.04.2 DVD's if we are unable to provide an option to remain on the original Precise stack for the DVD's), we will message that anyone installing and wishing to remain on the original 12.04 stack to please install from the 12.04.0 or 12.04.1 media and update. 5. We only intend to support enablement stack package combinations in 12.04 which are derived from the same release, eg. the 12.10 X.org must be used in conjunction with the 12.10 kernel and vice versa. Intermixing a 12.10 enablement kernel with the 12.04 X.org stack or a 12.10 enablement X.org stack with a 12.04 kernel will not be officially tested nor supported. 6. Anyone running with the original Precise stack will not be automatically updated to the new Quantal enablement stack. Users can electively choose to install the Quantal (or newer) enablement stack meta package if they wish to do so. 7. Additionally, anyone upgrading to Precise will not be automatically upgraded to the new Quantal enablement stack. Again, they can electively choose to do so by manually installing the appropriate meta package. 8. The original 12.04 stack in Precise will remain supported for the usual 5yr life cycle of the LTS release. 9. Anyone running with the newer Quantal enablement stack will remain on that stack until the following 14.04 LTS enablement stack is available and supported in 12.04. Users will *not* be automatically rolled forward to interim non-LTS enablement stack offerings. * If anyone is interested in updating to newer enablement stack offerings in Precise as they become available, we will provide series specific meta packages which they can manually choose to install. We will also provide a rolling release meta package for those who do want to roll forward automatically. Again, this will be an elective package install and not mandatory. 10. When an interim non-LTS enablement stack offering (ie Q|R|S enablement stack in P) reaches it's EOL, users will be automatically rolled forward to the 14.04 LTS enablement stack, eg 12.10 enablement stack users will be automatically upgraded to the 14.04 enablement stack in Precise upon the 12.10 enablement stack reaching it's EOL. This will ensure a continuous line of support. See item 11 below for follow on discussions. 11. [TBD] The interim non-LTS enablement stacks (ie Q|R|S enablement stacks in P) will only be supported in Precise from the time they appear in a point release through the remainder of their natural release life cycle, eg the 12.10 enablement stack will be supported for 15mo in Precise due to the 3mo offset between 12.10's official release and the 12.04.2 point release. * There are concerns that 12.10 will EOL at the same time 14.04 is released. Some are in favor of driving a more rigorous QA effort of the 14.04 enablement stack in 12.04 to ensure an immediate and smooth transition to the 14.04 enablement stack on the day the 12.10 enablement stack EOL's. This would also likely result in an increased level of quality for the initial 14.04 release due to the extra testing focus. Others are however more conservative and would prefer we not offer the 14.04 enablement stack in Precise until the 14.04.1 time frame. We commonly message that users should not be using an LTS release for production environments until the .1
[CFT - Closed] RC6 Enabled by Default on Sandy Bridge
Hi All, I just wanted to send a note to announce that the RC6 call for testing is now officially closed. We appreciate all of the testing feedback we received. It had a direct impact and influence on our decision to enable plain RC6 by default for Precise. Between the testing feedback we received and interaction with the upstream developers, we were also able to find and fix a handful of RC6 related issues. Kudos to all involved. Thanks, Leann Ogasawara On Fri, 2012-02-24 at 13:57 -0800, Leann Ogasawara wrote: On Thu, 2012-02-23 at 21:21 -0800, Leann Ogasawara wrote: On Sat, 2012-02-18 at 13:07 -0800, Leann Ogasawara wrote: [...] If you are running Ubuntu 12.04 (Precise Pangolin) and willing to test and provide feedback, please refer to our PowerManagementRC6 wiki for detailed instructions [3]. Additionally, instructions for reporting any issues with RC6 enabled are also noted on the wiki. We would really appreciate any testing and feedback users are able to provide. I first want to thank everyone who has already tested and provided their feedback. It is very much appreciated. There has however been some recent developments with the current RC6 patch which originated this call for testing. An adjustment has been made to that original patch: http://lists.freedesktop.org/archives/intel-gfx/2012-February/015319.html We're hoping this fix resolves the remaining issues when RC6 is enabled by default. A test kernel has already been built and posted to the RC6 bugs noted in the PowerManagementRC6 wiki [3]. For anyone else who was interested in testing, and wants to re-test, I ask that you please hold off until we are able to upload this additional fix. I hope to get a Beta Freeze exception for this and intend follow up with the Release Team accordingly. I will respond to this email once we have an official kernel in the archive ready for additional testing. We have uploaded a new Ubuntu kernel, v3.2.0-17.27, which contains the latest RC6 fix [4]. For anyone who tested previously, if you would be willing to re-test with this newer kernel, that would be great. I'd especially like to request that anyone who saw issues with RC6 when testing earlier to please re-test. Thanks again for all of the testing effort and feedback so far. I do apologize for the additional testing requests being made, but it is very much appreciated. Thanks, Leann Ogasawara [1] http://phoronix.com/forums/showthread.php?68199-Intel-Wants-YOUR-Linux-Questions-Feedbackp=246785#post246785 [2] http://lists.freedesktop.org/archives/intel-gfx/2012-February/015131.html [3] https://wiki.ubuntu.com/Kernel/PowerManagementRC6 [4] https://launchpad.net/ubuntu/+source/linux/3.2.0-17.27 -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Ubuntu 12.04 Kernel Version - 3.2
Hi All, Now that we are past the Ubuntu Precise Pangolin 12.04 Kernel Freeze, the Ubuntu Kernel Team felt this would be an appropriate time to officially confirm and announce that the Ubuntu 12.04 kernel will be based on the upstream v3.2 Linux kernel [1]. Going forward, we'll continue to update the Ubuntu 12.04 kernel with the latest upstream v3.2.y Linux stable kernel releases. For those seeking the specific details of all the changes provided in the Ubuntu 12.04 kernel, please refer to the ubuntu-precise git repository [2]. We've also categorized the Ubuntu specific changes in an UbuntuDelta wiki for anyone interested [3]. Thanks, The Ubuntu Kernel Team [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=805a6af8dba5dfdd35ec35dc52ec0122400b2610 [2] http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-precise.git;a=summary [3] https://wiki.ubuntu.com/Kernel/FAQ/UbuntuDelta -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Ubuntu 12.04 Kernel Configurations
Hi All, Now that we are past the Ubuntu Precise Pangolin 12.04 Kernel Freeze, the Ubuntu Kernel Team felt this would also be an appropriate time to advertise what we intend to be the final kernel configurations for all the main distro and ports kernel flavors. The purpose is to expose the main configuration changes and provide pointers to the full configurations for those who are interested. To aid in the comparison of kernel config changes from Ubuntu 11.10 (Oneiric) to Ubuntu 12.04 (Precise) we have generated a kernel configuration comparison report [1]. We have also posted the full Ubuntu 11.10 and Ubuntu 12.04 configurations for each flavor [2]. Thanks, The Ubuntu Kernel Team [1] https://wiki.ubuntu.com/Kernel/Configs/OneiricToPrecise [2] http://kernel.ubuntu.com/~kernel-ppa/configs -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: [RFC] Drop Non-smp PowerPC Kernel Flavor
On Tue, 2012-03-20 at 06:53 +, Adam Conrad wrote: On Tue, Mar 20, 2012 at 02:30:14PM +0800, Jeremy Kerr wrote: Benh pointed out 78c5c68a; which looks like it'll address this. I've built some packages: http://people.canonical.com/~jk/powerpc-oldworld-smp/ - let me know if the -smp flavour works on your machine. Huzzah. That does indeed fix it, that build boots on my machine. I guess now I have to give up my UP kernel, eh? :P Jeremy and Ben, thanks for chasing down this fix. I've gone ahead and applied it to our Precise git repo and it should be available in the next upload. Adam, given the above issue is now resolved for you. I would like to proceed with our original proposal of removing the non-smp PowerPC flavor. In the event we uncover any further issues which would require us to reinstate the non-smp PowerPC flavor, we will proceed with the alternative solution as outlined in [1]. Thanks, Leann [1] https://lists.ubuntu.com/archives/ubuntu-devel/2012-March/034964.html -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[RFC] Drop Non-smp PowerPC Kernel Flavor
Hi All, The Ubuntu Kernel Team has been evaluating some of the current maintenance burdens for the upcoming Precise Pangolin 12.04 LTS release. One area which would reduce the maintenance costs would be to drop the non-smp PowerPC kernel flavor. There are currently three PowerPC flavors: * non-smp (linux-image-powerpc) * smp (linux-image-powerpc-smp) * smp-64 (linux-image-powerpc64-smp) Even though PowerPC is a community maintained port [1], the PowerPC kernels are still generated along side the officially supported distro kernels. Taking that into consideration, every PowerPC flavor takes ~2hrs to build, ie. ~6hrs for all three flavors. Given the number of official builds and test builds that are performed over the life of the LTS, this equates to a significant amount of time. We would thus like to propose dropping the non-smp PowerPC kernel flavor. Doing so would also require the installer to be updated, hence CC'ing Colin Watson. We'd like to drop this as soon as possible, in time for Beta-2 would be ideal. Thoughts? Thanks, Leann Ogasawara [1] https://lists.ubuntu.com/archives/ubuntu-announce/2007-February/98.html -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: [RFC] Drop Non-smp PowerPC Kernel Flavor
On Wed, 2012-03-14 at 11:59 -0500, Micah Gersten wrote: On 03/14/2012 11:52 AM, Leann Ogasawara wrote: Hi All, The Ubuntu Kernel Team has been evaluating some of the current maintenance burdens for the upcoming Precise Pangolin 12.04 LTS release. One area which would reduce the maintenance costs would be to drop the non-smp PowerPC kernel flavor. There are currently three PowerPC flavors: * non-smp (linux-image-powerpc) * smp (linux-image-powerpc-smp) * smp-64 (linux-image-powerpc64-smp) Even though PowerPC is a community maintained port [1], the PowerPC kernels are still generated along side the officially supported distro kernels. Taking that into consideration, every PowerPC flavor takes ~2hrs to build, ie. ~6hrs for all three flavors. Given the number of official builds and test builds that are performed over the life of the LTS, this equates to a significant amount of time. We would thus like to propose dropping the non-smp PowerPC kernel flavor. Doing so would also require the installer to be updated, hence CC'ing Colin Watson. We'd like to drop this as soon as possible, in time for Beta-2 would be ideal. Thoughts? Thanks, Leann Ogasawara [1] https://lists.ubuntu.com/archives/ubuntu-announce/2007-February/98.html What's the impact on supported PowerPC hardware? Jeremy Kerr did some testing a while back and noted that the PowerPC smp flavor should run on non-smp hardware, but did acknowledge there could be a slight performance degradation. Jeremy, do you still have the data available? Thanks, Leann -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: [CFT] RC6 Enabled by Default on Sandy Bridge
On Thu, 2012-02-23 at 21:21 -0800, Leann Ogasawara wrote: On Sat, 2012-02-18 at 13:07 -0800, Leann Ogasawara wrote: [...] If you are running Ubuntu 12.04 (Precise Pangolin) and willing to test and provide feedback, please refer to our PowerManagementRC6 wiki for detailed instructions [3]. Additionally, instructions for reporting any issues with RC6 enabled are also noted on the wiki. We would really appreciate any testing and feedback users are able to provide. I first want to thank everyone who has already tested and provided their feedback. It is very much appreciated. There has however been some recent developments with the current RC6 patch which originated this call for testing. An adjustment has been made to that original patch: http://lists.freedesktop.org/archives/intel-gfx/2012-February/015319.html We're hoping this fix resolves the remaining issues when RC6 is enabled by default. A test kernel has already been built and posted to the RC6 bugs noted in the PowerManagementRC6 wiki [3]. For anyone else who was interested in testing, and wants to re-test, I ask that you please hold off until we are able to upload this additional fix. I hope to get a Beta Freeze exception for this and intend follow up with the Release Team accordingly. I will respond to this email once we have an official kernel in the archive ready for additional testing. We have uploaded a new Ubuntu kernel, v3.2.0-17.27, which contains the latest RC6 fix [4]. For anyone who tested previously, if you would be willing to re-test with this newer kernel, that would be great. I'd especially like to request that anyone who saw issues with RC6 when testing earlier to please re-test. Thanks again for all of the testing effort and feedback so far. I do apologize for the additional testing requests being made, but it is very much appreciated. Thanks, Leann Ogasawara [1] http://phoronix.com/forums/showthread.php?68199-Intel-Wants-YOUR-Linux-Questions-Feedbackp=246785#post246785 [2] http://lists.freedesktop.org/archives/intel-gfx/2012-February/015131.html [3] https://wiki.ubuntu.com/Kernel/PowerManagementRC6 [4] https://launchpad.net/ubuntu/+source/linux/3.2.0-17.27 -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: [CFT] RC6 Enabled by Default on Sandy Bridge
On Sat, 2012-02-18 at 13:07 -0800, Leann Ogasawara wrote: [...] If you are running Ubuntu 12.04 (Precise Pangolin) and willing to test and provide feedback, please refer to our PowerManagementRC6 wiki for detailed instructions [3]. Additionally, instructions for reporting any issues with RC6 enabled are also noted on the wiki. We would really appreciate any testing and feedback users are able to provide. I first want to thank everyone who has already tested and provided their feedback. It is very much appreciated. There has however been some recent developments with the current RC6 patch which originated this call for testing. An adjustment has been made to that original patch: http://lists.freedesktop.org/archives/intel-gfx/2012-February/015319.html We're hoping this fix resolves the remaining issues when RC6 is enabled by default. A test kernel has already been built and posted to the RC6 bugs noted in the PowerManagementRC6 wiki [3]. For anyone else who was interested in testing, and wants to re-test, I ask that you please hold off until we are able to upload this additional fix. I hope to get a Beta Freeze exception for this and intend follow up with the Release Team accordingly. I will respond to this email once we have an official kernel in the archive ready for additional testing. Thanks again, Leann Ogasawara [1] http://phoronix.com/forums/showthread.php?68199-Intel-Wants-YOUR-Linux-Questions-Feedbackp=246785#post246785 [2] http://lists.freedesktop.org/archives/intel-gfx/2012-February/015131.html [3] https://wiki.ubuntu.com/Kernel/PowerManagementRC6 -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[CFT] RC6 Enabled by Default on Sandy Bridge
Hi All, RC6 is a technology which allows the GPU to go into a very low power consumption state when the GPU is idle (down to 0V). It results in considerable power savings when this stage is activated. When comparing under idle loads with machine state where RC6 is disabled, improved power usage of around 40-60% has been witnessed [1]. Up until recently, RC6 was disabled by default for Sandy Bridge systems due to reports of hangs and graphics corruption issues when RC6 was enabled. Intel has now asserted that RC6p (deep RC6) is responsible for the RC6 related issues on Sandy Bridge. As a result, a patch has recently been submitted upstream to disable RC6p for Sandy Bridge [2]. In an effort to provide more exposure and testing for this proposed patch, the Ubuntu Kernel Team has applied this patch to 3.2.0-17.26 and newer Ubuntu 12.04 Precise Pangolin kernels. We have additionally enabled plain RC6 by default on Sandy Bridge systems so that users can benefit from the improved power savings by default. We have decided to post a widespread call for testing from Sandy Bridge owners running Ubuntu 12.04. We hope to capture data which supports the the claims of power saving improvements and therefore justify keeping these patches in the Ubuntu 12.04 kernel. We also want to ensure we do not trigger any issues due to plain RC6 being enabled by default for Sandy Bridge. If you are running Ubuntu 12.04 (Precise Pangolin) and willing to test and provide feedback, please refer to our PowerManagementRC6 wiki for detailed instructions [3]. Additionally, instructions for reporting any issues with RC6 enabled are also noted on the wiki. We would really appreciate any testing and feedback users are able to provide. Thanks in advance, The Ubuntu Kernel Team [1] http://phoronix.com/forums/showthread.php?68199-Intel-Wants-YOUR-Linux-Questions-Feedbackp=246785#post246785 [2] http://lists.freedesktop.org/archives/intel-gfx/2012-February/015131.html [3] https://wiki.ubuntu.com/Kernel/PowerManagementRC6 -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Minutes from the Ubuntu Kernel Team meeting, 2011-11-22
= Meeting Minutes = http://irclogs.ubuntu.com/2011/11/22/%23ubuntu-meeting.txt http://voices.canonical.com/kernelteam == Agenda == https://wiki.ubuntu.com/KernelTeam/Meeting#Tues, 22 Nov, 2011 === ARM Status === Precise/omap4: first kernel upload done (3.0.0-1401.2) - still based on Oneiric source code but the configuration has been synced with master. Misc: besides the usual SRU kernels, there's nothing else to report. === Release Metrics and Incoming Bugs === precise nominated bugs * 32 linux kernel bugs (up 12) Ubuntu precise-alpha-1 bugs * 1 linux kernel bugs (up 1) series-updates bugs * 0 precise linux kernel bugs (no change 0) * 10 oneiric linux kernel bugs (no change 0) * 10 natty linux kernel bugs (no change 0) * 3 maverick linux kernel bugs (no change 0) * 7 lucid linux kernel bugs (no change 0) * 0 hardy linux kernel bugs (no change 0) === Incoming Bugs === * 8 precise bugs (no change 0) * 635 oneiric bugs (down 5) * 1677 natty bugs (down 3) * 1099 maverick bugs (no change 0) * 979 lucid bugs (down 4) * 43 hardy bugs (down 3) === Regressions === regression-update bugs * 0 precise bugs (no change 0) * 7 oneiric bugs (no change 0) * 19 natty bugs (no change 0) * 40 maverick bugs (no change 0) * 76 lucid bugs (no change 0) * 0 hardy bugs (no change 0) regression-release bugs * 1 precise bugs (no change 0) * 61 oneiric bugs (up 6) * 434 natty bugs (no change 0) * 236 maverick bugs (no change 0) * 208 lucid bugs (no change 0) * 2 hardy bugs (no change 0) regression-proposed bugs * 0 precise bugs (no change 0) * 1 oneiric bugs (no change 0) * 4 natty bugs (no change 0) * 0 maverick bugs (no change 0) * 2 lucid bugs (no change 0) * 0 hardy bugs (no change 0) === Milestone Targeted Work Items === || apw || hardware-p-kernel-boot|| 3 work items || || || hardware-p-kernel-delta-review|| 1 work item || || || foundations-p-ipv6|| 1 work item || || || desktop-o-xorg-stakeholders-request || 1 work item || || cking || hardware-p-kernel-version-and-flavors || 1 work item || || || hardware-p-kernel-delta-review|| 1 work item || || ogasawara || hardware-p-kernel-version-and-flavors || 1 work item || || || hardware-p-kernel-delta-review|| 2 work items || || sforshee || hardware-p-kernel-delta-review|| 1 work item || || smb || hardware-p-kernel-delta-review|| 1 work item || || tgardner || hardware-p-kernel-version-and-flavors || 1 work item || || || hardware-p-kernel-delta-review|| 1 work item || If your name is in the above table, please review your Alpha-1 work items and either get them closed or push them out to the next milestone. Remember, Alpha-1 is Thurs Dec 1. === Status: Precise Development Kernel === We have uploaded the 3.2.0-1.3 Ubuntu kernel which was based on the upstream v3.2-rc2 kernel. Please install and test on any kit you have. Feedback is appreciated. We've already discovered breakage with the wl DKMS package as well as some suspend/resume and shutdown issues on some Intel Atom kit. If there are any patches which need to land for Alpha-1, submit them now. Important Upcoming Dates: * Thurs Dec 1 - Alpha 1 (~ 1 week) === Status: CVE's === === CVE Metrics === Currently open CVEs for each supported branch: || Package || Open || || || || || linux Hardy ||8 || || linux Lucid ||5 || || linux Maverick ||5 (-1) || || linux Natty ||5 (-1) || || linux Oneiric||4 || || linux Precise||4 || || linux-ec2 Lucid ||5 || || linux-fsl-imx51 Lucid||5 || || linux-mvl-dove Lucid ||5 || || linux-mvl-dove Maverick ||5 || || linux-ti-omap4 Maverick ||5 (-2) || || linux-ti-omap4 Natty ||6 || || linux-ti-omap4 Oneiric ||4 || || linux-ti-omap4 Precise ||4 || || linux-lts-backport-maverick Lucid||5 (-1) || || linux-lts-backport-natty Lucid ||5 (-1) || || linux-lts-backport-oneiric Lucid ||4 || This week four new CVEs were added to the list. Progress remains slow and steady, overall we finish the week with about the same number of outstanding CVEs. One of the new CVEs currently awaits an upstream fix. === Status: Stable, Security, and Bugfix Kernel Updates - Oneiric/Natty/Maverick/Lucid/Hardy === Last week saw the verification and testing of the current -proposed updates. Here is
Ubuntu 11.10 Kernel Configurations
Hi All, With the Ubuntu 11.10 Kernel Freeze approaching, the Ubuntu Kernel Team felt this would also be an appropriate time to advertise what we intend to be the final kernel configurations for all the main distro and ports kernel flavors. The purpose is to expose the main configuration changes and provide pointers to the full configurations for those who are interested. To aid in the comparison of kernel config changes from Ubuntu 11.04 (Natty) to Ubuntu 11.10 (Oneiric) we have generated a delta report [1]. We have also posted the full Ubuntu 11.04 and Ubuntu 11.10 configurations for each flavor [2]. Thanks, The Ubuntu Kernel Team [1] https://wiki.ubuntu.com/Kernel/Configs/NattyToOneiric [2] http://kernel.ubuntu.com/~kernel-ppa/configs -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Ubuntu Kernel Team Meeting Minutes - 2011-08-16
= Meeting Minutes = [[http://irclogs.ubuntu.com/2011/08/16/%23ubuntu-meeting.txt|IRC Log of the meeting.]] BR [[http://voices.canonical.com/kernelteam|Meeting minutes.]] == Agenda == [[https://wiki.ubuntu.com/KernelTeam/Meeting#Tues, 16 Aug, 2011|20110816 Meeting Agenda]] === ARM Status === TOPIC: ARM Status (ppisati) Generic kernel arm: nothing interesting, besides lp709245 (ARM SMP scheduler performance bug) that is becoming a show stopper. Oneiric/ti-omap4: a new BSP/kernel update (1202.6) is in the pipe. Oneiric/tegra: nothing new to report. === Release Metrics and Incoming Bugs === === Release Metrics === TOPIC: Release Metrics and Incoming Bugs (ogasawara) oneiric nominated bugs * 31 linux kernel bugs (up 11) Ubuntu ubuntu-11.10-beta-1 bugs * 2 linux kernel bugs (up 2) series-updates bugs * 0 oneiric linux kernel bugs (no change 0) * 18 natty linux kernel bugs (down 1) * 3 maverick linux kernel bugs (no change 0) * 7 lucid linux kernel bugs (no change 0) * 0 hardy linux kernel bugs (no change 0) === Incoming Bugs === * 116 oneiric bugs (up 27) * 1511 natty bugs (up 19) * 1091 maverick bugs (up 2) * 954 lucid bugs (up 13) * 33 hardy bugs (up 2) === Regressions === regression-update bugs * 0 oneiric bugs (no change 0) * 13 natty bugs (no change 0) * 40 maverick bugs (down 1) * 78 lucid bugs (up 3) * 0 hardy bugs (no change 0) regression-release bugs * 3 oneiric bugs (up 2) * 439 natty bugs (no change 0) * 238 maverick bugs (down 2) * 215 lucid bugs (up 1) * 2 hardy bugs (no change 0) regression-proposed bugs * 1 oneiric bugs (up 1) * 3 natty bugs (up 1) * 1 maverick bugs (no change 0) * 1 lucid bugs (up 1) * 0 hardy bugs (no change 0) === Beta-1 Work Items === TOPIC: Beta-1 Work Items || apw || other-kernel-o-gcc-build-dependency || 1 work item || || || other-kernel-o-bug-handling || 2 work items|| || || other-kernel-o-version-and-flavours || 2 work items|| || || other-kernel-o-ubuntu-delta-review || 1 work item || || || desktop-o-xorg-stakeholders-request || 1 work item || || || desktop-o-xorg-tools-and-processes || 4 work items|| || lag || other-kernel-o-ubuntu-delta-review || 1 work item || || ogasawara || other-kernel-o-version-and-flavours || 2 work items|| || rsalveti || other-kernel-o-ubuntu-delta-review || 1 work item || || sarvatt || desktop-o-xorg-tools-and-processes || 1 work item || || sconklin || desktop-o-xorg-stakeholders-request || 1 work item || || smb || other-kernel-o-version-and-flavours || 1 work item || || tjaalton || other-kernel-o-ubuntu-delta-review || 1 work item || If you're listed in the table above, please review your work items. === Status: General Oneiric === TOPIC: Status: General Oneiric (ogasawara) Some important dates to keep in mind are as follows: * Aug 25 - Beta Freeze (~1 week) * Sept 1 - Beta 1 (~2 weeks) * Sept 15 - Kernel Freeze (~4 weeks) * Sept 22 - Beta 2 (~5 weeks) We'll continue pull in bug fixes and follow upstream stable v3.0.x as we move towards release. I'd also like to note that I've opened the P-series git repo and recently rebased it to v3.1-rc2. It's available in my personal repo on zinc - git://kernel.ubuntu.com/ogasawara/ubuntu-p.git . I'll make an official announcement to the mailing list shortly. === Status: CVE's === TOPIC: Status: CVE's (apw) == 2011-08-16 (weekly) == === CVE Metrics === Currently open CVEs for each supported branch: || Package || Open || || || || || linux Hardy ||7 || || linux Lucid ||3 || || linux Maverick ||3 || || linux Natty ||3 || || linux Oneiric||2 || || linux-ec2 Lucid ||3 || || linux-fsl-imx51 Lucid||3 || || linux-mvl-dove Lucid ||3 || || linux-mvl-dove Maverick ||3 || || linux-ti-omap4 Maverick ||3 || || linux-ti-omap4 Natty ||3 || || linux-ti-omap4 Oneiric ||2 || || linux-lts-backport-maverick Lucid||3 || || linux-lts-backport-natty Lucid ||3 || We have just found a regression introduced by one of the fixes for CVE-2011-1020. Investigation ongoing. === Status: Stable Kernel Team === TOPIC: Status: Stable Kernel Team (sconklin) ||== Status of kernels == || || This is kernel verification week. All kernels except Natty were ready for verification this || week, but a regression has been discovered in all kernels except Natty due to application of || a CVE patch. All kernels will be respun and further status will be announced when we have || estimated completion times for kernel prep. || || The CVE
Ubuntu 11.04 Kernel Configurations
Hi All, With the Ubuntu 11.04 Beta-1 release approaching, the Ubuntu Kernel Team felt this would also be an appropriate time to advertise what we intend to be the final kernel configurations for all the main distro and ports kernel flavors. The purpose is to expose the main configuration changes and provide pointers to the full configurations for those who are interested. To aid in the comparison of kernel config changes from Ubuntu 10.10 (Maverick) to Ubuntu 11.04 (Natty) we have generated a delta report [1]. We have also posted the full Ubuntu 10.10 and Ubuntu 11.04 configurations for each flavor [2]. Thanks, The Ubuntu Kernel Team [1] https://wiki.ubuntu.com/Kernel/Configs/MaverickToNatty [2] http://kernel.ubuntu.com/~kernel-ppa/configs -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Ubuntu 11.04 Kernel Version - 2.6.38
Hi All, With the Ubuntu 11.04 Beta-1 release approaching, the Ubuntu Kernel Team felt this would be an appropriate time to officially announce that the Ubuntu 11.04 kernel will be based on the 2.6.38 mainline kernel. The decision to target a 2.6.38 kernel was made during the Kernel Version and Flavors session [1] at UDS-Natty in Orlando, Florida. As Ubuntu 11.04 is not an LTS release and given the timing of the upstream kernel release, the Ubuntu Kernel Team felt that targeting the 2.6.38 kernel would provide our users the best support for new hardware, driver updates, and bug fixes. Going forward, we'll continue to update the Ubuntu 11.04 kernel with the upstream 2.6.38.y stable releases. For those seeking the fine grained details of all the changes provided in the Ubuntu 11.04 kernel, please refer to the git repository [2]. Thanks, The Ubuntu Kernel Team [1] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-version-and-flavours [2] http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-natty.git;a=summary -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Suspend/Resume Call for Testing - Ubuntu 9.04 Beta
Hi Everyone, With the Ubuntu Jaunty Jackalope 9.04 Beta release [1], the Ubuntu Kernel Team would like to request your assistance with suspend/resume testing. The team has been gathering information about Ubuntu's suspend/resume support for varying pieces of hardware. If you would like to participate and volunteer to perform tests, the Ubuntu Kernel Team has provided a suspend_test script [2]. The script has been packaged with checkbox 0.7 and should be available with the Jaunty 9.04 Beta release. The script will perform a number of suspend/resume tests. The first few tests will require human interaction. In total, the tests should take approximately 30min to complete and will perform 34 suspend/resume cycles. For information on how to run the script and other details, refer to the SuspendResumeTesting wiki [3]. Test results are also being tracked on the Ubuntu wiki [4] so please be sure to add any information for hardware that is not yet listed. Also, feel free to include any additional information for hardware that is currently listed. In the event that a test should fail, hooks have been added to apport to automatically detect failures and subsequently file a report in Launchpad. Upon rebooting the system after a failure, apport will try to gather as much information from the system and guide one through the bug filing process. Please be sure to also visit the corresponding debugging page [5] which documents additional requested information that apport is unable to gather. Please include this information in the bug report as well. The team appreciates all the time and feedback that can be dedicated to suspend/resume testing and reporting. Please let us know your results. Thanks in advance, The Ubuntu Kernel Team [1] http://www.ubuntu.com/testing/jaunty/beta [2] /usr/share/checkbox/scripts/suspend_test [3] https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting [4] https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting/Feedback [5] https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume -- ubuntu-devel-announce mailing list ubuntu-devel-announce@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce
