17:00 <jsalisbury> #startmeeting
17:00 <meetingology> Meeting started Tue Jun 18 17:00:04 2013 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
17:00 <meetingology> 
17:00 <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
17:00 <jsalisbury> ##
17:00 <jsalisbury> ## This is the Ubuntu Kernel Team weekly status meeting.
17:00 <jsalisbury> ##
17:00 <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
17:00 <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Saucy
17:00 <jsalisbury> # Meeting Etiquette
17:00 <jsalisbury> #
17:00 <jsalisbury> # NOTE: '..' indicates that you are finished with your input.
17:00 <jsalisbury> #       'o/' indicates you have something to add (please wait until you are recognized)
17:00 <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
17:00 <sconklin> o/
17:00 <henrix> o/
17:00 <ppisati> o/
17:00 <cking> \o
17:00 <sforshee> o/
17:00 <ogasawara> o/
17:00 <smb> \o
17:00 <rtg_> o/
17:00 <apw> o/
17:01 <bjf> o/
17:01 <kamal> o/
17:01 <jsalisbury> [TOPIC] ARM Status (ppisati)
17:01 <ppisati> Q/master: lp1176977 ("XFS instability on armhf under load") - passed all xfs
17:01 <ppisati> tests (tested both on arm and x86), but there's still one patch missing (and
17:01 <ppisati> waiting to enter linux-next for 3.11).
17:01 <ppisati> */highbank: lp1182637("cpu_offlining fails to run on ARM") - indeed, it was a
17:01 <ppisati> firmware issue: updating the node to the last available firmware, made cpu
17:01 <ppisati> hotplugging work - lp1185669 ("CPU cores offline and can't be brought back up on
17:01 <ppisati> ARM Server card") is probably a dup.
17:01 <ppisati> R/master: lp1171582("hvc0 getty causes random hangs"), seems like i can detect
17:01 <ppisati> the presence of a jtag console (DBGAUTHSTATUS NSNE bit) and thus attach or not
17:01 <ppisati> the xen console to it, i'll give it a try.
17:01 <ppisati> ..
17:01 <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
17:02 <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
17:02 <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
17:02 <jsalisbury> ..
17:02 <jsalisbury> [TOPIC] Milestone Targeted Work Items (ogasawara)
17:02 <ogasawara> [LINK] https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork
17:02 <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-s/canonical-kernel-distro-team.html
17:02 <ogasawara> || apw       || client-1303-power-consumption-testing || 1 work item ||
17:02 <ogasawara> ||           || foundations-1305-arm64-bringup        || 1 work item ||
17:02 <ogasawara> || ogasawara || foundations-1305-kernel               || 1 work item ||
17:02 <ogasawara> ||           || mobile-power-management               || 1 work item ||
17:02 <ogasawara> || sforshee  || foundations-1303-phablet-kernel-maintenance || 1 work item ||
17:02 <ogasawara> || smb       || servercloud-s-virtstack               || 1 work item  ||
17:02 <ogasawara> ..
17:02 <jsalisbury> [TOPIC] Status: Saucy Development Kernel (ogasawara)
17:02 <ogasawara> Our Saucy unstable branch has been rebased to the latest v3.10-rc6
17:02 <ogasawara> upstream kernel.  We unfortunately have still not uploaded yet.  We are
17:02 <ogasawara> still awaiting fixups for a few DKMS packages.  We hope to upload by EOW
17:02 <ogasawara> or early next week.  In the mean time we have gone ahead and rebased our
17:02 <ogasawara> Saucy master branch to the recent v3.9.6 upstream stable kernel and
17:02 <ogasawara> uploaded.
17:02 <ogasawara> For our phablet kernels we have been investigating some kernel size
17:02 <ogasawara> constraints and the modules which we have enabled and built in.
17:02 <ogasawara> Important upcoming dates:
17:02 <ogasawara> Thurs June 27 - Alpha 1 (opt in)
17:02 <ogasawara> ..
17:03 <jsalisbury> [TOPIC] Status: CVE's (sconklin)
17:03 <sconklin> == 2013-06-18 (7 days) ==
17:03 <sconklin> Currently we have 62 CVEs on our radar, with 3 CVEs added and 2 CVEs retired in the last week.
17:03 <sconklin> See the CVE matrix for the current list:
17:03 <sconklin> [LINK] http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
17:03 <sconklin> Overall the backlog has increased slightly this week:
17:03 <sconklin> [LINK] http://people.canonical.com/~kernel/status/cve-metrics.txt
17:03 <sconklin> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
17:03 <sconklin> ..
17:03 <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Raring/Quantal/Precise/Lucid/Hardy (bjf/henrix/sconklin)
17:03 <sconklin> Status for the main kernels, until today (Jun. 18):
17:03 <sconklin> *   Lucid - Beginning prep;
17:03 <sconklin> * Precise - Beginning prep;
17:03 <sconklin> * Quantal - Beginning prep;
17:03 <sconklin> * Raring  - Beginning prep;
17:03 <sconklin> Current opened tracking bugs details:
17:03 <sconklin> * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
17:04 <sconklin> For SRUs, SRU report is a good source of information:
17:04 <sconklin> * http://people.canonical.com/~kernel/reports/sru-report.html
17:04 <sconklin> Future stable cadence cycles:
17:04 <sconklin> * https://wiki.ubuntu.com/RaringRingtail/ReleaseInterlock
17:04 <sconklin> ..
17:04 <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
17:04 <jsalisbury> Thanks everyone
17:04 <jsalisbury> #endmeeting