Meeting Minutes

IRC Log of the meeting.

Agenda

2010-23-03 Meeting Agenda

Outstanding actions from last meeting

1. JFo to send out regression bug day announcements on monday
   Carried forward to next week.
2. JFo to do a wiki page on regression bug days
   In progress, carried forward to next week.

Lucid Release Status: Bugs

Blueprints: kernel-lucid-bug-handling

Nothing new to report.

Blueprints: kerne-lucid-kernel-config-review

Nothing new to report.

Blueprints: kernel-lucid-kms

Testing of the beta has been mostly good so far, there are a couple of “blank screen on install” bugs to look at.

Blueprints: kernel-lucid-suspend-resume

Nothing new to report.

Blueprints: kernel-lucid-apparmor-development

Another lkml push going out today, will also issue pull requests for the bug fixes it includes.
Since beta 1 release have picked up another couple bugs to look at with security team
Bug #544819, Bug #544789, Bug #544764 as well as #529288 which I haven’t been able to
reproduce and currently looks as if it is caused by memory corruption.

• apparmor “apparmor does not work with midori” [Undecided,New] https://launchpad.net/bugs/544819
• apparmor “apparmor-logprof not working” [Undecided,New] https://launchpad.net/bugs/544789
• apparmor “unkillable apparmor_parser” [Undecided,New] https://launchpad.net/bugs/544764
• linux “”Kernel Oops” – unable to handle kernel paging request at ffff880323279bf2 RIP is at aa_dfa_match_len+0xd9/0xf0″ [Low,Incomplete] https://launchpad.net/bugs/529288

Blueprints: kernel-lucid-boot-performance

Nothing new to report.

Other Release Tasks: Lucid Audio Support

Still working on the bug survey. I’ve moved to working on modifications to arsenal
scripts to do more of the work. I’ve done a bit of refactoring of Bryce’s process-new-bugs.py
script and sent it to him. I’ll take his feedback and appy the changes to our scripts
as well. I’m trying to make it so we don’t fork the scripts quite so much.

Other Release Tasks: Lucid Better Power Mgt

Sent some patches upstream to pm-utils and am waiting on feedback. Will push out a new set of packages when I hear back.

Other Release Tasks: EC2 Lucid Kernel Status

Testing fix for Bug #527208, which also seems to fix Bug #540378

• linux-ec2 “ec2 instance fails boot, no console output on c1.xlarge” [High,Confirmed] https://launchpad.net/bugs/527208
• linux-ec2 “BUG: soft lockup – CPU#1 stuck for 66s! [swapper:0]” [Medium,New] https://launchpad.net/bugs/540378

Other than those its looking good.

Status: Lucid

Ok, apw uploaded a kernel including 2.6.32.10 and a newer igb driver. Uploaded meta today so it will probably get offered soonish.
Will gather updates till Friday and then do another upload.

Security & Bugfix Kernels

Packages marked with ‘*’ have been uploaded to proposed. Planned acceptance into proposed is tomorrow.

Incoming Bugs: Regressions

Current regression stats (broken down by release):

regression-potential (up 40)

• 128 lucid bugs

regression-update (up 1)

• 12 karmic bugs
• 5 jaunty bugs
• 2 intrepid bugs
• 1 hardy bug

regression-release (down 1)

• 53 karmic bugs
• 22 jaunty bugs
• 11 intrepid bugs
• 4 hardy bugs

regression-proposed (no change)

• 1 karmic bug

Incoming Bugs: Bug day report

Open Discussion or Questions

1. A warm welcome from all to Kamal Mostafa, the latest kernel team member.

Meeting Minutes

IRC Log of the meeting.

Agenda

2010-09-03 Meeting Agenda

Outstanding actions from last meeting

1. None

Lucid Release Status: Bugs

Blueprints: kernel-lucid-bug-handling

Almost done with the analysis of the X debugging pages. JFo will update the team on the current state of the Kernel Team pages and an initial draft of recommended changes to the structure and layout via the e-mail list. Will have the arsenal scripts running (not in dry run mode) by the end of this week.

• I’m almost ready to present my findings on the X wiki debug pages and how I’d like to restructure the Kernel Team pages. I hope to send something on this to the list this week

• I am reworking the way the arsenal scripts gather and process bugs so that I can extend the ‘reach’ of the script deeper into the backlog. I’ll probably do a rather intense round of bug processing during the lull after release freeze.

