Archive for November, 2010

Brad Figg

Kernel Team Meeting Minutes

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20101130 Meeting Agenda

ARM Status

  • Marvel (mvl-dove)

    • Nothing new this week.
  • Freescale (fsl-imx51)

    • Discussed merging their latest 2.6.35 BSP to our kernel tree. Might be Maverick.
  • Texas Instruments (ti-omap)

    • Tested Linaro 2.6.35 prebuilt kernel and Linaro 2.6.37 based kernel from their tree on OMAP Beagle board.
    • Linaro kernel works fine with Maverick and Natty minimal root file system.

Release Metrics

Release Meeting Bugs (6 bugs, 14 Blueprints)
==== Alpha 1 Milestoned Bugs (14 across all packages (up 1)) ====

  • 0 linux kernel bugs (no change)
  • 0 linux-ti-omap bugs (no change)
  • 0 linux-meta-ti-omap bug (no change)
    ==== Release Targeted Bugs (103 across all packages (up 8)) ====
  • 5 linux kernel bugs (up 2)
  • 0 linux-ti-omap bugs (no change)
  • 0 linux-meta-ti-omap bug (no change)
    ==== Milestoned Features ====
  • 6 blueprints (Including HWE Blueprints)
    ==== Bugs with Patches Attached:142 (up 2) ====
  • Bugs with Patches
  • Breakdown by status

Blueprints: Natty Bug Handling

  • Started on the list of bugs from the 5 teams that we identified as being where our most critical bugs come from.
    The list is available in its current form: http://reports.qa.ubuntu.com/reports/jfo/kernel-buglist-by-team.html
    It is still very rudimentary, but your feedback on it is still welcome.
  • I’ve also changed the bugs with patches item to in progress due to my initial review of the bugs as they currently
    stand. I have also begun doing some draft documentation on how to address these bugs in the proper way. I will
    be working with several of you to further refine this information in the near future.
  • Started looking at the arsenal scripts we have currently with a view toward getting them back running daily. I
    have several tasks identified for this week concerning documenting their process as well as working with
    Deryck H to address the limitation on how many can be processed at one shot.

Blueprints: Kernel Configuration Review

All configuration changes from the UDS review session are now applied and uploaded. Also the AGP drivers of interest have been identified and moved built-in. An ubuntu kernel with XEN_PCI_PLATFORMDEV has been tested in an Amazon Cluster Compute image. Further testing is needed within an Ubuntu Cluster Compute image, and testing is needed to see if it isn’t causing some of the issues in Bug #669496. Work benchmarking the effect of changing HZ is ongoing with a report due by natty-alpha-1.

Blueprints: Enhancements to the firmware test suite

Changes to fwts (natty development branch):

  • ACPI method testing: add some more advice feedback, check for infinite
    loop exeception errors.
  • bios mtrr tests: skip MtrrFixDramModEn test for non-AMD CPUs
  • acpitables: some MADT / APIC sanity checks, dump out P_LVL3_LAT correctly
  • bios mtrr tests: skip MtrrFixDramModEn test for non-AMD CPUs
  • acpitables: some MADT / APIC sanity checks, dump out P_LVL3_LAT correctly
  • get ACPI version number from /sys/module/acpi/parameters/acpica_version
  • various build warning fixes

Blueprints: Handling of Deviations from Standard Kernels

I added the deviation docs to the kernel trees. So last thing todo is the script.

Blueprints: Review of the Stable Maintenance Process (sconklin / bjf)

The first pass through the process went well, although we didn’t hold strictly to a two-week cadence, as we started with kernels ready for verification.
We had great help from certification on this, and they will have a representative joining us in this meeting starting next week.
We learned a lot and are refining the process, documented here:

  • https://wiki.ubuntu.com/Kernel/StableReleaseCadence

    In preparation for the beginning of the next stable kernel release, we ask that commits to all -next branches be held until the
    stable kernel team has completed merging those changes with the master branches.
    We will announce on ubuntu-kernel-team mailing list when the -next branches are open again.

Blueprints: Ubuntu Kernel Delta Review

A number of small changes dropping old no longer required patches. 13 of the 19 personal patch reviews are now done. Some of these are likely to miss the natty-alpha-1 deadline, but none are release critical for the milestone.

