Alpha 3 Milestoned Bugs

Release Targeted Bugs

linux

2

15

linux-fsl-imx51

3

3

linux-ec2

0

0

linux-mvl-dove

1

1

Blueprints: kernel-lucid-bug-handling

No update, all items are still in progress.

Blueprints: kernel-lucid-review-of-ubuntu-delta

drbd confirmed no longer in use with the server team and dropped from the kernel. Awaiting testing on the Lenovo driver combination which should close the last item here.

Blueprints: kerne-lucid-kernel-config-review

It seems we require SECCOMP enabled for Lucid, this is there for the distro kernels but under investigation for ARM.

Blueprints: kernel-lucid-kms

Upstream for DRM and upstream for the main drivers of interest, i915 and ATI, are all disavowing 2.6.32 indicating there is no hope of getting this working. As we are already backporting Nouveau from 2.6.33 we are now examining the feasability of a wholesale DRM backport as a better starting point. Testing ongoing, though all new issues are being shown up by this combination.

Blueprints: kernel-lucid-suspend-resume

Nothing new to report.

Blueprints: kernel-lucid-apparmor-development

Finally got another push to LKML out, working through the feedback. This update is now in the archive in lucid, we run whatever has been pushed upstream. This push is cleanups and code transforms requested by upstream.

Blueprints: kernel-lucid-boot-performance

We remain around the 1.6s to rootfs mark. khubd fixes are now uploaded and looking good.

Other Release Tasks: Lucid Audio Support

Nothing new to report.

Other Release Tasks: Lucid Better Power Mgt

Nothing new to report.

Other Release Tasks: EC2 Lucid Kernel Status

I (jjohansen) poked at running a pv-ops kernel again briefly, it looks promising but it needs to be run through all zones, and regions. Quesiont: What do we want to do if the pv-ops kernel is working? It would be nice to dump the xen patchset but it is getting aweful late. I (apw) presume that is much closer to the normal kernel? We could possibly get rid of the -ec2 kerenls but a lot more testing needs to be done to be sure. We might need to FF the change, but if it means we don’t need more than a flavour then its worth it I (jjohansen) redid pv-ops with some of the configs that we learned are problematic disabled. We would need a flavour but not a topic branch but a flavour is much less maintenance overhead. We will make this a high priority and get an answer before beta-1. We will get the server team involved as well.

Status: Lucid

Lucid is at stable v2.6.32.8, the khubd fixes have now hit the archive and boot times are looking better. We have potential issues with the HDA beep being discordant and loud, but this seems to be codec specific and not the nightmare screech issue we have had before, investigation ongoing. We also have graphics issues as discussed above, a decision will have to be taken in the next week as to direction. Progress has been pretty solid the last week, with us nearly hitting the trend-line for a day. The new issues above have pushed us back a little. I have been through the remaining Alpha-3 items and pushed any that are clearly not release critical out to ubuntu-10.04-beta-1, these include the apport changes etc which can easily be done after kerenel freeze. If I have pushed your items out and they are kernel related we do need something soon; be ta-1 is only 3 weeks out.

Security & Bugfix Kernels

Dapper

2.6.15-55.82

(security)

Hardy

2.6.24-27.65

(security)

2.6.24-27.67

(proposed)[0]

0/3 verifications done (+0)

Intrepid

2.6.27-17.45

(security)

Jaunty

2.6.28-18.59

(security)

Karmic

2.6.31-19.56

(security)

2.6.31-20.57

(proposed)[15]

5/19 verifications done (+1)

LBM

2.6.31-20.22

(proposed)[15]

0/ 2 verifications done

mvl-dove

2.6.31-211.22

(security)

2.6.31-211.23

(waiting for acceptance)

fsl-imx51

2.6.31-108.21

(security)

2.6.31-108.22

(proposed)[6]

0/ 1 verifications done (+0)

ec2

2.6.31-304.10

(security)

2.6.31-304.11

(proposed)[6]

0/ 1 verifications done (+0)

The mvl-dove upload is not processed, yet as there were questions about its impact by pitti which have not been answered. The questions are why it is needed and what is the impact. Working on getting a few more changes in Karmic proposed being verified. Likewise fsl-imx51 and ec2 interested parties should report back on the bugs in question.

Incoming Bugs: Regressions

Current regression stats (broken down by release):

regression-potential (up 30)

51 lucid bugs

regression-update (no change)

9 karmic bugs

5 jaunty bugs

2 intrepid bugs

1 hardy bug

regression-release (no change)

55 karmic bugs

23 jaunty bugs

11 intrepid bugs

4 hardy bugs

regression-proposed (no change)

1 karmic bug

Incoming Bugs: Bug day report