• I sent out an e-mail to the c-k-t list (meant to send to the k-t list) regarding a wiki page describing the rationale for automated bug processing. Please provide some feedback. I’d like to get this URL integrated into the arsenal scripts soon.

Blueprints: kerne-lucid-kernel-config-review

Discussion thread started on the remaining sub-systems and PATA/SATA driver status. Should have patches for immediatly after Beta-1.

Blueprints: kernel-lucid-kms

We are seeing a lot of issues with i945 and older graphics cards, which includes all the atom netbooks. This is looking to be new occurance of the i915.powersave problems, we will disable powersaving for these ‘older’ cards by default.

Blueprints: kernel-lucid-suspend-resume

Looks like we are getting some useful information as a result of the patch to measure suspend resume times. I am currently looking at the suspend/resume bugs filed recently and trying to get a sense of any common elements we can find.

Blueprints: kernel-lucid-apparmor-development

The latest upstream push is ready go out.

Blueprints: kernel-lucid-boot-performance

The ureadahead patches are with Foundations for testing. Again we should have results in time for the first upload after Beta-1.

Other Release Tasks: Lucid Audio Support

Nothing significantly new this week.

I’m several days into my als-driver bug survey and have looked at almost 200 bugs. I’m basicly going through them one by one and adding tags onto them. If they have not had any action for more than a couple months I’m requesting a test of a dev image and the mainline kernel. I’m pretty amazed at the number of bugs that have not seen any attention since their initial submission.

The biggest buckets are “no sound at all” and “internal mic not working”. There are a few that look like upgrade isses, people running out and buying the latest HW expecting it to “just work”, etc.

I also see that there are a bunch of bugs that are “past expiration”. I asked around about this and was told that the bot that ran around marking these “invalid” had to be turned off because it wasn’t smart enought and was invalidating bugs it shouldn’t. I was told that a new status is being created “Expired” specifically for these bugs and that the bot would be smartened up. This work is supposed to happen this month.

Other Release Tasks: Lucid Better Power Mgt

The release team has pretty much veto’d putting the pmutils functionality in as it didn’t hit b-1. The rest has been postponed due to workload.

Other Release Tasks: EC2 Lucid Kernel Status

Working on Launchpad bug 527208 in linux-ec2 “ec2 instance fails boot, no console output on c1.xlarge” [High,Confirmed] https://launchpad.net/bugs/527208

Have confirmed that it isn’t exhibiting under similar circumstances in rackspace cloud. I haven’t made anymore progress on testing pv-ops.

Status: Lucid

Lucid remains at stable v2.6.32.9, though v2.6.32.10 is now available and will be applied once Beta-1 is over. We have commited patches to expose the DRM backports version such that when v2.6.33.1 DRM patches we can tell that that has occured in bug reports. We have also changed the default settings for the CDROM trays to allow direct removal of disks, userspace will handle this shortly.

All of the main kernels (linux, linux-fsl-imx51, linux-mvl-dove, linux-qcm-msm, and linux-ec2) remain unchanged from last week. linux-ti-omap was just accepted into the archive. Anything which requires a kernel change will have to wait until after beta-1 and will have to pass the abbreviated SRU process (2 acks required).

Security & Bugfix Kernels

Security update is expected somewhen today (after some final tests)

Incoming Bugs: Regressions

Current regression stats (broken down by release):

regression-potential (up 30)

• 88 lucid bugs

regression-update (no change)

• 11 karmic bugs
• 5 jaunty bugs
• 2 intrepid bugs
• 1 hardy bug

regression-release (no change)

• 54 karmic bugs
• 22 jaunty bugs
• 11 intrepid bugs
• 4 hardy bugs

regression-proposed (no change)

• 1 karmic bug

Incoming Bugs: Bug day report

Today is another Kernel Team ‘regression-’ bug day. Thanks for working on these last week. I’ll be looking at the schedule for the rest of this release and proposing more bug days to work out regressions to Pete for inclusion in the schedule. I anticipate that, as we move closer to the release freeze, we will probably do more than one bug day a week, but I want to see what the timeframe looks like before I propose that.

I didn’t get to schedule a community bug day today as I had planned. I will get things ready to hold another bug day against bugs with patches attached for next week.

Open Discussion or Questions

1. Nothing new this week.

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.