Blueprints: Kernel Version and Flavours

Preliminary testing of the Linaro OMAP3 kernel suggests it does contain the require Ubuntu delta and will boot the Beagle board (our target platform). We are waiting on working ARM CD images to allow substitution of this kernel for further Ubuntu feature testing. As ARM CDs are not expected until the end of the week some of this is likely to miss natty-alpha-1; work items moved out as appropriate.

Status: Natty

The final kernel for natty-alpha-1 (2.6.37-7.18) has been uploaded, built and is in the archive. This is a v2.6.37-rc3 based kernel carrying all of the configuration harmonisation and much of the Ubuntu patch delta review feedback. We are expecting to upload a futher kernel carrying a v2.6.37-rc4 rebase as soon as the milestone freeze lifts. Please test the alpha CDs once they come out.

Security & bugfix kernels – Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf)

      Upd./Sec.    Proposed    TiP    Verified   
   Dapper: Kernel    2.6.15-55.89            
   Hardy: Kernel    2.6.24-28.81            
   = LRM    2.6.24.18-28.7            
   Karmic: Kernel    2.6.31-22.69            
   = mvl-dove    2.6.31-214.32            
   = ec2    2.6.31-307.21            
   Lucid: Kernel    2.6.32-26.48            
   = LBM    2.6.32-25.24    2.6.32-26.25         
   = mvl-dove    2.6.32-209.27            
   = fsl-imx51    2.6.31-608.19    2.6.31-608.20         
   = ec2    2.6.32-309.18            
   = lts-backport-maverick    2.6.35.22.34            
   Maverick: Kernel    2.6.35-23.41            
   = mvl-dove    2.6.32-410.27    2.6.32-412.28         
   = ti-omap4    2.6.35-903.18            
  • In the last week, a security update was prepared and released.

Incoming Bugs: Regressions

Incoming Bugs
19 Natty Bugs (up 7)
1088 Maverick Bugs (up 26)
1109 Lucid Bugs (up 21)
Current regression stats (broken down by release):

regression-potential

As this tag is deprecated, this listing is only to ensure that I keep it on my radar until
changes to the apport hooks and my processing of the currently tagged bugs is completed.

  • 1 natty bugs
  • 394 maverick bugs
  • 178 lucid bugs

regression-update

  • 23 maverick bugs (up 3)
  • 81 lucid bugs (up 3)
  • 6 karmic bugs (no change)
  • 0 hardy bugs (no change)

regression-release

  • 167 maverick bugs (up 11)
  • 199 lucid bugs (up 7)
  • 40 karmic bugs (no change)
  • 2 hardy bugs (no change)

regression-proposed

  • 13 maverick bugs (no change)
  • 6 lucid bugs (no change)
  • 1 karmic bug (no change)

Triage Status

The first iteration of the Bug List is running hourly. It is available:

http://reports.qa.ubuntu.com/reports/jfo/kernel-buglist-by-team.html

As always your feedback on it is much appreciated.
Bug Expiration seems to be working. I have seen several bugs Expired by the system recently. I am trying to work out how
to see what is being expired (number wise) versus what we would have expired with our arsenal script. This is mainly to see
if the process is working as we expect so that I can provide that feedback to the LP team.

Incoming Bugs: Bug day report

The next bug day will be next Tuesday covering regression-update bugs. there are 118 bugs that need to
be looked at, the majority of which will need to be tested against the latest released version and the current version in
development. I’ll send out an e-mail today concerning the day. I’ll also post a blog post on our voices page.

Jeremy Foshee

Kernel Bug Day Tuesday, 7 December, 2010

Hi everyone!

It is time once again to hold a Kernel Bug Day. I will start blogging these events now instead of only sending out the usual e-mail. I hope that some of you will join in.

This Tuesday, December 7th, the Kernel team will conduct a Bug Day focused on bugs tagged ‘regression-update’. These bugs are an indication that some update to the kernel caused a failure. We’d like for these bugs to be brought current by requesting testing on one of the other versions to include mainline and current development. Your help in requesting that information and in completing the general triage of these bugs would be greatly appreciated. :-)

