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.
* 13 blueprints (Including HWE blueprints)
Bugs with Patches Attached:111 (down 6 from last week)
No progress from last week. Doing the testing now
Nothing new this week.
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.
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.
Ported over the latest .34 Xen patchset, it currently has some issues, so we will stay with Lucid EC2 kernel until they are resolved.
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]].
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.
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.
- 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.
The initargs patches have now been tested, updated and pushed to the Maverick kernels. The ureadahead patches remain untested.
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)
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).
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.
- mvl-dove branch in lucid has been updated to sync with the latest Marvell
Nothing new this week; however, cooloney indicates that smb may have completed
some work to upload the kernel to -proposed.
- Nothing new this week; however, cooloney indicates that smb may have completed
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.
- A new topic branch named ti-omap4 was merged into Maverick. It is based on TI
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) 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:
- BugLink: Launchpad bug 509006 in linux-mvl-dove (Ubuntu) “[dove] hibernation failed to resume” [High,Confirmed]
- BugLink: Launchpad bug 576257 in linux-mvl-dove (Ubuntu Maverick) “[dove] BSP update for LSP 5.1.1″ [Undecided,Triaged]
- BugLink: Launchpad bug 591249 in linux-mvl-dove (Ubuntu Maverick) “[dove] BSP update for 5.2.1″ [Undecided,Triaged]
- BugLink: Launchpad bug 567157 in linux-fsl-imx51 (Ubuntu Maverick) “regulators enabled at boot and also print error messages at boot.” [High,In progress]
- BugLink: Launchpad bug 575558 in linux-fsl-imx51 (Ubuntu Maverick) “kernel panic when set mac address of FEC” [High,New]
- BugLink: Launchpad bug 559065 in linux-fsl-imx51 (Ubuntu) “ifconfig eth0 down will cause system hang after fec.c driver update” [High,In progress]
- BugLink: Launchpad bug 584920 in linux-ti-omap (Ubuntu Maverick) “netinstall fails, it has no network driver for moschip” [Medium,Fix committed]
- BugLink: Launchpad bug 566238 in linux-ti-omap (Ubuntu Lucid) “wlan0 “Interface doesn’t support scanning.” — CONFIG_CFG80211_WEXT is not set” [Undecided,Fix committed]
- ec2 has no specific changes
Incoming Bugs and Regression Stats
Current regression stats:
|lucid||223 (?)||34 (+4)||142 (+6)||1|
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.