Archive for September, 2010

Brad Figg

Kernel Team Meeting Minutes

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20100928 Meeting Agenda

ARM Status

lag chases snakes in his sleep.

Release Metrics:

please note that the statistics are for a 2 week time period:

Release Meeting Bugs (5 bugs, 9 Blueprints)

Release Milestoned Bugs (26 across all packages (down 45))

  • 1 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 (144 across all packages (down 51))

  • 13 linux kernel bugs (up 6)
  • 0 linux-fsl-imx51 bugs (down 1)
  • 0 linux-ec2 bugs (down 1)
  • 2 linux-mvl-dove bugs (down 1)
  • 0 linux-ti-omap bugs (down 1)
  • 0 linux-meta-ti-omap bug (no change)

Milestoned Features

  • 13 blueprints (Including HWE Blueprints)

Bugs with Patches Attached:121 (down 2)

Blueprint: kernel-maverick-bug-handling

Remaining items postponed. To be discussed at UDS.

Status: Maverick

The Maverick Release Candidate comes out this Thurs Sept 30 and the Release Team has stopped processing upload requests for the Ubuntu 10.10 Release Candidate. See https://wiki.ubuntu.com/ReleaseCandidateProcess for more info.

We’ve been queuing patches for Maverick SRU which includes the latest 2.6.35.5 and 2.6.35.6 stable updates. We are also planning a 0-day kernel upload which has been documented at bug 647071 . I’d finally like to point out that we have closed out all Maverick blueprint work items \o/. We have been and will be below the trend line for the entire Maverick cycle for our overall burn down chart.

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

   Upd./Sec.    Proposed    TiP    Verified   
Dapper: Kernel    2.6.15-55.88            
Hardy: Kernel    2.6.24-28.79            
= LRM    2.6.24.18-28.7            
Jaunty: Kernel    2.6.28-19.65            
Karmic: Kernel    2.6.31-22.65    2.6.31-22.66    5    1/ 4 (+ 1)   
= mvl-dove    2.6.31-214.30    2.6.31-214.32    5    1/ 4 (+ 1)   
= fsl-imx51    — retired —            
= ec2    2.6.31-307.17    2.6.32-307.18    5    1/ 4 (+ 1)   
Lucid: Kernel    2.6.32-25.44            
= LBM    2.6.32-25.23    2.6.32-25.24    1    0/ 1   
= mvl-dove    2.6.32-209.25    2.6.32-211.27    0      
= fsl-imx51    2.6.31-608.19    2.6.31-608.20    0      
= ti-omap    2.6.33-502.10    (in progress)         
= ec2    2.6.32-308.16    (in progress)         
  • The Lucid proposed kernel has been moved to updates. Topic branch updates
    which are rebased against this have or will be uploaded.
  • Karmic fsl-imx51 has been retired.

Incoming Bugs: Regressions

629 Maverick Bugs (up 96)

978 Lucid Bugs (down 58)

Current regression stats (broken down by release):

regression-potential

  • 320 maverick bugs (up 48)
  • 160 lucid bugs (down 10: to be converted to regression-release)

regression-update

  • 55 lucid bugs (up 8)
  • 7 karmic bugs (no change)
  • 4 jaunty bugs (no change)
  • 0 hardy bugs (no change)

regression-release

  • 170 lucid bugs (down 11)
  • 36 karmic bugs (down 1)
  • 17 jaunty bugs (down 1)
  • 2 hardy bugs (down 1)

regression-proposed

  • 6 lucid bugs (down 1)
  • 1 karmic bug (no change)
    Jaunty bugs will be closed and removed from this list once Jaunty EOLs

Incoming Bugs: Bug day report

I’ve put off the bug day till next week due to the past week of traveling. The next Kernel Community Bug Day will be on bugs in the New status improperly.

There are curently about 1500 bugs in the New state. My guess is that many of these are the result of people simply marking Expired bugs to new without doing the requested tasks. The majority should move to Invalid or Triaged depending on the reporters interaction.

We will continue to have the Team Bug Day to address the Top 50 list as half days on Friday and Monday unless someone has an objection.