Information concerning the Bug Day itself can be located on the wiki at https://wiki.ubuntu.com/Kernel/BugTriage/BugDay. As noted there and in the e-mail I sent out earlier, should you desire a head start on the triage day, that contribution too is most appreciated.

I will be available in the #ubuntu-kernel channel of the FreeNode IRC server should you have any questions.

Happy Triaging!

~JFo

Brad Figg

Kernel Team Meeting Minutes

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20101123 Meeting Agenda

ARM Status

  • Marvel (mvl-dove)

    • Marvell’s latest LSP, 5.3.6 has been integrated into our tree and uploaded.
  • Freescale (fsl-imx51)

    • Nothing new this week
  • Texas Instruments (ti-omap)

    • Bug #666267 – Added DKMS package to this bug and asked for help from Mario. TI is
      still based on the 2.6.35 kernel. It is unlikely that we will be cherry-picking
      patches due to their proliferation all over the tree. They (TI) may move to 2.6.38
      next year.

Release Metrics

Release Meeting Bugs (6 bugs, 13 Blueprints)

Alpha 1 Milestoned Bugs (13 across all packages (down 1))

  • 0 linux kernel bugs (no change)
  • 0 linux-ti-omap bugs (no change)
  • 0 linux-meta-ti-omap bug (no change)

Release Targeted Bugs (95 across all packages (up 9))

  • 3 linux kernel bugs (no change)
  • 0 linux-ti-omap bugs (no change)
  • 0 linux-meta-ti-omap bug (no change)

Milestoned Features

  • 1 blueprints (Including HWE Blueprints)

Bugs with Patches Attached:140 (up 2)

Blueprints: Natty Bug Handling

nothing to report this week

Blueprints: Kernel Configuration Review

All configuration changes from the UDS review session are now applied and uploaded. Also the AGP drivers of interest have been identified and moved built-in. Only two items remain, neither critical for natty-alpha-1. These items are still on track for natty-alpha-1 completion.

Blueprints: Enhancements to the firmware test suite

Changes to fwts (natty development branch):

  • Add in methods tests – 69 new tests to exercise AML Methods
  • Added error checking with CMOS reads
  • Improved FACS 32/64 pointer mismatch checks in FADT
  • Check for \_SB_._OSC buffer overflows

Blueprints: Handling of Deviations from Standard Kernels

Just sent out some rfc for the in-tree documentation
Suggestion was for json format but making it simpler for a script seems not a good reason for changing the format for now
So I would still go with the maintainers format for now

Blueprints: Review of the Stable Maintenance Process (sconklin / bjf)

We’ve successfully wrapped up our first trial of the new stable kernel process. Lucid and Maverick
kernels currently in -proposed are being promoted to -updates today. Everyone involved in the new
process have identified areas they will be working to improve for the next cycle. Current thinking
is the next cycle will start with an upload on Dec. 9.

Blueprints: Ubuntu Kernel Delta Review

aufs2 updated to official 2.6.37-rcN release from upstream. LIRC patches dropped to clean up the delta. 6 of the 21 personal patch reviews are now done. Some of these are likely to miss the natty-alpha-1 deadline, but none are release critical for the milestone.

Blueprints: Kernel Version and Flavours

Discussions are ongoing as to the kernels to use for omap3, this centres around whether the Linaro kernel is fully featured enough and what levels of support we are able to provide for it. Discussions continue but we are currently waiting on testing of the Linaro kernel against the current userspace. This will not become critical until natty-alpha-2.

Status: Natty

The distro kernels are now rebased onto v2.6.37-rc3 and uploaded. This latest kernel includes a further update to aufs bringing it in line with upstream. It also carries the bulk of the configuration changes identified at UDS, harmonising a number of options; where those options are there to fix FTBS those are now documented. It also carries a preview of the latest version of the “200 line” miracle automatic scheduler group patch, any feedback on this kernel appreciated. Testing generally remains good.

Security & bugfix kernels – Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf)

* Lucid and Maverick -proposed kernels promoted to -updates.
* Call for further testing of ec2 and ARM -proposed kernels for Lucid and Maverick.
I’ve pinged Tobin Davis for ARM.

   Upd./Sec.    Proposed    TiP    Verified   
