We have uploaded a new Precise linux kernel. Please note the ABI bump. The most notable changes are as follows:

* rebase to mainline v3.2-rc7

The full changelog can be seen at:

https://launchpad.net/ubuntu/+source/linux/3.2.0-7.13

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20111220 Meeting Agenda

ARM Status

P/omap4: a new kernel (3.2.0-1403.3) based off 3.2-rc5 (Ubuntu-3.2.0-4.10)
has been released.
SRU kernels: besides natty/omap4 and lucid/imx51 finally getting the
“large mmap()” fix, there’s nothing else to report.

Release Metrics and Incoming Bugs

Release metrics and incomming bug data can be reviewed at the following link:

http://people.canonical.com/~kernel/reports/kt-meeting.txt

Milestone Targeted Work Items

Status: Work Items
==================

If your name is in the above table, please review your Alpha-2 work
items. Note that Alpha-2 is Thurs Feb 2.

Blueprint: hardware-p-kernel-power-management

• Write eventstat to accurately monitor and log wakeup events
  git://kernel.ubuntu.com/cking/eventstat.git and

  https://launchpad.net/~colin-king/+archive/powermanagement

• HDD busy results:

  http://zinc.canonical.com/~cking/power-benchmarking/hdd-wakeups

• Wakeup Event results:

  http://zinc.canonical.com/~cking/power-benchmarking/events

• UEFI vs BIOS power management testing:

  http://zinc.canonical.com/~cking/power-benchmarking/legacy-bios-vs-uefi-firmware

Status: Precise Development Kernel

Status: Precise Development Kernel
==================================
We’ve recently uploaded the 3.2.0-5.11 and 3.2.0-6.12 Ubuntu kernels.
Notable changes in these uploads include rebasing to v3.2-rc6, setting
DEFAULT_MMAP_MIN_ADDR=32k on arm, adding overlayfs and veth to -virtual,
and misc config updates. Please test and let us know your results.
Important Upcoming Dates:

• Thurs Feb 2 – Alpha 2 (~7 weeks)

Status: CVE’s

Currently open CVEs for each supported branch:

We have had a five new CVEs this week. Two have been resolved via
upstream stable. The remainder do not yet have any upstream fixes.
We continue to have one CVE with fix outstanding.

Status: Stable, Security, and Bugfix Kernel Updates – Oneiric/Natty/Maverick/Lucid/Hardy

No update this week.

Open Discussion or Questions? Raise your hand to be recognized

A question of when is the next meeting?
The next meeting will be January 3rd.
As that misses one week, that should be announced probabally, as in cancelling the 27th
I’ll send out a notice. Unless folks think we should still have a meeting on the 27th?
No, thats great, cancel it
Any other open comments?
Great, have a safe and happy holidays everyone!

We have uploaded a new Precise linux kernel. Please note the ABI bump.
The most notable changes are as follows:

  * rebase to mainline v3.2-rc6

The full changelog can be seen at:

https://launchpad.net/ubuntu/+source/linux/3.2.0-6.12

We have uploaded a new Precise linux-ti-omap4 kernel. Please note the ABI bump.
The most notable changes are as follows:

  * rebased to Ubuntu-3.2.0-4.10

The full changelog can be seen at:

https://launchpad.net/ubuntu/+source/linux-ti-omap4/3.2.0-1403.3

We have uploaded a new Precise linux kernel. Please note the ABI bump. The most notable changes are as follows:

* DEFAULT_MMAP_MIN_ADDR=32k on arm
* Enable CONFIG_LOCKUP_DETECTOR=y
* Add overlayfs and veth to virtual inclusion list
* Resolve WARNING: at drivers/block/floppy.c:2929 do_fd_request
* Rebase to upstream 55b02d2f
* Misc config updates

The full changelog can be seen at:

https://launchpad.net/ubuntu/+source/linux/3.2.0-5.11

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.

Agenda

20111213 Meeting Agenda

ARM Status

P/omap4: a new kernel (3.2.0-1402.2) based off 3.2 (Ubuntu-3.2.0-3.9) has been released, while a new TI BSP + 3.2-rc5 is in the pipe.
SRU kernels: nothing to report.