Reviewers, please take a look at your needs-review lists and help us keep the process moving. There are several lists that are not getting a look.
Please also take ownership of your bugs as you work them so we can get them fixed or otherwise off the list. There are a number in need of love.
There are several subsystems owned by all that need to be reviewed for inclusion in our top 50 list.

Triage Status

There was a surprising amount of attendance in the UHS Kernel Bugs talk and a number of the participants were actively listening, so I hope this means that we will have some good buy in on the process form these folks should any of them come on board with hardware/kernel bugs.
Since I was traveling, I have not had the chance to interact with the community over the past week.

Open Discussion or Questions: Raise your hand to be recognized

Nothing this week.

Brad Figg

Kernel Team Meeting Minutes

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20100914 Meeting Agenda

ARM Status

  • Marvel (mvl-dove)

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

    • ON GOING : B605042: Java segfault on Freescale iMX5.1 Babbage board with Lucid – will try to bisect Lucid 2.6.31 kernel
  • Texas Instruments (ti-omap)

    • ON GOING : B591941 Original patch was not complete – Adrian Hunter should release the final patch this week.
    • ON GOING : B608266 Fix submitted and accepted – still waiting for mobile team to test.
    • ON GOING : B633227 ES2.0 board is unstable when highmem is enabled – backported a patch from upstream to solve memtester issue
    • ON GOING : B628029 ES2.0 board does not boot with CONFIG_PM enabled
    • NEW : B622935 a patch has been written – author needs to send it upstream
    • PATCH : Lots of TI audio patches have now been applied – testing under way
    • PATCH : B563650 upstream patch was applied
    • PATCH : B477106 Lucid alpha-2 and earlier freeze upon suspend with sd card plugged in with some hardware
    • PATCH : B588243 upstream patch was applied
    • FIXED : B613855 omap3 beagle XM MMC card always comes up read-only
    • FIXED : B605488 scheduling while atomic: mmcqd/46/0×00000002
    • FIXED : B589624 omap flavour does not work on beagle XM board
    • FIXED : B605832 LG monitor behaving incorrectly when used in conjunction with the Panda board and HDMI
    • FIXED : B477106 Maverick alpha-2 and earlier freeze upon suspend with sd card plugged in with some hardware
    • FIXED : B592295 omapdss DISPC error: SYNC_LOST_DIGIT
    • FIXED : B628107 false alarm – first boot loaded unstable kernel

      (tgardner) lag, is yuor memtest solved with the cache line patch?
      (lag) It’s not mine, but I don’t believe that it is
      (tgardner) ok

Release Metrics:

Release Meeting Bugs (12 bugs, 9 Blueprints)

Release Milestoned Bugs (71 across all packages (down 8))

  • 1 linux kernel bugs (no change)
  • 0 linux-fsl-imx51 bugs (down 1)
  • 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 (195 across all packages (down 7))

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

Milestoned Features

  • 13 blueprints (Including HWE Blueprints)

Bugs with Patches Attached:123 (up 6)

Blueprint: kernel-maverick-bug-handling

Nothing to report.

Blueprint: kernel-maverick-bios-test-automation

  • Changes this week to fwts:

    • Updated USB boot image tests to use the ncurses based dialog interface
    • natty branch:
      mtrr: test for SYSCFG[MtrrFixDramModEn], more intelligent mtrr testing
      klog + acpi tests: check for single MADT
      pci: check for _CRS PCI host bridge configuration
      acpidump: annotated dump of ERST, SLIT, SRAT, SBST, ECDT, CPEP, BERT,
      DSDT, SSDT, RSDT, XSDT
      lib: hexdump
      bios: romdump (dump BIOS + option ROMs)
      framework: add –show-progress-dialog option for dialog tool

      Note, this agenda item is finished for the Maverick development cycle and will be removed from the meeting agenda.

Status: Maverick

We’ve uploaded a new Maverick kernel, 2.6.35-21.31. This was to resolve linux-libc-dev ti-omap4 version conflicts which prevented any armel uploads.