Dapper: Kernel    2.6.15-55.89            
Hardy: Kernel    2.6.24-28.80            
= LRM    2.6.24.18-28.7            
Karmic: Kernel    2.6.31-22.68            
= mvl-dove    2.6.31-214.30    2.6.31-214.32         
= ec2    2.6.31-307.21            
Lucid: Kernel    2.6.32-26.47            
= LBM    2.6.32-25.24    2.6.32-26.25         
= mvl-dove    2.6.32-209.25    2.6.32-211.27         
= fsl-imx51    2.6.31-608.19    2.6.31-608.20         
= ec2    2.6.32-309.18            
= lts-backport-maverick    2.6.35.22.34            
Maverick: Kernel    2.6.35-23.40            
= mvl-dove    2.6.32-410.27            
= ti-omap4    2.6.35-903.18            

Incoming Bugs: Regressions

Incoming Bugs
19 Natty Bugs (up 7)
1062 Maverick Bugs (up 37)
1088 Lucid Bugs (up 6)
Current regression stats (broken down by release):

regression-potential

As this tag is deprecated, this listing is only to ensure that I keep it on my radar until
changes to the apport hooks and my processing of the currently tagged bugs is completed.

  • 3 natty bugs
  • 396 maverick bugs (up 32 since the final maverick meeting)
  • 177 lucid bugs (up 14 since the final maverick meeting)

regression-update

  • 20 maverick bugs (no change)
  • 78 lucid bugs (up 1)
  • 6 karmic bugs (no change)
  • 0 hardy bugs (no change)

regression-release

  • 156 maverick bugs (up 9)
  • 192 lucid bugs (down 1)
  • 40 karmic bugs (no change)
  • 2 hardy bugs (no change)

regression-proposed

  • 13 maverick bugs (no change)
  • 6 lucid bugs (down 1)
  • 1 karmic bug (no change)

Incoming Bugs: Bug day report

Today is the Bug Day. It is focusing on Bugs with patches so that I can focus
on getting the particular process I must use to address these bugs organized.
I will likely be pinging several of you with questions over the next week as
I work to finalize these steps and get them documented.
The next bug day will on December 7th. I will define the scope of that bug day in my e-mail
to the list so that I can take some time to determine what the best use of that
day will be.

Triage Status

Spoke this week with Tapas Mishra who is interested in helping out. We had a great conversation on where to start. This conversation had been preceeded by someone providing several key links to wiki documentation that provided a first step toward Tapas’ desire to work on wireless issues. My recommendation was to look at current wireless bugs that have been filed and use those issues to gain an understanding of the type of issues we see with wireless drivers. Unforunately, due to the modular, and sometimes closed corporate nature of wireless drivers, we don’t have a way to help someone who is interested in beginning coding on wireless drivers, but I am hopeful that the information I was able to provide and the recommendations smb and I made will be helpful.

Open Discussion or Questions: Raise your hand to be recognized

  • Just a question how comfortable those with upload rights are with the patch piloting and whether they would know what to do. There are some links in the original email which are intended to help one http://wiki.ubuntu.com/UbuntuDevelopment/CodeReviews

    • The concensus is we don’t really know much about it.

  • Just a heads up that alpha1 is coming up. Get your changes in.
Brad Figg

Kernel Team Meeting Minutes

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20101116 Meeting Agenda

ARM Status

  • TI – They are still stabilizing 2.6.35 based kernel for omap4. And they will probably skip 2.6.36 and move to 2.6.37 directly, but it won’t happen before December.

Release Metrics

Release Meeting Bugs (0 bugs, 12 Blueprints)

Alpha 1 Milestoned Bugs (14 across all packages)

  • 0 linux kernel bugs (no change)
  • 0 linux-fsl-imx51 bugs (no change)
  • 0 linux-ec2 bugs (no change)
  • 0 linux-mvl-dove bugs (no change)
  • 0 linux-ti-omap bugs (no change)
  • 0 linux-meta-ti-omap bug (no change)