Release Metrics and Incoming Bugs

Just adding link this week, instead of posting all data.

http://people.canonical.com/~kernel/reports/kt-meeting.txt

Milestone Targeted Work Items

If your name is in the above table, please review your Alpha-2 work items. Note that Alpha-2 is Thurs Feb 2.

Blueprint: hardware-p-kernel-power-management

Power Management:

• Re-run power.d readahead and journal-commit tests on non-idle
  user application scenerios.
• Measure mouse power consumption, different rates + devices:

  http://zinc.canonical.com/~cking/power-benchmarking/mouse-movement

• Complete PowerTop good/bad results:

  http://zinc.canonical.com/~cking/power-benchmarking/powertop-good-bad-recommendations

• Measure backlight levels power traits:

  http://zinc.canonical.com/~cking/power-benchmarking/backlight-non-linearity

• More extensive 32 vs 64 bit power comparisons (in progress)
• Compare UEFI vs BIOS firmware (in progress)
• Complete pm-utils measurements:

  http://zinc.canonical.com/~cking/power-benchmarking/pm-utils-results

• Crowd-sourcing pm-utils extra tweaks, CALL FOR TESTING:

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

Status: Precise Development Kernel

We have uploaded the 3.2.0-4.10 Ubuntu kernel which is based on latest upstream v3.2-rc5 kernel. Additionally, after yesterday’s Tech Board discussion around the i386 non-pae flavor, it was decided to continue carrying this flavor for 12.04 and then drop it in 12.10. The installer will also be switched to default to the pae flavor for i386.

Important Upcoming Dates:

• Thurs Feb 2 – Alpha 2 (~7 weeks)

Status: CVE’s

CVE-2010-4251 CVE-2010-4805 CVE-2011-1082 CVE-2011-1083: epoll DOS — fix incomplete, referred back to Security for review
CVE-2011-1747: agp ioctl memory DOS — no upstream fix as yet
CVE-2011-3347: be2net non-member vlan DOS — cannot identify upstream fix
CVE-2011-3638: ext4 extent split — upstream fix identified, pending application
CVE-2011-4112: pktgen bridge panic — redhat is withdrawing the CVE
CVE-2011-4131: nfs4 ACL oops — fix is still iterating upstream, pending
CVE-2011-4347: kvm kvm_vm_ioctl_assign_device crashes — no upsteam fix as yet

=== CVE Metrics ===

Currently open CVEs for each supported branch:

We only have one open CVE with an upstream fix currently. The remainder await fixes from upstream.

(bah, will drop the CVE- prefix for future updates.) ..

Status: Stable, Security, and Bugfix Kernel Updates – Oneiric/Natty/Maverick/Lucid/Hardy

Many of the kernels in -proposed were quickly verified and went into
regression testing early. This week is mostly about finishing up the
stragglers. A new Oneiric has been prep’d and uploaded. We’ll just have
to see if we can get it verified and regression tested before the
dead week of Christmas.

Here is the status for the main kernels, until today (13/12):

• Hardy – 2.6.24-30.97
  • On holiday

• Lucid – 2.6.32-36.79
  • Regression testing in progress.

• Maverick – 2.6.35-31.63
  • On holiday

• Natty – 2.6.38-13.53
  • Regression testing in progress.

• Oneiric – 3.0.0-14.23
  • Prep’d and trying to reach -proposed

    Current opened tracking bugs details:

• http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html

  For SRUs, SRU report is a good source of information:

• http://people.canonical.com/~kernel/reports/sru-report.html

  Future stable cadence cycles:

• https://wiki.ubuntu.com/PrecisePangolin/ReleaseInterlock

Hardware Certification – Testing Pools

hi
let me do this gradually As part of the SRU workflow the hardware certification team tests the -proposed kernel on as many certified systems as possible. As the number of certified systems for each release has grown, getting full coverage has become more and more difficult. To allow us to reduce the number of systems tested we have devised a system of ‘testing pools’. This takes advantage of a system which stores details of the certified hardware including it constituent components to provide as broad a component coverage as possible.