Kernel Freeze is this Thurs Sept 16th. After Kernel Freeze, we transition to our SRU policy. I plan to upload our final Maverick kernel Sept 17th. There is little to no room for uploading any kernels beyond the 17th as the archive will freeze in preparation for Mavrick’s 10.10 Release Candidate. Any patches which have any hope of landing the the 10.10 Maverick kernel need to be submitted and garnered the appropriate
Ack’s prior to the 16th.

We are again nearing being above the trend line for our overall burn down chart. We need to start closing out all remaining open work items.
JFo, sconklin, apw, tgardner, jjohansen, smb: It appears you have open work items. Please review if your work item(s) can be marked as DONE or POSTPONED, else get er done.

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

   Upd./Sec.    Proposed    TiP    Verified   
Dapper: Kernel    2.6.15-55.87            
Hardy: Kernel    2.6.24-28.77    (pending)         
Jaunty: Kernel    2.6.28-19.64            
Karmic: Kernel    2.6.31-22.63    2.6.31-22.64    21    0/ 4   
= mvl-dove    2.6.31-214.30    2.6.31-214.31    21    0/ 4   
= fsl-imx51    2.6.31-112.28            
= ec2    2.6.31-307.17    2.6.31-307.18    21    0/ 4   
Lucid: Kernel    2.6.32-24.42    2.6.32-25.43    13    1/25 (+ 1)   
= LBM    2.6.32-24.17    2.6.32-25.22    13    0/ 4   
= mvl-dove    2.6.32-209.25    (pending)         
= fsl-imx51    2.6.31-608.19            
= ti-omap    2.6.33-502.10            
= ec2    2.6.32-308.15            
  • There are very little to no verifications coming in for the Karmic and Lucid
    proposed kernels. It looks like we need to start our own bug(them)-squad.
  • Accepting packages into proposed also faces some delays as pitti was on
    holiday and it feels like there is no real backup there.
  • Karmic-fsl-imx51 sounds like being dead to me. We should probably make an
    official announcement that we won’t do any security updates on it anymore
    and see whether anybody cries.

Incoming Bugs: Regressions

533 Maverick Bugs (up 85)

1036 Lucid Bugs (up 39)

Current regression stats (broken down by release):

regression-potential

  • 272 maverick bugs (up 47)
  • 170 lucid bugs (up 4: to be converted to regression-release)

regression-update

  • 47 lucid bugs (down 2)
  • 7 karmic bugs (no change)
  • 4 jaunty bugs (no change)
  • 0 hardy bugs (no change)

regression-release

  • 181 lucid bugs (up 4)
  • 37 karmic bugs (no change)
  • 18 jaunty bugs (no change)
  • 3 hardy bugs (no change)

regression-proposed

  • 7 lucid bugs (no change)
  • 1 karmic bug (no change)
    We are in the stage now where we are getting almost 90 bugs a week for Maverick

    JFo is continuing to work on removing the “regression-potential” tag from various processes.

Incoming Bugs: Bug day report

Due to much of the kernel team being in Taipei next week, the next bug day will be postponed to the following week.

Triage Status

The Kernel Triage Summit was a success. I am thankful to all of you who were able to make yourselves available for the sessions. Thanks to sconklin, diwic, apw and ogasawara for holding the sessions. I’ll be blogging about the event and making the transcripts and survey available to those who were unable to attend.

sconklin    Thanks JFO, I thought we got good participation   
JFo    any input you’d like to make on the Summit?   
JFo    sconklin, I did too   
JFo    I was well pleased   
apw    just that we should touch those people who attended and showed interest again   
JFo    I agree   
apw    to follow up with them, and get their feedback individually   
JFo    I’ll be going though the transcript to see who was involved and get back with them   
ogasawara    and we should follow up that the info dispersed lands in a wiki page somewhere   
JFo    yes   
apw    there was some very good audio info in there we must not lose ..   
JFo    I think that is the most important bit here   
JFo    apw, definitely agree   

Open Discussion or Questions: Raise your hand to be recognized

  • As we will be in Taipei next week, I’d like to see about doing the bug chat on Thursday or Friday.