Release Targeted Bugs (86 across all packages)

  • 3 linux kernel bugs (no change)
  • 0 linux-fsl-imx51 bugs (no change)
  • 0 linux-ec2 bugs (no change)
  • 0 linux-mvl-dove bugs (no change)
  • 0 linux-ti-omap bugs (no change)
  • 0 linux-meta-ti-omap bug (no change)

Milestoned Features

  • 1 blueprints (Including HWE Blueprints)
    This number is wrong. The only blueprint I see on the list is mine.

Bugs with Patches Attached:138 (up 14) since the last meeting 1 month ago

  • Bugs with Patches
  • Breakdown by status
    As these are now one of my main focus points. I will begin working specifically on them this week.
    The goal is to beat this number back to zero and then maintain as close to that as possible going forward.
    I’ll be asking some of you to review bugs as needed to assess their viability and to improve my work on the overall
    list over time. Once I have the hang of it, I hope to submit those patches that make sense to the list for review.

Blueprints: Natty Bug Handling

nothing to report

Blueprints: Enhancements to the firmware test suite

Changes to fwts (natty development branch):

  • remove need for sudo when loading ACPI tables from file (bug fix)
  • initial ACPI tables field checking – on common fields that give most issues
  • move kernel log tables into json format data
  • remove –fwts-debug
  • –stdout-summary outputs FAILED levels, e.g FAILED_HIGH, FAILED_LOW, etc
  • adjust log width to match tty width when logging to stdout
  • add aborted and skipped test to summary
  • cpufreq: make this an experimental test as it’s not fully validated yet
  • check for non-compliant brightness levels
  • working on AML method sanity checking

Blueprints: Handling of Deviations from Standard Kernels

Small progress in the documentation, will do the in tree doc next and try the tooling.
For the drm33 upstream kernel I finished the scripting and have sent out the first patch queued notice

Blueprints: Review of the Stable Maintenance Process

We’re roughly half way through the first trial of the new stable kernel process, which is outlined here;

https://wiki.ubuntu.com/Kernel/StableReleaseCadence

Yesterday, we reverted commits for bugs without verification, and uploaded the resulting kernels this morning.
As soon as they are built, they will require QA and Cert testing before being released.

For Maverick, The following bugs had commits reverted due to lack of verification:

  • 598938 [Realtek ALC269] ALSA test tone not correctly played back
  • 637291 [Realtek ALC269] ALSA test tone not correctly played back; no audio on laptop speakers but
  • 648871 [Realtek ALC269] ALSA test tone not correctly played back
  • 642892 [Realtek ALC269] ALSA test tone not correctly played back
  • 655386 no audio playback except with headphones but it is extremely quiet
  • 546769 no sound with Realtek ALC269 – on Sony Vaio VPCEB1S1E
  • 663642 DVI doesn’t work at BeagleBoard xM rev A3
  • 580749 Pulseaudio is not running VT1708

    For Lucid, The following bugs had commits reverted due to lack of verification:

  • 598938 [Realtek ALC269] ALSA test tone not correctly played back
  • 637291 [Realtek ALC269] ALSA test tone not correctly played back; no audio on laptop speakers but
  • 642892 [Realtek ALC269] ALSA test tone not correctly played back
  • 655386 no audio playback except with headphones but it is extremely quiet
  • 546769 no sound with Realtek ALC269 – on Sony Vaio VPCEB1S1E
  • 580749 Pulseaudio is not running VT1708
  • 605047 Internal Microphone on Dell Lattitude e6410 does not work
  • 628776 HP NC511i Driver (be2net and be2scsi) is missing in kernel module udebs
  • 580749 Pulseaudio is not running VT1708
  • 465942 Hardware device disappearing from Sound Preferences on ASUS 0x104381b3
  • 587546 Pulseaudio fails after several seconds
    General comments on the new stable cadence process:
    * Thanks for all the help and understanding. This first test run through the process steps has been very labor intensive, slow, and error prone.
    * We are refining the process as we go. Details are being maintained on the wiki page linked above.
    * Martin Pitt has agreed to change the verification tagging for bugs to “verification=[needed|failed|done]-”
    in order to help us track verification in different released kernels within the same bug.

    Reverted patches will be reapplied once the appropriate action is taken in the bug report. For specific details see:

    https://wiki.ubuntu.com/Kernel/StableReleaseCadence

