June 21st, 2011 by Meeting Minutes
IRC Log of the meeting.
Meeting minutes.
Agenda
ARM Status
Kernel development: nothing new to report.
Oneiric/ti-omap4: during the last TI call we got to know that _perhaps_ we will get a 3.0 kernel for the O cycle. Still not 100% sure and no ETA yet. Linaro already has a .39 kernel but it doesn’t boot on my panda (while it seems it works ok with a linaro hwpack if device tree is disabled).
Gcc 4.6 and omap usb: lp#791552 has been confirmed as a kernel upstream bug, thus until we get a proper fix and as long as we us gcc 4.6, we loose usb across all the omap* targets. So far all the proposed workarounds didn’t help.
Release Metrics and Incoming Bugs
oneiric nominated bugs
- 28 linux kernel bugs (up 8)
Ubuntu oneiric-alpha-2 bugs
- 3 linux kernel bugs (up 3)
oneiric-updates bugs
- 0 linux kernel bugs (no change 0)
natty-updates bugs
- 25 linux kernel bugs (no change 0)
maverick-updates bugs
- 3 linux kernel bugs (no change 0)
lucid-updates bugs
- 8 linux kernel bugs (no change 0)
hardy-updates bugs
- 0 linux kernel bugs (no change 0)
Incoming Bugs
- 23 oneiric bugs (up 4)
- 1326 natty bugs (up 14)
- 1129 maverick bugs (up 2)
- 1038 lucid bugs (up 1)
- 38 hardy bugs (no change 0)
Regressions
regression-update bugs
- 0 oneiric bugs (no change 0)
- 4 natty bugs (no change 0)
- 43 maverick bugs (up 1)
- 77 lucid bugs (up 2)
- 0 hardy bugs (no change 0)
regression-release bugs
- 0 oneiric bugs (no change 0)
- 450 natty bugs (down 3)
- 247 maverick bugs (down 1)
- 224 lucid bugs (no change 0)
- 2 hardy bugs (no change 0)
regression-proposed bugs
- 0 oneiric bugs (no change 0)
- 2 natty bugs (no change 0)
- 2 maverick bugs (no change 0)
- 0 lucid bugs (no change 0)
- 0 hardy bugs (no change 0)
Blueprints: Oneiric Delta Review
apw, lag, manjo, ralveti, rtg: you have work items to review your set of Ubuntu patches which I’ve postponed to Alpha-2 for you. Please take a moment to review when you have a chance. See https://wiki.ubuntu.com/KernelTeam/Specs/KernelOneiricUbuntuDeltaReview for your specific set of patches.
Blueprints: Oneiric Server Requirements
Was able to get some domUs started with Oneiric as dom0. Some strange problem to follow-up on when having xenconsole and console on a serial line. Also need to file a bug to get blkback and netback loaded when the system gets started as dom0. Otherwise there is a strange effect when starting the domUs.
Status: General Oneiric
We uploaded the 3.0-1.2 Ubuntu kernel last week. This was rebased on the upstream v3.0-rc3 release. Alpha-2 is also approaching, ie Thurs June 30. That means we’ll likely upload our final Alpha-2 kernel this Friday June 24th. If there are any patches that need to land in Alpha-2, get them sent to the kernel-team mailing list asap.
Status: Stable Kernel Team
Kernel SRU tracking page
-
http://people.canonical.com/~kernel/reports/sru-report.html
Current status
Hardy
- released
Lucid
- Verification complete but a regression is suspected
- Regression bug: http://launchpad.net/bugs/791512
- Kernel will not be released until this is resolved
- QA testing is in progress
- Security Signoff is in progress
Maverick
- Verification complete
- Awaiting QA testing or signoff
- Security Signoff is in progress
Natty
- Regressions have been detected in -proposed We are waiting for feedback from the reporters and can’t proceed until the regressions are resolved.
-
Tracking bug:
-
http://launchpad.net/bugs/792013
-
-
Regression bugs:
-
https://bugs.launchpad.net/bugs/794096
-
https://bugs.launchpad.net/bugs/793796
-
Security & bugfix kernels – Maverick/Lucid/Hardy
| Current Kernel versions are always available here: http://people.canonical.com/~kernel/reports/versions.html | |||||||||
| Package | Upd/Sec | Proposed | TiP | Verified | |||||
| lucid linux-meta-lts-backport-natty | 2.6.38.10.20 | 0 | 0 | ||||||
| — linux-ec2 | 2.6.32-316.31 | 2.6.32-317.34 | 3 | 3 | |||||
| — linux-lts-backport-natty | 2.6.38-10.44~lucid1 | 1 | 1 | ||||||
| — linux-meta-mvl-dove | 2.6.32.216.18 | 2.6.32.217.19 | 0 | 0 | |||||
| — linux-ports-meta | 2.6.32.32.24 | 2.6.32.33.25 | 0 | 0 | |||||
| — linux-mvl-dove | 2.6.32-216.33 | 2.6.32-217.34 | 8 | 8 | |||||
| — linux-meta-lts-backport-maverick | 2.6.35.25.36 | 2.6.35.30.38 | 0 | 0 | |||||
| — linux-lts-backport-maverick | 2.6.35-25.44~lucid1 | 2.6.35-30.54~lucid1 | 21 | 21 | |||||
| — linux-meta | 2.6.32.32.38 | 2.6.32.33.39 | 0 | 0 | |||||
| — linux-firmware | 1.34.7 | 1.34.10 | 0 | 0 | |||||
| — linux | 2.6.32-32.62 | 2.6.32-33.68 | 3 | 3 | |||||
| — linux-fsl-imx51 | 2.6.31-608.25 | 2.6.31-609.26 | 0 | 0 | |||||
| — linux-meta-fsl-imx51 | 2.6.31.608.9 | 2.6.31.609.10 | 0 | 0 | |||||
| — linux-backports-modules-2.6.32 | 2.6.32-32.32 | 2.6.32-33.33 | 0 | 0 | |||||
| — linux-meta-ec2 | 2.6.32.316.17 | 2.6.32.317.18 | 0 | 0 | |||||
| maverick linux-ports-meta | 2.6.35.28.21 | 2.6.35.30.23 | 0 | 0 | |||||
| — linux-mvl-dove | 2.6.32-416.33 | 2.6.32-417.34 | 6 | 6 | |||||
| — linux-meta-mvl-dove | 2.6.32.416.6 | 2.6.32.417.7 | 0 | 0 | |||||
| — linux-firmware | 1.38.6 | 1.38.8 | 1 | 0 | |||||
| — linux | 2.6.35-28.50 | 2.6.35-30.54 | 14 | 14 | |||||
| — linux-backports-modules-2.6.35 | 2.6.35-28.20 | 2.6.35-30.22 | 0 | 0 | |||||
| — linux-meta | 2.6.35.28.36 | 2.6.35.30.38 | 0 | 0 | |||||
| natty linux-meta-ti-omap4 | 2.6.38.1209.7 | 0 | 0 | ||||||
| — linux-backports-modules-2.6.38 | 2.6.38-10.6 | 0 | 0 | ||||||
| — linux-firmware | 1.52.1 | 0 | 0 | ||||||
| — linux | 2.6.38-10.44 | 15 | 15 | ||||||
| — linux-ti-omap4 | 2.6.38-1209.13 | 10 | 10 | ||||||
| — linux-meta | 2.6.38.10.25 | 0 | 0 | ||||||
Open Discussion or Questions
ogasawara:
-
bjf, the links you post at the start of the meeting still reference Natty, should be Oneiric
- Noted and fixed.
-
The bug stats we post each meeting, are those useful to anyone other than myself? Would it suffice to just post the link to the stats?
sconkline: -
I have the same question about kernel versions in the meeting – is posting th elink just as useful?
- The elink is more appropriate in that case
Pages