Last week’s BugDay was a success. Stats are available at:

http://qa.ubuntu.com/reports/jfo/kernel-bugday/20100216.html

The next Kernel BugDay is scheduled for next Tuesday the 2nd of March. The

focus will be Bugs with patches attached.

Open Discussion or Questions

None

Manoj Iyer

February 22nd, 2010 by Manoj Iyer

No Comments

Sunday was the final day at SCALE8x, We had good traffic at our booth,the loco team was bring us people with interesting problems and perspectives. I had this one person come up to me and express his dis-satisfaction about Ubuntu.

“I have a desktop that has an ATI Radeon card, and I can’t get the display to work. There are a lot of reports on the user forums about this card and canonical is not doing anything about it. I have emailed canonical about it but I see no action. Should I tell people to switch to fedora ?”

This person is a journalist, and I did not want him to give Ubuntu bad press because he did not know the correct process to get this problems resolved. Forums are for users to communicate with users, and when a solution is posted to the forum the thread is almost never closed, and users keep adding comments to it making it hard to find any useful information there. If you think you have a problem the correct process is to report a bug in launchpad. As an example, if sound does not work, and you have done some basic troubleshooting and found it to be a bug, reporting this bug is very easy. Open a terminal and run the following command.

$ ubuntu-bug audio

More serious kernel problems are automatically reported by apport. In the end, this journalist seemed less unhappy, but still insisted that the user experience is not what it is supposed to be, and that user experience is the reason that keep Apple Macs and Microsoft Windows in business. Point taken, you should not have to know about a process to report a problem, operating system should treat the user as dumb and do it under the covers, and apport does not to an extend.

One of the more serious issues I am seeing with Lucid is that with Nvidia binary drivers. On certain laptops, on boot, the display comes up fuzzy .

Fuzzy display with Nvidia binary drivers on Lucid. Alpha3

But you can easily fix this, just switch to VT1 and back to VT5, and you display will look almost normal. There are still some issues.

Problems with Nvidia binary drivers

I noticed this problem mostly on Sony Vaio W series notebooks, Compaq Presario V6000, and Toshiba Satellite S402. The Sony Vaio W series is particularly a bad case because it is a new model. Most of these laptops that had problems with Nvidia cards also had problems with suspend/resume working properly, and a bug in plymouth causes the system to freeze if you hit the “enter/return” key.

I made contacts with several of the vendors at the show. I talked to the owner of ZaReason he had all the models of his laptops/netbooks on display. They ships all of their netbooks/laptops with Ubuntu 9.10 preinstalled. I invited him over to our testing booth to test all his netbook/laptop models. He later promised to ship us some hardware to do some enablement and fix issues. I talked to the people from softlayer they use Ubuntu Server Edition on all their offerings. I need to connect them with the Server team people. The other interesting group I talked to was Revolution Linux. They already have partnership with Canonical. From a project perspective, looks like ltsp clusters is something we could use for our Hardware Compatibility Testing effort.

LTSP Cluster

We had no banners saying “Ubuntu Hardware Compatibility Test, please bring your laptops and help us test” so some people could not find us. We should do a better job of making us visible next time. We will do this again at the Texas Linux Fest on 10th April.

Manoj Iyer

February 20th, 2010 by Manoj Iyer

No Comments

We are on day two at SCALE8x, we did not have much traffic while the keynote was going on, we also lost the wireless network because they were streaming the keynote live and that sucked all the available bandwidth.

We are testing Laptops and Netbooks with latest Lucid Alpha. We have a pxe-boot server setup and also several USB sticks loaded with Lucid running kernel compatibility test suite on startup.

We are finding out that Nvidia graphics cards are causing major problems using the proprietary drivers. There was an announcement yesterday that Nouveau will be the default driver in Lucid, this seems to be the right step forward.

I am also having fun helping people fix issues they have with their laptop/netbook. A few minutes ago someone walked by with an Aspire one, and he complained that his wired ethernet card is not working. I booted it up with a Lucid USB key, found that he has a AR8132 nic that needed the alt1c module to work properly. Seems like his Mandriva is missing this module, but Lucid (10.4) ships with it, and his network worked off the bat. There were some laptops that refused to boot, Sony VAIO W Series Mini Notebook for instance does not boot with Lucid.

So, we are just starting the day, hoping more people will show up at our booth with new laptop/netbook that they want to test with Lucid.

Alpha 3 Milestoned Bugs

Release Targeted Bugs

linux

1

14

linux-fsl-imx51

3

4

linux-ec2

0

0

linux-mvl-dove

2

2

Blueprints: kernel-lucid-bug-handling

No update, all items are still in progress.

Blueprints: kernel-lucid-review-of-ubuntu-delta