Status: Natty

apw just uploaded -4.13 yesterday. the 2.6.37-rc2 is in the works.

Security & bugfix kernels – Maverick/Lucid/Karmic/Hardy/Dapper

   Upd./Sec.    Proposed    TiP    Verified   
Dapper: Kernel    2.6.15-55.89            
Hardy: Kernel    2.6.24-28.80            
= LRM    2.6.24.18-28.7            
Karmic: Kernel    2.6.31-22.68            
= mvl-dove    2.6.31-214.30    2.6.31-214.32         
= ec2    2.6.31-307.21            
Lucid: Kernel    2.6.32-25.45    3.6.32-26.47    14    6 / 24   
= LBM    2.6.32-25.24    2.6.32-26.25         
= mvl-dove    2.6.32-209.25    2.6.32-211.27         
= fsl-imx51    2.6.31-608.19    2.6.31-608.20         
= ec2    2.6.32-309.18            
= lts-backport-maverick    2.6.35.22.34            
Maverick: Kernel    2.6.35-22.35    3.6.35-23.38    14    12 / 30   
= mvl-dove    2.6.32-410.27            
= ti-omap4    2.6.35-903.18            

Incoming Bugs: Regressions

Incoming Bugs
12 Natty Bugs
1025 Maverick Bugs (up 304 since the final maverick meeting)
1082 Lucid Bugs (up 68 since the final maverick meeting)
Current regression stats (broken down by release):

regression-potential

As this tag is deprecated, this listing is only to ensure that I keep it on my radar until
changes to the apport hooks and my processing of the currently tagged bugs is completed.

  • 3 natty bugs
  • 396 maverick bugs (up 32 since the final maverick meeting)
  • 177 lucid bugs (up 14 since the final maverick meeting)

regression-update

  • 20 maverick bugs
  • 77 lucid bugs (up 13)
  • 6 karmic bugs (no change)
  • 0 hardy bugs (no change)

regression-release

  • 147 maverick bugs
  • 193 lucid bugs (up 16)
  • 40 karmic bugs (up 3)
  • 2 hardy bugs (no change)

regression-proposed

  • 13 maverick bugs
  • 7 lucid bugs (up 1)
  • 1 karmic bug (no change)
    Please note that I have removed Jaunty from the listing above.

Incoming Bugs: Bug day report

The next Kernel Bug Day will be next Tuesday. The focus will be on bugs with patches attached
in order to begin the serious amount of work to be done there. I am planning to work with Andy
and Tim this week to see how we will handle Team Bug Days since we are changing the way we do
the Top Bugs each week. I will also begin working up a weekly report of the major bugs we are looking at.
Chances are I will make some of that data available during this meeting going forward.

Please note that if we take any of those patches, we either need the HW to verify them or have a commitment from the community to verify them or they weill be reverted

Triage Status

I talked with a number of the folks we work with to triage bugs during UDS, but, other than that,
I have nothing to report on as far as status. I am, however, interested in your thoughts on holding
another Kernel Triage Summit. We could do our own again, or we can make it a part of one of the
community events such as Ubuntu Developer Week, Open Week, etc.

Based on all the effort that you’ve put into getting community involvement, did we get any value or would you have been better off just doing that amount of effort in triaging yourself?

We saw some benefit, but I think it is too early to tell the impact. I’d have to defer to those who presented and attended as to the usefulness. I felt it was a success, more so than I had hoped for.

I’m asking about community triaging in general

We saw some improvement, but I don’t know if it was commensurate with the effort involved in organizing our own.
In summary I think I could have just done the triage effort myself.

Open Discussion or Questions

Noting new this week.

Brad Figg

Kernel Team Meeting Minutes

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20101109 Meeting Agenda

ARM Status

  • Marvell dove

    • Nothing new (they’ve shipped their LSP 5.3.6)
  • Texas Instruments

    • for ti-omap4, we just fixed a config issue bug 672635
    • PATCH : PowerSGX patch:
      .Spent a lot of time looking at powerSGX
      .Studied 3 implementation: Android, Meego and rcn-ee
      .The Meego patch was folded in linaro-linux-2.6.35 but got rejected -) not upstreamable
      .To be accepted, the patch would have to be nursed through the iteration process -) this is a full time assignment
      .Going from ubuntu to linaro for kernel maintenance mandate that submitted patches be upstreamable

