linux: 4.8.0-31.33 -proposed tracker

Bug #1648034 reported by Luis Henriques
This bug report is a duplicate of:  Bug #1649358: linux: 4.8.0-32.34 -proposed tracker. Edit Remove
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
In Progress
Medium
Unassigned
Automated-testing
Fix Released
Medium
Canonical Kernel Team
Certification-testing
In Progress
Medium
Taihsiang Ho
Prepare-package
Fix Released
Medium
Luis Henriques
Prepare-package-meta
Fix Released
Medium
Luis Henriques
Prepare-package-signed
Fix Released
Medium
Luis Henriques
Promote-to-proposed
Fix Released
Medium
Steve Langasek
Promote-to-security
New
Medium
Ubuntu Stable Release Updates Team
Promote-to-updates
New
Medium
Ubuntu Stable Release Updates Team
Regression-testing
Confirmed
Medium
Canonical Kernel Team
Security-signoff
In Progress
Medium
Steve Beattie
Upload-to-ppa
Invalid
Medium
Unassigned
Verification-testing
Confirmed
Medium
Canonical Kernel Team
linux (Ubuntu)
Invalid
Undecided
Unassigned
Yakkety
Fix Released
Medium
Unassigned

Bug Description

This bug is for tracking the 4.8.0-31.33 upload package. This bug will contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

-- swm properties --
boot-testing-requested: true
derivative-trackers-created: true
phase: Promoted to proposed
proposed-announcement-sent: true
proposed-testing-requested: true

Luis Henriques (henrix)
tags: added: kernel-release-tracking-bug
tags: added: block-proposed
tags: added: block-proposed-yakkety
tags: added: yakkety
Changed in linux (Ubuntu Yakkety):
status: New → Confirmed
Changed in kernel-sru-workflow:
status: New → In Progress
importance: Undecided → Medium
Changed in linux (Ubuntu):
status: New → Invalid
Changed in linux (Ubuntu Yakkety):
importance: Undecided → Medium
Revision history for this message
Brad Figg (brad-figg) wrote : Packages available

Backport packages from packages here can be worked on, the following tracking bugs were opened for them:
linux-hwe-edge (16.04.1) - bug 1648038

description: updated
description: updated
Brad Figg (brad-figg)
description: updated
description: updated
Brad Figg (brad-figg)
description: updated
description: updated
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp4 (s390x.LPAR) - tests ran: 1, failed: 0
description: updated
description: updated
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : kernel02 (s390x.zVM) - tests ran: 1, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : modoc (ppc64el) - tests ran: 1, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 0
description: updated
description: updated
Revision history for this message
Brad Figg (brad-figg) wrote : onza (amd64) - tests ran: 1, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : modoc (ppc64el) - tests ran: 1, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 18, failed: 2
Revision history for this message
Brad Figg (brad-figg) wrote : onza (i386) - tests ran: 1, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 10, failed: 2
Revision history for this message
Taihsiang Ho (tai271828) wrote :

Hardware Certification have begun testing this -proposed kernel.

Revision history for this message
Brad Figg (brad-figg) wrote : modoc (ppc64el) - tests ran: 18, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : ms10-34-mcdivittB0-kernel (arm64) - tests ran: 33, failed: 11
Revision history for this message
Brad Figg (brad-figg) wrote : modoc (ppc64el) - tests ran: 10, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : ms10-34-mcdivittB0-kernel (arm64) - tests ran: 141, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : onza (amd64) - tests ran: 36, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : dwalin (amd64) - tests ran: 7, failed: 4
Revision history for this message
Brad Figg (brad-figg) wrote : ms10-34-mcdivittB0-kernel (arm64) - tests ran: 64, failed: 2
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 5, failed: 3
Revision history for this message
Brad Figg (brad-figg) wrote : onibi (amd64) - tests ran: 7, failed: 4
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 33, failed: 2
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 16, failed: 4
Revision history for this message
Brad Figg (brad-figg) wrote : onza (i386) - tests ran: 23, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 141, failed: 28
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 2, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 64, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : dwalin (amd64) - tests ran: 36, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : modoc (ppc64el) - tests ran: 36, failed: 4
Revision history for this message
Brad Figg (brad-figg) wrote : onza (amd64) - tests ran: 19, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : modoc (ppc64el) - tests ran: 16, failed: 3
Revision history for this message
Brad Figg (brad-figg) wrote : modoc (ppc64el) - tests ran: 141, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : modoc (ppc64el) - tests ran: 2, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : onibi (i386) - tests ran: 5, failed: 2
Revision history for this message
Brad Figg (brad-figg) wrote : onibi (amd64) - tests ran: 33, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : onibi (i386) - tests ran: 20, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 10, failed: 3
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 5, failed: 3
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 33, failed: 2
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 16, failed: 5
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 141, failed: 28
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 2, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 64, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 1, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp4 (s390x.LPAR) - tests ran: 1, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 10, failed: 2
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp4 (s390x.LPAR) - tests ran: 10, failed: 2
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp4 (s390x.LPAR) - tests ran: 18, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : kernel02 (s390x.zVM) - tests ran: 141, failed: 28
Revision history for this message
Brad Figg (brad-figg) wrote : kernel02 (s390x.zVM) - tests ran: 2, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : kernel02 (s390x.zVM) - tests ran: 64, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : onibi (i386) - tests ran: 5, failed: 2
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp4 (s390x.LPAR) - tests ran: 5, failed: 3
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp4 (s390x.LPAR) - tests ran: 16, failed: 4
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp4 (s390x.LPAR) - tests ran: 141, failed: 28
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp4 (s390x.LPAR) - tests ran: 2, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp4 (s390x.LPAR) - tests ran: 64, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp4 (s390x.LPAR) - tests ran: 33, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : s2lp6g002 (s390x.zKVM) - tests ran: 18, failed: 2
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (25.5 KiB)

