Archive for June, 2010

Brad Figg

Kernel Team Meeting Minutes

June 29th, 2010 by Brad Figg
Categories: Uncategorized
No Comments

Meeting Minutes

IRC Log of the meeting.
Blog of the meeting minutes.

Agenda

2010-06-29 Meeting Agenda

Open action: manjo to send a firewire patch with test info

manjo    I believe pgraner tested this with kino and dvgrab and reported it to work.
manjo    I had submitted a bzr patch making the switch to ubuntu kernel mailing list,
manjo    waiting for tgardner or Keybuk to pick this up.
tgardner    hmm, I think we’re still awaiting some test results
Keybuk    hmm? I don’t do kernel stuff
manjo    tgardner, test results from ?
tgardner    Keybuk, its just a matter of swizzling some blacklists
tgardner    manjo, results from pgraner et al
Keybuk    ah, the old kansas city shuffle
manjo    tgardner, ok
tgardner    how about Luke’s audio supprt changes?
tgardner    wasn’t there an app that needed updating?
manjo    he was going to upgrade some of the audio packages
manjo    and he volunteered to do it
tgardner    manjo, has he done so?
manjo    tgardner, I will check with him again today
tgardner    manjo, once we have a synopsis of resul;ts, then I’ll make the blacklist changes
manjo    tgardner, ack

Open action: JFo to put out a CFT on new firewire stack

No status, JFo on vacation

Release Metrics

No status, JFo on vacation

Blueprint: kernel-maverick-apparmor

Synced latest upstreaming version of AA into Maverick. Marc Deslauriers already hit Bug #599450 which testing missed. I am looking at it and it should be a quick fix.

Blueprint: kernel-maverick-firewire-stack

Covered in the open action item.

Blueprint: kernel-maverick-misc

No status, apw on vacation

Blueprint: kernel-maverick-new-kernel-on-lts

The Lucid LTS backport kernel from Maverick continues to track the Maverick kernel.

Blueprint: kernel-maverick-pv-ops-ec2-kernel

no change. I just started looking at this again and will have a new test kernel today

Blueprint: kernel-maverick-tracing-support

Nothing new, development work is done, should be removed from meeting schedule.

Blueprint: kernel-maverick-ubuntu-delta-review

All Alpha2 work items are complete. Nothing new to report.

Blueprint: kernel-maverick-union-mounts

No status, apw on vacation

Blueprint: kernel-maverick-bug-handling

No status, JFo on vacation

Blueprint: kernel-maverick-upstart

No status, apw on vacation

Blueprint: kernel-maverick-bios-test-automation 

Changes to Firmware Test Suite this week:
  7 Additional tests:
      maxfreq: check CPU freq scaling max frequency against CPU max freq.
      cstates: measure C states across CPUs and check activity when loaded
      WMI: inspect DSDT for WMIs and dump out WMI methods and events (for hotkeys).
      lid: interactive lid event detection test.
  Other improvements + fixes:
      klog scanning: use pcre rather than glibc regex.
      Improved progress feedback (-p, --show-progress).
      mtrr: check for MTRR config of VGA regions by BIOS.
      mttr: fix prefetchable region detection bug
      Add batch or interactive modes of testing.
      Include 800+ example klog errors to test against.

Status: Maverick

We uploaded a last minute linux-2.6.35-6.8 Alpha2 kernel on Sunday to resolve bug 597904 which was a blocker for building Alpha2 arm images. We will essentially be uploading a 0-day Alpha2 kernel, linux-2.6.35-6.9, to resolve bug 588861. I’ve been given the green light to upload it late Wed. We currently have it uploaded to our kernel-ppa as an interim solution.

All of our team’s Alpha2 work items are complete, so good job everyone. Alpha 3 is Thurs Aug 5th which is a little over a month away. Please review the list of work items for Alpha 3:

ARM Status 

- Marvel (mvl-dove):
    Nothing new this week.
- Freescale (fsl-imx51):
    Nothing new this week.
- Texas Instruments (ti-omap):
    In Maverick, cooloney prepared a branch which includes some ASoC audio and
    other fixes for git pull.
- Bugs:
    cooloney went through the omap bug list, located here:

https://bugs.edge.launchpad.net/ubuntu/+source/linux-ti-omap.

    Closed a bug to won't fix. Nothing new on other bugs.

Security & bugfix kernels – Karmic/Jaunty/Intrepid/Hardy/Others 

Dapper:      2.6.15-55.84  (security)
Hardy:       2.6.24-28.70  (security)
             2.6.24-28.71  (proposed)[11]  0 / 1 verifications done
Jaunty:      2.6.28-19.61  (security)
Karmic:      2.6.31-22.60  (security)
             2.6.31-22.61  (waiting for approval)
 - mvl-dove  2.6.31-214.28 (security)
             2.6.31-214.29 (waiting for approval)
 - fsl-imx51 2.6.31-112.28 (security)
             2.6.31-112.29 (waiting for approval)
 - ec2       2.6.31-307.15 (security)
             2.6.31-307.16 (waiting for approval)
Lucid:       2.6.32-22.36  (security)
             2.6.32-23.37  (proposed)[18] 14/39 verifications done
 - LBM       2.6.32-23.37  (proposed)[15]  3/ 3 verifications done
 - mvl-dove  2.6.32-205.18 (security)
             2.6.32-206.19 (proposed)[11] 13/41 verifications done (+ 1)
 - fsl-imx51 2.6.31-608.14 (security)
             2.6.31-608.15 (proposed)[11]  4/ 8 verifications done (+ 2)
 - ti-omap   2.6.33-501.7  (security)
             2.6.33-502.8  (proposed)[11]  0/ 4 verifications done
 - qcm-msm   2.6.31-802.4  (security)
             2.6.31-802.5  (proposed)[11]  1/ 5 verifications done
 - ec2       2.6.32-306.11 (security)
             2.6.32-307.12 (proposed)[11] 12/38 verifications done