kstailey    HPET + PAT = Oops (affects many systems) see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/563481/comments/34   
kstailey    please help test, thanks   
ogasawara    kstailey: which release?   
kstailey    > Jaunty   
kstailey    in the past PAT was not enabled   
ogasawara    kstailey: I assume there is a patch to fix it? and if so is it upstream?   
tgardner    about a month   
smb    not very long   
kstailey    Karmic and Lucid   
kstailey    “>” as in “greater than   
kstailey    as in when PAT code was thrust upon the world   
apw    yeah finally twigged that about 2s too late, ignore me pls   
kstailey    go search on: ubunut nopat   
kstailey    to see the impact   
kstailey    er, ubuntu   
apw    if there is an upstream patch then could you send the patch on to kernel-team@ list, then it’ll get on the list for consideration   
kstailey    try https://patchwork.kernel.org/patch/120327/   
kstailey    no warrantees   
Brad Figg

Kernel Team Meeting Minutes

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20100907 Meeting Agenda

Release Metrics:

Release Meeting Bugs (6 bugs, 9 Blueprints)

Release Milestoned Bugs (79 across all packages)

  • 1 linux kernel bugs (no change)
  • 1 linux-fsl-imx51 bugs (up 1)
  • 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 (202 across all packages (up 60))

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

Milestoned Features

  • 13 blueprints (Including HWE Blueprints)

Bugs with Patches Attached:117 (down 1)

Blueprint: kernel-maverick-bug-handling

Summit schedule sent. Saturday is the Triage Summit.
More vague work ongoing with the Forum, hopefully more closed out this week, several items will be postponed out of necessity.

Blueprint: kernel-maverick-bios-test-automation

*Changes this week to fwts:

  • handle some inquiries from community
  • LP#627959 FADT fix thanks to AceLan + GAS+64 bit addr fixes
  • update fwts to 0.18.2 in maverick universe
  • start natty branch: CMOS, APCI dumps

Status: Maverick

We’ve uploaded a new Maverick kernel, 2.6.35-20.29. Please test.

Kernel Freeze is Thurs Sept 16th, ie ~1 week away. After Kernel Freeze, we transition to our SRU policy. My target scenario however will be that we’ll have no changes to the kernel beyond kernel freeze. Also note that Maverick’s RC (Release Candidate) date is Sept 30. I suspect if any last minutes kernel changes do need to happen, an upload will need to occur approx 1 week before the Release Candidate to allow enough lead time for builds and assembly of candidate images.

We are again nearing being above the trend line for our overall burn down chart. We need to start closing out all remaining open work items. If your name appears in the following list, you have open work items. Please review if your work item(s) can be marked as DONE or POSTPONED, else get er done.
JFo, sconklin, cking, apw, diwic, tgardner, jjohansen, smb

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

A new lucid kernel went into proposed last week ~600 commits

Incoming Bugs: Regressions

448 Maverick Bugs (up 80)
997 Lucid Bugs (up 39)
Current regression stats (broken down by release):

regression-potential

  • 225 maverick bugs (up 47)
  • 166 lucid bugs (up 4: to be converted to regression-release)

regression-update

  • 49 lucid bugs (up 6)
  • 7 karmic bugs (no change)
  • 4 jaunty bugs (no change)
  • 0 hardy bugs (no change)

regression-release

  • 177 lucid bugs (up 10)
  • 37 karmic bugs (no change)
  • 18 jaunty bugs (no change)
  • 3 hardy bugs (no change)

regression-proposed

  • 7 lucid bugs (up 3)
  • 1 karmic bug (no change)

Incoming Bugs: Bug day report

Last weeks bug day was marginally successful due to my e-mail issuhttp://voices.canonical.com/kernelteam/?p=6096es.
I’d like to have next weeks bug day be on the same bugs, those in the Triaged state.
I’ll be sending out the Bug Day mail later this week.
We will continue to have the Team Bug Day to address the Top 50 list as half days on Friday and Monday.
Reviewers, please take a look at your needs-review lists and help us keep the process moving.
Please also take ownership of your bugs as you work them so we can get them fixed or otherwise off the list.
There are several subsystems owned by all that need to be reviewed for inclusion in our top 50 list.
sigh, that first line is all messed up