Initially the system ensured that at least one instance of each piece of hardware (as identified by PCI Id’s) was present in the testing pool. This turned out not to fulfill the goal of the system since we still ended up with needing almost all the systems we had to provide full coverage (e.g. 165 systems certified for Natty gave a testing pool of 158)

We made a first effort at reducing the size of the pools by considering only components of particular categories to be ‘important’. A list of these was sent to the kernel-team mailing list.

https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AphFraZYTghddElqTHl3NmZsWXVDYkMxcE5zX3EtR0E&hl=en_US#gid=0

These give us testing pools of ~50 systems. However we are not happy yet with the coverage. We need feedback on which components need to be added in. The criteria used should be: how likely is it that a bug could occur in just a subset of the components of this category? A good example is the category ‘Display Controller/VGA Compatible Controller’ which we do cover already. We know for a fact that bugs will be specific to particular makes of graphics card. Same for CPUs (‘Processor’ category)

We really need feedback on this
…

brendand, This will all be documented in the meeting minutes. It would be good if you could also follow up with an email to the kernel-team mailing list.

Open Discussion or Questions? Raise your hand to be recognized

brendand: Do you have a revised list which has all the possible components you want us to review to consider adding back in? Also, what # are you looking for to satify coverage? ogasawara – if you can access that link then all the ones marked ‘x’ are not considered at the moment

we have no fixed number to reach

brendand, what is the max number of machines that you can cover ?

tgardner – it seems to be about 90, realistically speaking. something like that.
ack

i would prefer for now to take each component category on it’s own merits’ rather than considering how many extra systems it adds. we (the hwcert team) can worry about managing that

i had a question to pose, as a bit of a thought experiment

Could a bug affect only a subset of device of the category ‘Bridge/PCI bridge’?

brendand, likely, but its more likely to be BIOS specific
if there is more than one different piece of h/w in any category it is possible to get different results from each however, we have way fewer problems with PCI bridges.

apw – yes, definitely *possible*.
actually the point of that question was to illustrate the line of thinking that needs to be taken to evaluate this list of component categories between tgardner and apw that’s the kind of critique of the list i’m looking for
thanks
Any Open Discussion comments?

one last thing. i’m not sure is that link public. anyone who can’t get access please let me know and i’ll sort something out

If no other comments, then going once

brendand: how do you want feedback, maybe a “feedback” column, and we’ll add X’s to categories we think should be added back?

ogasawara – i’m arranging for everyone to have edit rights and i’ll add a feedback column

brendand: let us know when it’s ready for editing. I’m sure a few of us can just a quick pass off and tick the ones we want.
brendand, any other comments?

yeah, if any of the categories don’t make sense to you, contact me about it
i’ll send the link to the kernel-team list

brendand, dot dot then ?

Any other open discussions or questions?

We have uploaded a new Precise linux kernel. Please note the ABI bump. The most notable changes are as follows:

* rebase to 3.2-rc5
* dmar: disable if ricoh multifunction detected
* dell-wmi: Demote unknown WMI event message to pr_debug

https://launchpad.net/ubuntu/+source/linux/3.2.0-4.10

We have uploaded a new Precise linux ti-omap4 kernel. The most notable
changes are as follows:

  * rebase to latest master release Ubuntu-3.2.0-3.9
  * temporary work around for hangs on reboot

The full changelog can be found at:

https://launchpad.net/ubuntu/+source/linux-ti-omap4/3.2.0-1402.2

We have uploaded a new Precise linux ti-omap4 kernel. The most notable
changes are as follows:

* update to a 3.2.0 mainline base

The full changelog can be found at:

https://launchpad.net/ubuntu/+source/linux-ti-omap4/3.2.0-1401.1

We have uploaded a new Precise linux kernel. The most notable changes are as follows:

* ext4: correct partial write discard size calculation
* pci: Rework ASPM disable code
* x86: Fix boot failures on older AMD CPU’s
* EHCI : Fix a regression in the ISO scheduler

The full changelog can be found at:

https://launchpad.net/ubuntu/+source/linux/3.2.0-3.9