It seems Martin was relatively happy with the current state so Lucid might move to updates at some point in the near future

Incoming Bugs and Regression Stats

No status, JFo on vacation

Incoming Bugs: Bug day report

No status, JFo on vacation

Open Discussion or Questions

abogani2    I would want only inform you that I placed -lowlatency and -realtime kernel on Zinc and in my PPA (https://launchpad.net/~abogani/+archive/ppa) for review. Ever if anyone have time and chance to do it. ;-)
 
 
kamal    regarding bug 594837 …
ubottu    Launchpad bug 594837 in linux (Ubuntu) “Lucid SRU: Intel Core i3/i5/i7 hang on resume from suspend (SCI_EN)” [High,Confirmed] https://launchpad.net/bugs/594837
kamal    still no response to the patch I submitted to stable@kernel.org 14 days ago:
kamal    [PATCH] ACPI: Unconditionally set SCI_EN on resume
kamal    should we continue to wait, or move forward with a Lucid SRU, or something else?
smb    kamal, Greg seems to have re-surfaced recently
smb    kamal, But you might re-ask
maks_    stable was on vacation.
kamal    maybe I’ll give it another week then, thanks.
 
 
lag    I’d like to request that the ARM Status item is brought forward i.e. placed nearer the top of the agenda. Otherwise; if the meeting goes on longer than 45-60mins I will be unable to present the item as I have to leave imminently for ‘other things’. :)
bjf    lag, i have no problem with that
bjf    lag, i’ll make it so
lag    I don’t want to tread on anyone’s toes
bjf    lag, it was an arbitrary decision on my part, i can change it
lag    Great, thanks
Brad Figg

Kernel Team Meeting Minutes

June 22nd, 2010 by Brad Figg
Categories: Uncategorized
No Comments

Meeting Minutes

IRC Log of the meeting.
Blog of the meeting minutes.

Agenda

2010-06-22 Meeting Agenda

Open action item: manjo to send a patch with test info

Nothing new this week.

Open action item: jfo to put out a CFT on new firewire stack

This is holding for manjo’s test kernel which will likely land in Alpha3. This is also tracked in the frewire blueprint.

Release Metrics

Bugs

 
  Alpha 2 Milestoned Bugs (17 (down 12)) Release Targeted Bugs (86 across all packages (up 3))
linux 1 1

Milestoned Features

* 13 blueprints (Including HWE blueprints)

Bugs with Patches Attached:111 (down 6 from last week)

Blueprint: kernel-maverick-apparmor

No progress from last week. Doing the testing now

Blueprint: kernel-maverick-firewire-stack

Nothing new this week.

Blueprint: kernel-maverick-misc

The debian commonisation is progressing well, Lucid and Maverick are both applied. Karmic is still pending approval. The TI-OMAP4 preliminary kernel has now been created and pushed to the repository.

Blueprint: kernel-maverick-new-kernel-on-lts

Uploaded Ubuntu-lts-2.6.35-5.6 this morning to the kernel-ppa at http://ppa.launchpad.net/kernel-ppa/ppa/ubuntu. Submitted upstream patch to deprecate a netfilter config option CONFIG_NF_CT_ACCT which will have an impact on Lucid userspace when the 11.04 kernel is backported.

Blueprint: kernel-maverick-pv-ops-ec2-kernel

Ported over the latest .34 Xen patchset, it currently has some issues, so we will stay with Lucid EC2 kernel until they are resolved.

Blueprint: kernel-maverick-tracing-support

