Meeting Minutes

IRC Log of the meeting.


2010-06-04 Meeting Agenda

Outstanding actions from last meeting

None this week.

Lucid Release Status: Bugs

Beta 2 Milestoned Bugs Release Targeted Bugs
linux 6 29
linux-fsl-imx51 0 0
linux-ec2 0 0
linux-mvl-dove 0 0

Blueprints: kernel-lucid-bug-handling

All work items done or postponed, only remaining tasks are for release.

Blueprints: kerne-lucid-kernel-config-review

Over-active beep in VT is under investigation. We expect to write up the configuration report in time for Beta-2.

Blueprints: kernel-lucid-kms

We have ongoing issues with Lid detection, currently we have LVDS lid detection reverted and we are looking at the fallout from that change.

Blueprints: kernel-lucid-suspend-resume

apport — allow us to detect frequency of failure:POSTPONED all other work items done

Blueprints: kernel-lucid-apparmor-development

Still looking for the root cause of Bug #552225, Bug #544764, Bug #549428, Bug #458299

  • Launchpad bug 552225 in apparmor “system bogs down when apparmor is running” [Undecided,New]
  • Launchpad bug 544764 in apparmor “unkillable apparmor_parser” [Undecided,New]
  • Launchpad bug 549428 in apparmor “Triggers permanent high i/o load after upgrade” [Undecided,Incomplete]
  • Launchpad bug 458299 in linux “apparmor_parser: page allocation failure. order:5″ [High,Fix released]

Not positive, but very likely one root cause. It is always replacement related, under high memory pressure/fragmented memory where fast path allocation fails and we fall back to vmalloc for the dfa. It seems to be very much related to the use of swap as I have reports that turning off swap makes it go away and in the end may be a bug in the mm and not apparmor. Also verified that the policy compiler is building isomorphs on multi-policy load and not suffering from a bug, and looked at ways to fix this for M so that we can use multi-profile load and have automated policy verification.

We haven’t been using multi-policy load because we have known that it is generating alternate dfas, and haven’t been able to verify them. I found a few more problems with what I was trying to kick out last week so it got delayed into this week, I have been working through, the checks to send out this morning I expect a few more audit changes will be required yet, and the path generation is some what dependent upon the __d_path patch discussion that I am also rekicking out patches for

Other Release Tasks: Lucid Audio Support

More arsenal work. Wrapping up the survey this week.

Other Release Tasks: Lucid Better Power Mgt

Nothing new this week.

Other Release Tasks: EC2 Lucid Kernel Status

We have Bug #532553, which is just a config oversight as far I can tell

  • Launchpad bug 532553 in linux-ec2 “linux-image-2.6.32-302-ec2 is missing iptables module xt_recent” [Low,Confirmed]

The only question being whether we want to turn it on this late. I (apw) would think anything netfilter related is handy to ahve in that environment, and we have a window to respin for release for somethign which only adds a module which is very low risk. Okay, I’ll send a patch out this morning

Status: Lucid

Beta-2 kernels are in an built. We are not expecting to change the kernel before beta-2. We are expecting some change still before release. Otherwise the worst issues are graphics related to my mind, and mostly getting resolved. Doubt they will all get resolved before release however. We are expecting to be getting a stable update too.

Security & Bugfix Kernels

Hardy 2.6.24-27.68 (security) *
  2.6.24-27.69 (proposed) [ 6] 1/ 3 verifications done (+1)
Intrepid 2.6.27-17.46 (security)
Jaunty 2.6.28-18.60 (security)
Karmic 2.6.31-19.58 (security) *
&lbsp; 2.6.31-19.59 (proposed) [ 6] 2/19 verifications done (+2)
LBM 2.6.31-20.22 (updates) *
&lbsp; 2.6.31-20.23 (proposed) [ 6] 0/ 2 verifications done
mvl-dove 2.6.31-211.26 (security) *
&lbsp; 2.6.31-213.27 (proposed) [ 6]
fsl-imx51 2.6.31-108.25 (security) *
&lbsp; 2.6.31-110.26 (proposed) [ 6] 0/ 1 verifications done
1/ 1 failed! #507416
ec2 2.6.31-304.13 (security) *
&lbsp; 2.6.31-110.26 (proposed) [ 6]

Nothing new this week.

Incoming Bugs: Regressions

Current regression stats (broken down by release):

regression-potential (up 130)

  • 223 lucid bugs

regression-update (down 1)

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

regression-release (down 1)

  • 52 karmic bugs
  • 21 jaunty bugs
  • 11 intrepid bugs
  • 4 hardy bugs

regression-proposed (no change)

  • 1 karmic bug

Incoming Bugs: Bug day report

The next Kernel Team ‘regression-’ bug day is Wednesday, April 7. Thanks for working on these last week.

Open Discussion or Questions

Just FYI — I (kamalm) am working on the “volume keys never release” issue — seems to be a common problem for various laptop models (bug 550979, bug 420473, bug 374884).
The problem can be fixed in ‘udev’ by adding bits to /lib/udev/… scripts — I plan to produce a patched ‘udev’ package for those bug submitters to test.

  • Launchpad bug 550979 in linux “Volume increase & decrease by function buttons never release on Dell Studio 1558″ [Medium,Confirmed]
  • Launchpad bug 420473 in linux “Coolbox QBook 270-02: volume keys produce more than one key event” [Medium,Incomplete]
  • Launchpad bug 374884 in linux “Keyboard quirk is required for Mitac 8050QDA Fn Volume keys to function.” [Undecided,New]