This bug was fixed in the package linux - 4.8.0-32.34

---------------
linux (4.8.0-32.34) yakkety; urgency=low

  [ Thadeu Lima de Souza Cascardo ]

  * Release Tracking Bug
    - LP: #1649358

  * Vulnerability picked up from 4.8.10 stable kernel (LP: #1648662)
    - net: handle no dst on skb in icmp6_send

linux (4.8.0-31.33) yakkety; urgency=low

  [ Luis Henriques ]

  * Release Tracking Bug
    - LP: #1648034

  * Update hio driver to 2.1.0.28 (LP: #1646643)
    - SAUCE: hio: update to Huawei ES3000_V2 (2.1.0.28)

  * Yakkety update to v4.8.11 stable release (LP: #1645421)
    - x86/cpu/AMD: Fix cpu_llc_id for AMD Fam17h systems
    - KVM: x86: fix missed SRCU usage in kvm_lapic_set_vapic_addr
    - KVM: Disable irq while unregistering user notifier
    - arm64: KVM: pmu: Fix AArch32 cycle counter access
    - KVM: arm64: Fix the issues when guest PMCCFILTR is configured
    - ftrace: Ignore FTRACE_FL_DISABLED while walking dyn_ftrace records
    - ftrace: Add more checks for FTRACE_FL_DISABLED in processing ip records
    - genirq: Use irq type from irqdata instead of irqdesc
    - fuse: fix fuse_write_end() if zero bytes were copied
    - IB/rdmavt: rdmavt can handle non aligned page maps
    - IB/hfi1: Fix rnr_timer addition
    - mfd: intel-lpss: Do not put device in reset state on suspend
    - mfd: stmpe: Fix RESET regression on STMPE2401
    - can: bcm: fix warning in bcm_connect/proc_register
    - gpio: do not double-check direction on sleeping chips
    - ALSA: usb-audio: Fix use-after-free of usb_device at disconnect
    - ALSA: hda - add a new condition to check if it is thinkpad
    - ALSA: hda - Fix mic regression by ASRock mobo fixup
    - i2c: mux: fix up dependencies
    - i2c: i2c-mux-pca954x: fix deselect enabling for device-tree
    - Disable the __builtin_return_address() warning globally after all
    - kbuild: add -fno-PIE
    - scripts/has-stack-protector: add -fno-PIE
    - x86/kexec: add -fno-PIE
    - kbuild: Steal gcc's pie from the very beginning
    - ext4: sanity check the block and cluster size at mount time
    - ARM: dts: imx53-qsb: Fix regulator constraints
    - crypto: caam - do not register AES-XTS mode on LP units
    - powerpc/64: Fix setting of AIL in hypervisor mode
    - drm/amdgpu: Attach exclusive fence to prime exported bo's. (v5)
    - drm/i915: Refresh that status of MST capable connectors in ->detect()
    - drm/i915: Assume non-DP++ port if dvo_port is HDMI and there's no AUX ch
      specified in the VBT
    - virtio-net: drop legacy features in virtio 1 mode
    - clk: mmp: pxa910: fix return value check in pxa910_clk_init()
    - clk: mmp: pxa168: fix return value check in pxa168_clk_init()
    - clk: mmp: mmp2: fix return value check in mmp2_clk_init()
    - clk: imx: fix integer overflow in AV PLL round rate
    - rtc: omap: Fix selecting external osc
    - iwlwifi: pcie: fix SPLC structure parsing
    - iwlwifi: pcie: mark command queue lock with separate lockdep class
    - iwlwifi: mvm: fix netdetect starting/stopping for unified images
    - iwlwifi: mvm: fix d3_test with unified D0/D3 images
    - iwlwifi: mvm: wake the wait queue when the RX sync counter is zero
    - mfd: cor...

Changed in linux (Ubuntu Yakkety):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.