trace-cmd and kernelshark have been uploaded as of 2 hrs ago, feel free to give it a spin! Our version of perf probe now also supports the new -s option for specifying the source directory. This blueprint is pretty much fulfilled in terms of development. JFo has a task for looking at arsenal scripting responses for ftraceable bugs, but that’s all. A todo task has been added to the [[http://wiki.ubuntu.com/Kernel/Arsenal|kernel team's arsenal script todo list]].

Blueprint: kernel-maverick-ubuntu-delta-review

2 of the usb sauce patches I pushed upstream to remove duplicate id’s are now in gregkh-2.6 tree. Per feedback on linux-wireless ml, I fixed up and resent the p54usb patch to comment out a duplicate id. I also resent the ipw2200 enable led by default patch with TJ’s official SOB. These last two are still pending acceptance.

Blueprint: kernel-maverick-union-mounts

The union mounts patches have been revised and are now at 2.6.34, however they are looking to be still undergoing heavy churn and review. I do not see them being ready for our use within the timescales required. We should probabally consider assuming it will not make it.

Blueprint: kernel-maverick-bug-handling

  • apw and I will be reworking the Triage section of the wiki. I’ll be adding a page for the BugDays and moving over some relevant information from the old ones, but generally leaving legacy information there.
  • The forum moderators are excited to be helping us address kernel related forum topics as well as bugs filed due to comments in the forums. More to come on this
  • I’ve sent out an initial inquiry out to gauge the interest in the proposed kernel triage summit. So far the response has been immensely positive. the X community is involved and it seems that there is a great deal of interest in the classes on specific subsystems. I also sent out a call for experts to address some of the subsystems that have a separate component outside the kernel such as X and audio specifically. I’ll send out some more specific e-mails as time goes on to gather subject experts for the classes.

Blueprint: kernel-maverick-upstart

The initargs patches have now been tested, updated and pushed to the Maverick kernels. The ureadahead patches remain untested.

Blueprint: kernel-maverick-bios-test-automation 

  Changes to Firmware Test Suite this week:
      Add in heurstic driven advice when detecting errors (lots of textual help)
      Lots of code tidy up (fix memory leaks, func return values), tested with valgrind
      Add in generic CPU identification code
      Automate debian packaging from git repo
      Put in PPA http://ppa.launchpad.net/firmware-testing-team/ppa-firmware-test-suite
      Scan ~2870 kernel logs from LP, extract errors, tune klog scanner to detect these errors.
      Regex pattern matching on log scanning (slower, more flexible though)

Status: Maverick

We just uploaded the linux-2.6.35-5.6 kernel yesterday. This primarily contains kernel config changes, so please test. Alpha 2 is Thurs July 1 (ie ~1week from today). You should be finalizing any work items you have or pushing them out to Alpha3 if they’re not Alpha2 release critical. Note that we’re currently above the trend line in our Alpha 2 burn down chart so get those items closed or moved asap!

Also, if you have any patches which you want to land in the Alpha2 kernel, they need to be sent to the kernel-team ml and have garnered the appropriate Ack’s before this Fri, June 25. I plan to upload our final Alpha2 kernel Thursday afternoon/Friday morning PST (UTC-7).

ARM Status

  • Marvel (mvl-dove) :

    • mvl-dove branch in lucid has been updated to sync with the latest Marvell
      Dove LSP 5.2.1 (mostly fixes), as well as one additional fix to the resume
      failure from hibernation.
  • Freescale (fsl-imx51):

    • Nothing new this week; however, cooloney indicates that smb may have completed
      some work to upload the kernel to -proposed.
  • Texas Instruments (ti-omap):

    • A new topic branch named ti-omap4 was merged into Maverick. It is based on TI
      2.6.34 omap4 kernel tree. rtg also helped to pull the branch and sync the Debian
      packaging stuff with our Maverick master branch. TI said they will provide a
      2.6.35-rc based omap4 tree to our Maverick in the middle of Aug.

Security & bugfix kernels – Karmic/Jaunty/Intrepid/Hardy/Others 

Hardy:       2.6.24-28.70  (security)
             2.6.24-28.71  (proposed)[ 4]  0 / 1 verifications done
Jaunty:      2.6.28-19.61  (security)
Karmic:      2.6.31-22.60  (security)
             2.6.31-22.61  (waiting for approval)
 - mvl-dove  2.6.31-214.28 (security)
             2.6.31-214.29 (waiting for approval)
 - fsl-imx51 2.6.31-112.28 (security)
             2.6.31-112.29 (waiting for approval)
 - ec2       2.6.31-307.15 (security)
             2.6.31-307.16 (waiting for approval)
Lucid:       2.6.32-22.36  (security)
             2.6.32-23.37  (proposed)[11] 14/39 verifications done (+ 6)
 - LBM       2.6.32-23.37  (proposed)[ 8]  3/ 3 verifications done (+ 2)
 - mvl-dove  2.6.32-205.18 (security)
             2.6.32-206.19 (proposed)[ 4] 12/41 verifications done (+12)
 - fsl-imx51 2.6.31-608.14 (security)
             2.6.31-608.15 (proposed)[ 4]  2/ 4 verifications done (+ 2)
 - ti-omap   2.6.33-501.7  (security)
             2.6.33-502.8  (proposed)[ 4]  0/ 4 verifications done
 - qcm-msm   2.6.31-802.4  (security)
             2.6.31-802.5  (proposed)[ 4]  1/ 5 verifications done (+ 1)
 - ec2       2.6.32-306.11 (security)
             2.6.32-307.12 (proposed)[ 4] 12/38 verifications done (+12)

For the various ARM topic branches, people with testing HW need to make sure
that beside of generic boot tests, they verify their specific bugs:

Incoming Bugs and Regression Stats

Incoming Bugs:

  Version Count
  Maverick 28 (+5)
  Lucid 980 (+30)

Current regression stats:

  Version Potential Update Release Proposed
  maverick 12 (+4)      
  lucid 223 (?) 34 (+4) 142 (+6) 1
  karmic   6 46 (-2) 1
  jaunty   4 19  
  hardy   1 2  

Incoming Bugs: Bug day report

Today’s bug day will be focusing on working Confirmed bugs and getting them to either Incomplete, by way of testing or information requests, or Triaged based on the completeness of the bug. My goal is to work through all of the Confirmed bugs to get them in the correct state. The Team Bug Days will continue to be the two half days on Friday and Monday. Please provide me feedback on these as you have it. Next week’s bug day will be two-fold. On the one hand, we will change the remaining lucid regression-potential bugs to regression release. On the other hand, we will be reviewing the incorrectly labeled new bugs that need to be some other status based on either response by the bug reporter or the inclusion of requested logging.

Open Discussion or Questions:

Just a reminder that we are all meant to be helping with the wiki gardening effort … this needs to be basically complete by the end of the platform sprint. There is a long todo of small items people can help out with. For the date & time challenged that is 23 July. The wiki todo page.

Brad Figg

Kernel Team Meeting Minutes

June 15th, 2010 by Brad Figg
Categories: Uncategorized
No Comments

Meeting Minutes

IRC Log of the meeting.

Agenda

2010-06-15 Meeting Agenda

Release Metrics

Bugs

 
  Alpha 2 Milestoned Bugs (29 (up 24)) Release Targeted Bugs (83 across all packages (up 33))
linux 10 17
 
 

Milestoned Features

13 blueprints (Includes HWE Blueprints)

Bugs with Patches Attached:117 (down 5 from last week)

Launchpad report of bugs with patches.
Breakdown of bugs with patches

 
 

Blueprint: kernel-maverick-apparmor

Slow progress – updated compatibility code, need to do testing and send out pull request when done

Blueprint: kernel-maverick-firewire-stack

Nothing to report

Blueprint: kernel-maverick-misc

The debian commonisation is progressing well, both Karmic and Lucid branch sets have been converted over. There is some resistance to applying these changes to Karmic currently as they are very hard to review and seen as perhaps outside the SRU process; discussions are ongoing but we may have to abandon doing this for Karmic. We have also mothballed a no longer used branch in Karmic, the netbook branch.

”’Question:”’ “Does this lift a hold on lucid patches against mvl-dove?”

”’Answer:”’ Yes, it appears to and we think the Marvell, lucid patches are in the tree and awaiting upload.”

Blueprint: kernel-maverick-new-kernel-on-lts

The LTS backport kernel and meta packages at http://ppa.launchpad.net/kernel-ppa/ppa/ubuntu are up to 2.6.35-3.4 (tracking the latest maverick kernel release). All appears well. In fact, its much better then the previous 2.6.35-rc2 based release which had some memory corrupter bugs.

Blueprint: kernel-maverick-pv-ops-ec2-kernel

pv-on-HVM drivers don’t help us out :( Karmic pv-ops kernel on EC2 is more flaky than it was in the Karmic cycle (only successfully booted in 1 of 4 availability zones). Lucid pv-ops is boot in 2 of 4 availability zones on last test. Maverick wasn’t booting at all under 2.6.35.2, have tried it with the latest config changes made pulled forward from Lucid and haven’t tried .3 yet. Current plan is revert to full Xen topic branch, and get other work items done and return to pv-ops kernel in a few weeks.

”’Question:”’ “Wasn’t there a middle option? The drivers only?”

”’Answer:”’ “The drivers are the pv-ops-HVM.”

Blueprint: kernel-maverick-tracing-support

Patch sent upstream for perf probe under review. I’ve packaged trace-cmd and kernelshark, sent three patches upstream for them (2 trace-cmd, 1 kernel). Will work on getting them into Maverick.

Blueprint: kernel-maverick-ubuntu-delta-review

I pushed 3 of our sauce patches upstream which just removed some duplicate device id’s. I’ve also dropped 2 more sauce patches which added MODULE_ALIAS for the Dell WMI module and the other which sent events on data interface as well as master interface for the hostap driver.

Blueprint: kernel-maverick-union-mounts

Waiting on testing from Foundations from updated kernels. Need to get the tools updated for this and uploaded to the same PPA, hoping to have those tommorrow.

tgardner    ogasawara, you got some pushback on one of those removals. what came of that?
ogasawara    tgardner: hrm, I didn’t see any reply.
ogasawara    tgardner: I’ll have to look into it
tgardner    ogasawara, the one with duplicate IDs
ogasawara    tgardner: I’m not subscribed to the upstream list so I wonder if I wasn’t CC’d on the reply?
tgardner    ogasawara, likely

Blueprint: kernel-maverick-bug-handling

Conversation with the Forums people has begun, they are talking internally to gather some thoughts on our proposal concerning the discussion between us to improve the quality of the information on the forums. They will be gettting back with me late this week or next week and we will go from there.
 
I have tested the SHA1 gathering script several times now. It will likely not be as useful as i thought due to the fact that the janitor puts a comment containing the SHA1 of the fix that solves an issue in bugs that potentially have multiple tasks, thus giving us false positives. I am working to define the problem before I see if we can modify the script to react to those comments appropriately.
 
I sent out the initial e-mail to get an idea of the interest level for a Kernel Triager Summit. Based on the response, I will begin the further planning items needed to make this a reality.

Blueprint: kernel-maverick-upstart

Waiting on testing from Foundation from updates kernels. Expecting preliminary feedback on Wednesday.

Blueprint: kernel-maverick-bios-test-automation 

Added the following functionality to the firmware test suite:
  Battery Test: Exercise CPU to drain quicker
  Kernel Version checking
  Include Blank Test Template
  Re-organise klog scanning, added more intelligence
  Logging: Add line numbering, test failure levels, summary of failures, improved automatic text formatting
  Add --no-s3 --no-s4 options to ignore suspend/hibernate tests
  Check for redundant _OSI(Linux)
  HPET sanity check vendor ID
  Syntax check SSDT tables
  Virtualisation extention checks
  Add in MCFG test
  General bug fixing and code tidying

Status: Maverick

We’ve rebased to 2.6.35-rc3 which should be available as of linux-2.6.35-3.4. Please test. Alpha 2 is Thurs July 1 (ie ~2weeks from today) so make sure you’re on track with any work items that need doing as we’re currently above the trend line in our Alpha 2 burn down chart: Also keep in mind that if you have any patches which you want to land in the Alpha2 kernel, they need to be sent to the kernel-team ml and have garnered the appropriate Ack’s *before* Fri Jun 25. I’ll send an email reminder this Friday.

Security & bugfix kernels – Karmic/Jaunty/Intrepid/Hardy/Others 

Dapper:      2.6.15-55.84  (security)
Hardy:       2.6.24-28.70  (security)
             2.6.24-28.71  (waiting for approval)
Jaunty:      2.6.28-19.61  (security)
Karmic:      2.6.31-22.60  (security)
             2.6.31-22.61  (waiting for approval)
 - mvl-dove  2.6.31-214.28 (security)
             2.6.31-214.29 (waiting for approval)
 - fsl-imx51 2.6.31-112.28 (security)
             2.6.31-112.29 (waiting for approval)
 - ec2       2.6.31-307.15 (security)
             2.6.31-307.16 (waiting for approval)
Lucid:       2.6.32-22.36  (security)
             2.6.32-23.37  (proposed)[4]  8/39 verifications done (+ 8)
 - LBM       2.6.32-23.37  (proposed)[1]  1/ 3 verifications done (+ 1)
 - mvl-dove  2.6.32-205.18 (security)
             2.6.32-206.19 (waiting for approval)
 - fsl-imx51 2.6.31-608.14 (security)
             2.6.31-608.15 (waiting for approval)
 - ti-omap   2.6.33-501.7  (security)
             2.6.33-502.8  (waiting for approval)
 - qcm-msm   2.6.31-802.4  (security)
             2.6.31-802.5  (waiting for approval)
 - ec2       2.6.32-306.11 (security)
             2.6.32-307.12 (waiting for approval)

As we found out today there is resistance on the current changes in Karmic which only affect the build infrastructure. This needs to be resolved before the uploads will be accepted into proposed.

Incoming Bugs and Regression Stats

Incoming Bugs:

  Version Count
  Maverick 23 (+8)
  Lucid 950 (+4)

Current regression stats:

  Version Potential Update Release Proposed
  maverick 8 (+1)      
  lucid 223 (-11;) 30 (+5) 136 (+8) 1
  karmic   6 (-3) 48 (-2) 1
  jaunty   4 (-1) 19 (-1)  
  hardy   1 2 (-1)  

Incoming Bugs: Bug day report

I neglected to announce the Bug Day scheduled for today last week due to travel for the SELF conference. That Bug Day will be held next week. The next bug day will be next Tuesday. We will be focusing on working Confirmed bugs and getting them to either Incomplete, by way of testing or information requests, or Triaged based on the completeness of the bug. My goal is to work through all of the Confirmed bugs to get them in the correct state and work but the best method for them based on conversation with Andy last week. I am happy with the progress of the Team bug day so far. I’d like to hold this again this week. I am open to continuing the two half days on Friday and Monday again if there is no objection.

”’Question:”’ “Are you all still finding the half day Kernel team days on friday and monday useful?”

”’Answer:”’ “Though not everyone has been able to participate as much as they’d like, they do like the split and we’ll continue to see if the idea gets traction.”

Open Discussion or Questions:

ogasawara    https://blueprints.launchpad.net/ubuntu/+spec/desktop-maverick-xorg-gpu-freeze-reports
ogasawara    There are 3 Alpha2 work items assigned to the canonical-kernel-team in
ogasawara    that blueprint.
ogasawara    sconklin, could I persuade you to own those 3 work items? It looked like
ogasawara    you and apw attended this UDS session but apw seems to have enough
ogasawara    Alpha2 work items on his plate.
sconklin    looking
ogasawara    while you’re looking, the other item was https://blueprints.edge.launchpad.net/ubuntu/+spec/foundations-m-uefi-support
ogasawara    This also has an Alpha2 work item assigned to canonical-kernel-team,
ogasawara    “Investigate situation with Intel graphics drivers on EFI”.
ogasawara    cking or tgardner, did either of you attend this UDS session? Can I get
ogasawara    one of you to own this work item?
sconklin    ogasawara: sure, I can take those
cking    ogasawara, nope, it clashed with something else I had to attend
ogasawara    sconklin: thanks, much appreciated.
tgardner    ogasawara, I volunteer cking as he’s already involved with EFI
sconklin    I’ll edit the blueprint now
ogasawara    cking: thanks
 
 
phunge0    https://bugs.launchpad.net/ubuntu/+source/linux/+bug/585092
ubottu    Launchpad bug 585092 in linux (Ubuntu) “tmpfs umount slowdown” [Medium,Triaged]
phunge0    Could I get some feedback on prospects for this bug in lucid? Upstream devs think they have a real fix to the problem (2nd try), it’s been posted to lkml but won’t be merged until 2.6.35-rc4 at earliest (when Linus gets back from vacation). I’m wondering if backporting it would be considered feasible. If not I’m hoping the workaround could be revisited, it has serious performance downsides.
phunge0    Please let me know if there’s someone specific I should be talking to.
tgardner    phunge0, is this so critical that you can’t wait 2 weeks for it to show up in due course?
smb    I believe last time they had a fix they reverted it due to hangs in xfs
bjf    phunge0, it looks like we are waiting to see what upstream wants to do about it
smb    But it was one of the things I wanted to investigate
phunge0    ok
apw    phunge0, do we have a poninter to the outstanding conversation on that
phunge0    it’s not critical, but my firm was hoping to migrate to lucid with the SRU
phunge0    http://lkml.org/lkml/2010/6/10/259
apw    to the ‘new’ fix? make it easier for us to track when it hits maverick so we can test
phunge0    and this blocks us
apw    phunge0, thanks
apw    phunge0, us ?
phunge0    this is the patchset http://lkml.org/lkml/2010/6/10/175
phunge0    my firm, sorry
tgardner    phunge0, it remains to be seen if Jens fix is gonna do the trick
apw    phunge0, thats like 13 patches!
tgardner    apw, maybe we can get it via stable :)
apw    tgardner, fingers crossed :)
phunge0    yeah, this is linus indicating that it might be acceptable for 2.6.35
smb    We might but that will certainly take time
apw    cirtainly we should help test it in 35
phunge0    http://lkml.org/lkml/2010/6/10/285
phunge0    but he pushed back
 
 
manjo    can we get some feed back on the firewire stack switch? I think its a matter of blacklisting old modules and whitelisting new ones
manjo    blacklist ohci1394 sbp2 eth1394 dv1394 raw1394 video1394 and whitelist firewire-ohci firewire-sbp2 firewire-core firewire-net in /etc/modprobe.d/blacklist-firewire.conf. As far as I can see this is the only real change that needs to happen to make this switch.
manjo    I emailed ubuntu-devel and ubuntu-kernel
manjo    and I don’t have any response yet
manjo    ie switch from old firewire stack to new stack
apw    so i’d recommend you ask on #ubuntu-devel about this as well
tgardner    manjo, did your email include a patch?
apw    there are some old hands there who can probabally help guide us as to the next step
manjo    tgardner, no, I thought we talked about this a while back and
manjo    foundations need to make that change ?
tgardner    manjo, we can do it as well. we have before
manjo    I am happy to send a patch
manjo    tgardner, to ubuntu-kernel ?
apw    manjo, do we have the alternate userspace stack available ?
tgardner    I want some test results too.
apw    (i thought there was one if you switched?)
manjo    yep we have both moduels built as of now
tgardner    manjo, yep, ubuntu-kernel list
apw    manjo, i meant the userspace integration, does it work with both ?
apw    s/both/either
tgardner    apw, thats what I meant by test results
manjo    apw, there was a bug for which the switch was tested
manjo    but I can send a patch with test info
tgardner    manjo, just put the results in the bug
apw    sounds good then …
JFo    I think we need a gneral CFT on the new stack then
manjo    tgardner, will do
tgardner    JFo, good idea
manjo    bjf, can you action me
manjo    so that I have this info for the next meeting
manjo    for/before
JFo    bjf, action me as well for the sending of the CFT
bjf    [ACTION] manjo to send a patch with test info
JFo    manjo, I’ll send it once you let me know it is built and where the test kernel is.
bjf    [ACTION] jfo to put out a CFT on new firewire stack
JFo    thanks bjf
 
 
kamal    Regarding bug 553498
ubottu    Launchpad bug 553498 in linux (Ubuntu Lucid) “Intel Core i3/i5/i7 hang on resume from suspend (SCI_EN)” [High,Fix committed] https://launchpad.net/bugs/553498
kamal    We have this marked as Fix Committed for Lucid, but the fix in Lucid (my original patch) only helps Dell Studio 155x machines, so isn’t really sufficient.
kamal    I would like to get M. Garrett’s better version of the fix (“Unconditionally set SCI_EN”, as it exists now in Maverick) pulled into Lucid so we can fix this for all i3/i5/i7 machines.
kamal    What is the procedure?
apw    kamal, propose it as an SRU patch in the normal way
apw    send it to the kernel-team list etc
tgardner    that one seems like a good stable update patch
kamal    ok, will do — can I change the bug state from “Fix Committed” back to “In Progress” or something also?
smb    Would there be chance that GregKH accepts it into stable upstream?
tgardner    smb reads my mind
apw    cirtainly worth asking …
bjf    kamal, you can also open a new bug just for the purposes of SRU, point back at the other bug
smb    kamal, as bjf suggest
kamal    bjf, ok I’ll open a whole new bug for this — should I ask GregKH about this directly?
smb    Sounds strange that the bug only closes dell but is named generically
kamal    the bug was originally titled “Dell Studio …” but I changed it after realizing that it affected all (?) i3/i5/i7 machines
apw    kamal, yeah we should get the title of the dell only bug fixed to be dell only and make the new one generic
smb    kamal, I wonder whether I have not written some notes how to do
smb    kamal, let me dig and get back to you
kamal    apw: ok, that makes sense re: the bug titling.
kamal    smb: I’ll wait for your notes.
kamal    thanks folks
Brad Figg

Kernel Team Meeting Minutes

June 8th, 2010 by Brad Figg
Categories: Uncategorized
No Comments

Meeting Minutes

IRC Log of the meeting.

Agenda

2010-06-08 Meeting Agenda

Release Metrics

Bugs

 
  Alpha 2 Milestoned Bugs (5) Release Targeted Bugs (50 across all packages (up 10))
linux 1 3

Milestoned Features

  • 14 blueprints (includes HWE blueprints)

Bugs with Patches Attached:122 (down 6 from last week)

Blueprint: kernel-maverick-apparmor

Started cross testing of compatibility patch and found some errors that need to fixed before it can be pulled in. Will try to get that cleaned up today so we can pull in the latest version, and send it upstream.
Caching patch fix – no progress still sitting on the back burner behind cold, compatibility patch, and EC2.

Blueprint: kernel-maverick-firewire-stack

Nothing new this week.

Blueprint: kernel-maverick-misc

The two items slipped out of Alpha-1 are still outstanding, though neither is a release task. The debian commonisation is currently progressing with Karmic master being retrofitted currently. We expect to have Karmic and Lucid master both complete by Wednesday, ready for test uploads.

Blueprint: kernel-maverick-new-kernel-on-lts

The Lucid LTS backport kernel is tracking Maverick at http://ppa.launchpad.net/kernel-ppa/ppa/ubuntu.
The current kernel and meta versions are linux-maverick-2.6.35-1.1~lucid1 and linux-meta-lts-backport-maverick-2.6.35.1.6.

Blueprint: kernel-maverick-pv-ops-ec2-kernel

pv-ops kernel has so far not been working out, and I am following up with Amazon.
Started looking at fallback plan 1 of pv-on-HVM driver but I haven’t been able to successfully build them yet (failing in the ballon driver atm). I need to test building them on an older stock kernel yet.

Blueprint: kernel-maverick-tracing-support

I (cnd) sent a patch upstream for relative source paths for perf probe, waiting on feedback
I took a closer look at trace-cmd and kernelshark and I’m not convinced quite yet that we really need kernelshark so I may just package up trace-cmd when I get the chance.

Blueprint: kernel-maverick-ubuntu-delta-review

I (ogasawara) own the majority of the Alpha2 work items so will start closing those out shortly.

Blueprint: kernel-maverick-union-mounts

Waiting on testing from Foundations from updated kernels. As part of the roll forward to v2.6.35-rc1 we have had to update AUFS2 as it no longer built. We expect to have to update it again before v2.6.35 final regardless of whether union-mounts make it.

Blueprint: kernel-maverick-bug-handling

Good progress on the wiki. There is now a Todo located at: https://wiki.ubuntu.com/Kernel/WikiToDo and a wiki gardening guide at: https://wiki.ubuntu.com/Kernel/WikiGardening Please use these references when working on the wiki pages.
Thanks to apw for getting those up and going

Blueprint: kernel-maverick-upstart

We have patches pending for the remaining Alpha-1 deliverable, waiting on testing from Foundations. We have also pulled forward the ‘readahead was used’ patches from Lucid testing to Maverick and pushed those to a further PPA for testing.

Blueprint: kernel-maverick-reducing-dkms-packages-required-for-hardware-enablement

Outcome was that “Tiger team” to discuss this to be set up by awe. This will be removed from the meeting agenda.

Blueprint: kernel-maverick-bios-test-automation 

  Added the following functionality to the firmware test suite:
      ACPI MCFG table test
      MTRR tests
      HPET sanity checks
      Simple Fan tests
      ACPI FADT table checks
      Simple Battery tests
      PCI Max Read Req sanity check
      BIOS EBDA check
  Misc:
      Add in e820 region checking
      Generalised list handling
      Fix iasl + pipe I/O bug
      Re-organise lib headers

Status: Maverick

We uploaded the 2.6.35-1.1 kernel which rebased us to 2.6.35-rc1. I’ll be uploading 2.6.35-2.2 within the hour. This will rebase us to 2.6.35-rc2. Please test if you are able to. Also, just a general reminder that Alpha 2 is Thurs July 1 (ie ~3weeks from today) so make sure you’re on track with any work items that need doing.

Security & bugfix kernels – Karmic/Jaunty/Intrepid/Hardy/Others 

  Dapper:        2.6.15-55.84  (security)
  Hardy:         2.6.24-28.70  (security)
  Jaunty:        2.6.28-19.61  (security)
  Karmic:        2.6.31-22.60  (security)
     - mvl-dove  2.6.31-214.28 (security)
     - fsl-imx51 2.6.31-112.28 (security)
     - ec2       2.6.31-307.15 (security)
  Lucid:         2.6.32-22.36  (security)
     - mvl-dove  2.6.32-205.18 (security)
     - fsl-imx51 2.6.31-608.14 (security)
     - ti-omap   2.6.33-501.7  (security)
     - qcm-msm   2.6.31-802.4  (security)
     - ec2       2.6.32-306.11 (security)
     - LBM       2.6.32-22.15  (waiting for acceptance to proposed)

The initial security release for Lucid caused a regression for KVM. Though the same patch is in Karmic and Jaunty without problems. It has been reverted for Lucid and an additional upload was made (thanks apw).

The current update to Lucid qcm-msm will be the last one as we lack testing hardware.

Currently preparing proposed uploads to Lucid and Karmic and while being on those, updating the abstracted debian implementation (apw). Lucid proposed will contain upstream stable 2.6.32.11-15 and 2.6.33.3-5 for DRM (amongst a lot of other changes). Target for upload to proposed for the master branch is Wednesday.

Incoming Bugs and Regression Stats

Incoming Bugs:

  Version Count
  Maverick 15 (+10)
  Lucid 946 (-59)

Current regression stats:

  Version Potential Update Release Proposed
  maverick 7 (+2)      
  lucid 234 (-28;) 25 (-1) 128 (-18) 1
  karmic   9 50 1
  jaunty   5 20  
  hardy   1 3  

Incoming Bugs: Bug day report

The next bug day will be next Tuesday. We will be focusing on working Confirmed bugs and getting them to either Incomplete, by waay of testing or information requests, or Triaged based on the completeness of the bug. My goal is to work through all of the Confirmed bugs to get them in the correct state and work out the best method for addressing them based on conversation with Andy yesterday. I also want to have a Team bug day much like we did this week to work the Top 50 list. I am open to having be two half days on Friday and Monday again if that worked out for everyone last time.
Any suggestions/objections? Was the two half days more useful than one whole one?

  • (ogasawara)I like the half days
  • (apw)I think half is better over all as its easier to do one or the other

Open Discussion or Questions: Anyone have anything?

apw Just a reminder that the wiki update is a team task, please do look over the ToDo and see if there are things you know about and can help clean up
manjo Is there a pointer (url) to the todo?
apw https://wiki.ubuntu.com/Kernel/WikiToDo
 
JFo Just wanted to mention that I have been invited to the QA meeting tomorrow to discuss the Triage Summit
JFo So I suspect there will be some more chat on it and I will be sending out an e-mail this week to kick things off
Brad Figg

Kernel Team Meeting Minutes

June 2nd, 2010 by Brad Figg
Categories: Uncategorized
No Comments

Meeting Minutes

IRC Log of the meeting.

Agenda

2010-6-1 Meeting Agenda

Maverick Release Metrics

Bugs

Alpha 1 Milestoned Bugs (0) Release Targeted Bugs (40 accross all packages)
linux 0 5

Blueprints

  • 14 Blueprints (includes HWE blueprints)

Bugs with Patches Attached: 130 (down 2 from last week)

Blueprint: kernel-maverick-apparmor (jjohansen)

Nothing new this week.

Blueprint: kernel-maverick-firewire-stack (manjo)

Nothing new this week.

Blueprint: kernel-maverick-misc (apw)

There are two outstanding items for Alpha-1, getting mainline builds to include linux-tools and progressing the -preempt pakcages. These are both non-release tasks. The first is likely to slip to alpha-2 now, the second is progresing but also likely to slip.

Blueprint: kernel-maverick-new-kernel-on-lts (tgardner)

LTS backport kernel and meta package are in the kernel-ppa. Its tracking maverick as its released.

Blueprint: kernel-maverick-pv-ops-ec2-kernel (jjohansen)

Slow progress, more testing without success. Will have to try pv-ops on HVM drivers this week.

Blueprint: kernel-maverick-tracing-support (cnd)

Kernel config is set, confirmed with upstream. No new work other than that yet.

Blueprint: kernel-maverick-ubuntu-delta-review (ogasawara)

There are only two work items still open for Alpha-1, both of which are not critical for Alpha-1′s release.

apw, manjo: if you don’t think you’ll get to those before Thurs, I’ll move them under the Alpha-2 milestone.

Blueprint: kernel-maverick-union-mounts (apw)

Still no testing feedback from foundations on union-mounts, there is talk of another drop occuring from upstream which will simplify the patches. It is unclear when this new drop will occur however.
We also have an issue with aufs2 in maverick which is leading to aufs2 panics during boot on the live-cd. I have an update for aufs2 which I am attempting to test to see if that fixes the issues. It is likely we will have to update aufs2 as soon as we are on 2.6.35-rcN. The update does appear to be good, and we are being asked to respin with aufs2 updated. Will get patches out shortly.

Blueprint: kernel-maverick-bug-handling (jfo)

Continuing work on the wiki pages with input from apw, ogasawara and smb. I plan to send some e-mail out on the ongoing effort today.
Also, I have some prep work happening that will move several topics to INPROGRESS.

Blueprint: kernel-maverick-upstart (apw)

We have patches pending for the remaining Alpha-1 deliverable, waiting on testing from Foundations. These would most readily be applied post Alpha-1.

Blueprint: kernel-maverick-reducing-dkms-packages-required-for-hardware-enablement (cking)

Nothing new this week

Blueprint: kernel-maverick-bios-test-automation (cking)

 *  Added functionality:
    *   Test for common BIOS error messages
    *   APIC edge/level trigger test
    *   acpiinfo: common kernel log ACPI checks
    *   Common S3/S4 PM kernel error checks
    *   S3 multiple suspend/resume cycle tests
    *   S4 hibernate/resume test
    *   Add in test run order/priority
    *   Rework kernel log scanning + execution of some user space tools
    *   Rework wakealarm code into common library calls
    *   Add ability to take pre-captured input from dmidecode, /proc/acpi/dsdt and dmesg rather than at run time
    *   Manoj added a test from the test suite into kernel-qa dev to prove the test suite integrates in okay.

Status: Maverick (ogasawara)

We uploaded the 2.6.34-5.12 Alpha 1 kernel last Friday. There will be no further uploads until after Thurs. Unfortunately the first iso’s were just spun yesterday and have uncovered 2 bugs we need to be aware of (thanks apw and tgardner for already taking ownership):

I should take that back, we might upload for the aufs bits. Also note that 2.6.35-rc1 was released so I’ll be rebasing Maverick today.

Security & bugfix kernels – Karmic/Jaunty/Intrepid/Hardy/Others (gnarl/smb)

 * Dapper:      2.6.15-55.83  (updates)
 * Hardy:       2.6.24-27.69  (updates)
 * Intrepid:    --- End of Support ---
 * Jaunty:      2.6.28-18.60  (updates)
 * Karmic:      2.6.31-21.59  (updates)
    - mvl-dove  2.6.31-213.27 (updates)
    - fsl-imx51 2.6.31-111.27 (updates)
    - ec2       2.6.31-306.14 (updates)
 * Lucid:       2.6.32-22.33  (updates)
    - mvl-dove  2.6.32-204.16 (release)
    - fsl-imx51 2.6.31-607.13 (release)
    - ti-omap   2.6.33-500.6  (release)
    - qcm-msm   2.6.31-800.2  (release)
    - ec2       2.6.32-305.9  (release)

Status unchanged from last week. Security release nearly out (probably tomorrow).

Incoming Bugs and Regression Stats

Incoming Bugs:

Version Count
Maverick 5 (+1)
Lucid 1005 (-129)

Current regression stats:

Version Potential Update Release Proposed
maverick 5 (+2)      
lucid 262 (-40;) 26 (+1) 146 (-3) 1
karmic   9 50 1
jaunty   5 20  
hardy   1 (-1) 3  

Incoming Bugs: Bug day report (JFo)

This week’s Bug Day will be on Thursday. I plan to send out an announcement for it later today with a reminder going out tomorrow. The current plan is to review Bugs with Patches attached to eliminate misreported patches and prepare the list for team review. Additionally, i will resume our use of the ‘cherry-pick’ tag to identify bugs with upstream commit SHA1s in them for us to review and react accordingly. You can see the list of these from this url

Open Discussion or Questions: Anyone have anything? (raise your hand please)

jfo Just wanted to draw your attention here
 
bjf Pointing to here
 
apw Remember we discussed the b43 driver not working, i’ve confirmed that it does not work in the current release kernel in lucid due to dma errors, etc.
  With smb’s latest stable 32.13 the b43 does work pretty well, and i am using it now
tgardner Is compat-wireless any better?
apw Can’t say i’ve tried it no