Triage Status

Kernel Triage Summit is on Saturday. Blog posts have gone up (http://voices.canonical.com/kernelteam/?p=6096)
The schedule is on the Fridge Calendar and on the Summit page itself (https://wiki.ubuntu.com/Kernel/BugTriage/Summit/Maverick).
I’ll continue microblogging and getting others to as well so that it can be as successful and well-attended as possible.

Open Discussion or Questions

JFo    Had a meeting today with several QA members and triagers concerning regression bugs.
JFo    The Kernel accounts for over 60 percent of the total number of these bug tags.
JFo    We discussed ways to reduce these numbers and I will likely be hosting a talk on this UDS.
JFo    There was also mention of the regression-potential tag and its use or lack thereof.
JFo    The general consensus was that it is not useful to anyone. I am interested in your thoughts on this.
JFo    ogasawara, any preference on if the regression-potential tag goes away?
bjf    i think we should apply some arsenal directly targeting regression bugs
ogasawara    I personally don’t leverage the regression-potential tagged bugs as they take a back seat to the regression-released bugs
JFo    additionally there is talk of changing the regression tags as well
JFo    bjf, I agree
JFo    ogasawara, neither do I
tgardner    regression-potential sounds like a bug that hasn’t been triaged.
JFo    it isn’t a terribly useful tag to me
JFo    tgardner, that is the thinking here as well
ogasawara    JFo: so I’m not opposed to that tag going away
JFo    I think, and I told them, that this can go away with almost no impact to us
JFo    ogasawara, cool, thanks :)
JFo    I figured you would be one of the only people to have an opinion on it :)
JFo    we should really take a look at the possibility that abogani fails to provide an -rt kernel
JFo    do we have anything that we could provide?
JFo    in the way of -preempt or -lowlatency?
JFo    I remember our talk tgardner about the duplication of effort
JFo    but the ubuntustudio folks are asking me about it often
JFo    among others
tgardner    which is why -preempt went back into the -rt kernel.
JFo    ok
tgardner    the folks that should be sponsoring abogani haven’t stepped up to the plate
JFo    so if he doesn’t release an -rt then there won’t be anything?
JFo    I see
Jeremy Foshee

First Kernel Triage Summit

On Saturday September 11th the Kernel Team will take the first in what I hope to be a series of steps toward educating ourselves and our community in the triage of the thousands of bugs that pass our way daily.


My goal for this event is to begin the process of training those interested in helping with kernel bugs in the way we process our bug tickets. This first event is meant to help us both educate and document. The information on the first ever Triage Summit is located on the wiki here.


As with everything we do, your feedback is appreciated. Please don’t hesitate to send us e-mail to the team list at kernel-team@lists.ubuntu.com or even on the wiki page itself. Your feedback will go a long way toward our plans for future events like this.


The schedule for Saturday is as follows:


1) at 1400 UTC we will hold a General session centered around providing information as to where to locate us, who our upstreams are and where to find them as well as the new subsystem breakdown of bugs to help us gather related issues more easily and get them in front of the right people.


2) at 1500 UTC there will be a session on Graphics and all of its related bits and bytes. There will be a focus on basic, effective triage for this subset as well as locations to find troubleshooting information and further reading on Graphics issues


3) at 1600 UTC there will be a session on audio bugs and the related subsystem parts involved there. This session will also have a basic troubleshooting and location portion so as to guide those interested in triaging audio bugs with further information.


4) at 1700 UTC we will have something of a lightning round in which we briefly discuss the USB/Firewire and Bluetooth stacks as well as helpful debugging and triage steps for this subset of bugs


As stated before, your feedback on these sessions as well as the documentation that will be provided will be most helpful to us. You are also welcome to approach us for other avenues of support. We are always looking for more help on a variety of kernel related areas such as documentation, bugs and spelling/grammar applications :-) so please don’t hesitate to ask how you can help.


I look forward to seeing a great many of you at the Summit on Saturday!


~JFo