Blueprints: Kernel Configuration Review

Configuration changes are defined and approved. Work has not yet started on applying these, should hit before natty-alpha-1.

Blueprints: Enhancements to the firmware test suite

Changes to fwts (natty development branch):

  • Added more intelligence in backlight issues found in klog
  • add –show-tests-full option
  • add –lp-tags to print out LP tags when scanning klog errors
  • make -p (show progress) default
  • add -q, –quiet option
  • add –dumpfile to load tables from acpidump and fwts –dump output
  • prototyped ACPI method execution for sanity checks and mutex state checks

Blueprints: Handling of Deviations from Standard Kernels

Not much to add for the moment. Working on the announcement scripts. And I guess someone needs to do the documentation at some point…

Blueprints: Review of the Stable Maintenance Process

During UDS, discussions were held which resulted in the adoption of a new process for release of stable kernel updates. Details about why this was needed and how it will be implemented have been committed to the Ubuntu wiki here:

https://wiki.ubuntu.com/Kernel/StableReleaseCadence

It looks like the first official cycle may start on Nov 18th, but this is still in discussion.

The question was asked, “how are we progressing on the testing front” to which the answer is: “we aren’t”. We will be asking that someone responsible for testing attend this meeting to report out on the progress.

Lots of discussion with how to handle reverting patches (or not). The decision was made to take the discussion to #ubuntu-kernel.

Blueprints: Ubuntu Kernel Delta Review

Work has started on updating the Ubuntu drivers. Work centers on updating aufs2 which is a blocker for (performant) live-cds. Pulled in an experimental version of aufs2 for testing in v2.6.36. Also pulled this up to v2.6.37-rc1 and did some testing. Looking good so far.

Blueprints: Kernel Version and Flavours

Pulled the ports meta-packages into the main master branch to simplify ongoing maintenance.

Status: Natty

Natty has just moved over to a v2.6.37-rc1 based kernel. Stability is unexpectedly high. Work is ongoing to get aufs2 working again so we can have performant live-cds shortly; likely in the next upload. Blueprints are mostly up to date with initial work items and work is just beginning on our deliverables.

Anyone who has not yet added milestones for their work items are likely to find I have assigned them one. You may well find that means your entire natty workload is now scheduled for natty-alpha-1. Please review these and split them out as necessary.

Security & bugfix kernels – Maverick/Lucid/Karmic/Hardy/Dapper

   Upd./Sec.    Proposed    TiP    Verified   
Dapper: Kernel    2.6.15-55.89            
Hardy: Kernel    2.6.24-28.80            
= LRM    2.6.24.18-28.7            
Karmic: Kernel    2.6.31-22.68            
= mvl-dove    2.6.31-214.30    2.6.31-214.32         
= ec2    2.6.31-307.21            
Lucid: Kernel    2.6.32-25.45    3.6.32-26.46    14    6 / 24   
= LBM    2.6.32-25.24    2.6.32-26.25         
= mvl-dove    2.6.32-209.25    2.6.32-211.27         
= fsl-imx51    2.6.31-608.19    2.6.31-608.20         
= ec2    2.6.32-309.18            
= lts-backport-maverick    2.6.35.22.34            
Maverick: Kernel    2.6.35-22.35    3.6.35-23.37    14    12 / 30   
= mvl-dove    2.6.32-410.27            
= ti-omap4    2.6.35-903.18            
  • The Karmic proposed kernel has been moved to updates.
  • Jaunty is no longer supported

Open Discussion or Questions: Raise your hand to be recognized

  • For those who own a blueprint could you add a ‘Status:’ block to your whiteboards which should be a couple of sentences covering the current progress and any blockers.
  • Discussion about “Subject: Ubuntu ARM and the linaro kernels” (https://lists.ubuntu.com/archives/ubuntu-devel/2010-November/031952.html). Noone knows how or if we will be using linaro provided kernels for natty distro development.