Followed up on “under-discussion” patches, this led to four patches being dropped as they are no longer required.

Blueprints: kerne-lucid-kernel-config-review

Benchmarking pulling out PATA/SATA controllers appears to indicate there is a time penalty, we therefore need to look at the most common controllers to retain.

Blueprints: kernel-lucid-kms

There is much discussion regarding the quality of KMS for ATI Radeon. It seems that upstream is not interested in supporting KMS for ATI on 2.6.32. So far we have only one confirmed broken card, and we may have a small patch stack to make that workable. As we are already backporting Nouveau should we extend that to ATI; discussions continue.

Blueprints: kernel-lucid-suspend-resume

I am reworking patch as per amitk’s comments, will submit soon.

Blueprints: kernel-lucid-apparmor-development

Removed an unused feature that is potential security vulnerability (other option was complete the feature and do heavy code auditing). The feature could allow privilege escalation when combined with change_profile. No CVE as there is no way to exploit it with out it being explicitly used in policy, which has never happened except in experimentation. finished up policy optimization, it provided a 50% reduction in size and 4x speedup, also laid the ground work for further improvements (table sharing, and faster table compression) in the future. pam_apparmor update should be done later in the week. Fixing locking deadlock. The freeing of profiles has a race that can potentially deadlock. This can occur when free_profile is triggered from an rcu callback that is occurring at the same time as a profile replacement/removal.

Blueprints: kernel-lucid-boot-performance

We remain around the 1.6s to rootfs mark. We have one outstanding bug to do with new locking to protect USB strings which have become mutable as a result of the introduction of wireless USB hubs. Patches to fix this issue using RCU techniques are in testing.

Other Release Tasks: Lucid Audio Support

I’ve rolled the alsa c-o-d for karmic as well as lucid in the last week. It’s obvious that they are being used, which is good news.

Other Release Tasks: Lucid Better Power Mgt

Nothing new to report.

Other Release Tasks: EC2 Lucid Kernel Status

Looking good we had a small update regression last week that should be fixed now Bug #520015 (haven’t tested)

Status: Lucid

Lucid is now updated to stable v2.6.32.8 and to include a couple more [sigh] Ironlake patches. Light testing it seems no worse than previously. Progress was pretty good over the sprint week with us tending towards the trend-line (ie. catching up). Most of the prime features seem on track, graphics is still problematic.

Security & Bugfix Kernels

Dapper

2.6.15-55.82

(security)

Hardy

2.6.24-27.65

(security)

Intrepid

2.6.27-17.45

(security)

Jaunty

2.6.28-18.59

(security)

Karmic

2.6.31-19.56

(security)

2.6.31-20.57

(proposed)[8]

5/18 verifications done (+1)

LBM

2.6.31-20.22

(proposed)[8]

0/ 2 verifications done

mvl-dove

2.6.31-211.22

(security)

2.6.31-211.23

(waiting for acceptance)

fsl-imx51

2.6.31-108.21

(security)

2.6.31-108.22

(waiting for acceptance)

ec2

2.6.31-304.10

(security)

2.6.31-304.11

(waiting for acceptance)

Security release is done. This time it included updates to fsl-imx51, mvl-dove and ec2 packages. The ports-meta will be refreshed as well. confirmation. A new upload to Hardy proposed is waiting for approval and will also be done for netbook-lpia. The Karmic proposed upload includes a few more patches than before and also fixes a regression through 2.6.31.9 that was catched before.

Incoming Bugs: Regressions

Current regression stats (broken down by release):

regression-potential (up 14)

38 lucid bugs

regression-update (no change)

9 karmic bugs

5 jaunty bugs

2 intrepid bugs

1 hardy bug

regression-release (no change)

55 karmic bugs

22 jaunty bugs

11 intrepid bugs

4 hardy bugs

regression-proposed (no change)

1 karmic bug

Incoming Bugs: Bug day report

A gentle reminder that today is Kernel BugDay. If you have any spare cycles, your help would be greatly appreciated.

The information on this weeks bug focus (suspend resume bugs) is available at https://wiki.ubuntu.com/KernelTeam/BugDay/20100216

Last week’s bug day was postponed due to the previous week’s Platform Sprint.

Open Discussion or Questions

apw wants to remind everyone that we are freezing the kernel on March the 11th, which means we have to have everything ready and in by March 8th.

Lucid Release Status: Milestoned Features

Lucid Release Status: Bugs with patches attached

Blueprints: kernel-lucid-bug-handling

Arsenal scripts are currently running in dryrun mode daily. I am finishing up adding the -r option in each script to enable the actual run. Reviewed the X debugging pages. I have started working up an outline of what we need to put in place and how we can use most of what we already have to do it. I’m also making up a listing of what information needs to be updated on our wiki.

Blueprints: kernel-lucid-review-of-ubuntu-delta

Nothing to report this week.

Blueprints: kerne-lucid-kernel-config-review

Testing for any boot-speed regression with the PATA and SATA disk controllers removed is ongoing. We have also cleaned up those patches which were under discusssion, dropping a number of redundant patches.

Answer: That is part of what the first item there is about. I am planning to test that, and use that to start an email discussion on kernel-team.

Blueprints: kernel-lucid-kms

Preliminary testing with nouveau has been pretty good. An upload of the new Lucid LBM is pending in the New queue currently.

There is some discussion starting that KMS on radeon may be not as good as it could be and we need to figure out what if anything we need to do there also

I (manjo) am looking at backporting some patches for radeon that might fix some of the memory issues that are being reported.

Blueprints: kernel-lucid-suspend-resume

I have 2 patches:

Prints a lot of info driver:device:resumetime

Is based on tracepoints.

I have tested patch #1, and I am in the process of testing patch #2. I plan on tweaking patch #1 and carrying it as a sauce in Lucid.

Blueprints: kernel-lucid-apparmor-development

Removed an unused feature that is potential security vulnerability (other option was complete the feature and do heavy code auditing). The feature could allow privilege escalation when combined with change_profile. No CVE as there is no way to exploit it with out it being explicitly used in policy, which has never happened except in experimentation. finished up policy optimization, it provided a 50% reduction in size and 4x speedup, also laid the ground work for further improvements (table sharing, and faster table compression) in the future. pam_apparmor update should be done later in the week. Fixing locking deadlock. The freeing of profiles has a race that can potentially deadlock. This can occur when free_profile is triggered from an rcu callback that is occurring at the same time as a profile replacement/removal.

Blueprints: kernel-lucid-boot-performance

Boot is looking better, plymouth has been pulled back out of initramfs and we are below budget again. We have one outstanding issue with khubd which seems to be hanging about, investigation is ongoing. We have also pulled some of the boot speed improvements back to the ARM branches for lucid, they are under testing now. We look to be at about 1.8s to rootfs right now

Other Release Tasks: Lucid Audio Support

Nothing new here, wiki and bug work needing to be done

Other Release Tasks: Lucid Better Power Mgt

I’ve been playing with CPU wakeups on a stock lucid isntall got it down to 5-6 wake ups after using some laptop-mode-tools tricks, blacklisting modules, etc. 5 wakeups/s now trying to figure out what parts of these hacks can be bundled with lucid I hope to have atleast some scripts for pm-utils.

Other Release Tasks: EC2 Lucid Kernel Status

Updated to latest set of patches, and updated configs to more closely match -server (with exception of physical device drivers, which diverged even more). Need to look at linux-meta-ec2 package as it has been reported by smoser that it isn’t updating to latest version of kernel.

Status: Lucid

We have refactored the debian abstraction to reduce the separation and thereby increase commonality of the rules and scripts. The kernel is currently being pulled up to v2.6.32.8 and should be uploaded today. Overall we are about half way through alpha-3 and we have completed about 58% of the milestoned tasks. Much of what remains undone are investigation items. We are making some progress to returning below the burn-down line: Canonical Kernel Team, Burndown Chart

Security & Bugfix Kernels

Dapper

2.6.15-55.82

(security)

Hardy

2.6.24-27.65

(security)

2.6.24-27.66

(proposed)[just uploaded]

Intrepid

2.6.27-17.45

(security)

Jaunty

2.6.28-18.59

(security)

Karmic

2.6.31-19.56

(security)

2.6.31-20.57

(proposed)[1]

4/18 verifications done

Security release is done. This time it included updates to fsl-imx51, mvl-dove and ec2 packages. The ports-meta will be refreshed as well. confirmation. A new upload to Hardy proposed is waiting for approval and will also be done for netbook-lpia. The Karmic proposed upload includes a few more patches than before and also fixes a regression through 2.6.31.9 that was catched before.

regression-update (no change)

regression-release (no change)

regression-proposed (no change)

Incoming Bugs: Bug day report

There was no bug day, the platform team was sprinting.

Open Discussion or Questions

amitk wants to revisit our decision (dtchen’s really) to turn off HDA power save mode. He is looking for numbers on how many users were affected by the sound glitches. An email will be sent to the kernel-team mailing list starting a discussion and bradf will work with amitk on discussions with upstream.

apw wants to remind everyone that we are frezing the kernel on March the 11th, which means we have to have everything ready and in by March 8th.

smb points out that Karmic SRU for the kernel are about to end as well.