linux: 4.9.0-15.16 -proposed tracker

It was not possible to create or handle the tracking bugs for the following packages (their tracking bugs based on this update must be handled manually):
linux-lts-zesty (16.04.1)

Please, do not send me this. It is impossible for me to unsubscribe !

On 20/01/2017 20:16, Brad Figg wrote:
> ** Changed in: kernel-development-workflow/prepare-package-signed
> Status: Confirmed => Fix Released
>
> ** Changed in: kernel-development-workflow/prepare-package-signed
> Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner (timg-tpi)
>
> ** Description changed:
>
> This bug is for tracking the 4.9.0-15.16 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
>
> - kernel-phase-changed:Friday, 20. January 2017 14:31 UTC
> - kernel-phase:Packaging
> -
> -- swm properties --
> derivative-trackers-created: true
> phase: Packaging
> + kernel-phase:Uploaded
> + kernel-phase-changed:Friday, 20. January 2017 19:16 UTC
>
> ** Description changed:
>
> This bug is for tracking the 4.9.0-15.16 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 --
> derivative-trackers-created: true
> - phase: Packaging
> - kernel-phase:Uploaded
> - kernel-phase-changed:Friday, 20. January 2017 19:16 UTC
> + phase: Uploaded
>

        tests ran: 18, failed: 16;
  http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-35-mcdivittB0-kernel__4.9.0-15.16__2017-01-26_07-10-00/results-index.html

        tests ran: 1, failed: 0;
  http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-35-mcdivittB0-kernel__4.9.0-15.16__2017-01-26_07-41-00/results-index.html

        tests ran: 10, failed: 2;
  http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-26_08-17-00/results-index.html

        tests ran: 11, failed: 2;
  http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-35-mcdivittB0-kernel__4.9.0-15.16__2017-01-26_08-06-00/results-index.html

        tests ran: 16, failed: 9;
  http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-35-mcdivittB0-kernel__4.9.0-15.16__2017-01-26_10-24-00/results-index.html

        tests ran: 2, failed: 0;
  http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-35-mcdivittB0-kernel__4.9.0-15.16__2017-01-26_11-24-00/results-index.html

        tests ran: 36, failed: 0;
  http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-26_12-31-00/results-index.html

        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-26_15-25-00/results-index.html

        tests ran: 64, failed: 2;
  http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-26_16-40-00/results-index.html

        tests ran: 1, failed: 0;
  http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-30_16-05-00/results-index.html

        tests ran: 18, failed: 0;
  http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-30_16-30-00/results-index.html

        tests ran: 10, failed: 2;
  http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-30_17-35-00/results-index.html

        tests ran: 11, failed: 2;
  http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-30_19-08-00/results-index.html

        tests ran: 36, failed: 22;
  http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-30_22-13-00/results-index.html

        tests ran: 16, failed: 4;
  http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-30_23-33-00/results-index.html

        tests ran: 141, failed: 0;
  http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-31_00-15-00/results-index.html

        tests ran: 2, failed: 0;
  http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-31_01-30-00/results-index.html

        tests ran: 64, failed: 2;
  http://kernel.ubuntu.com/testing/4.9.0-15.16-generic/ms10-34-mcdivittB0-kernel__4.9.0-15.16__2017-01-31_01-59-00/results-index.html

This bug was fixed in the package linux - 4.9.0-15.16

---------------
linux (4.9.0-15.16) zesty; urgency=low

  [ Tim Gardner ]

  * Release Tracking Bug
    - LP: #1658101

  * Zesty update to v4.9.5 stable release (LP: #1658099)
    - Input: xpad - use correct product id for x360w controllers
    - Input: i8042 - add Pegatron touchpad to noloop table
    - pinctrl: imx: fix imx_pinctrl_desc initialization
    - pinctrl: sh-pfc: r8a7795: Use lookup function for bias data
    - pinctrl: sh-pfc: Add helper to handle bias lookup table
    - regulator: tps65086: Fix 25mV ranges for BUCK regulators
    - regulator: axp20x: Fix axp809 ldo_io registration error on cold boot
    - drm/tegra: dpaux: Fix error handling
    - drm/vc4: Fix a couple error codes in vc4_cl_lookup_bos()
    - drm/savage: dereferencing an error pointer
    - selftests: do not require bash to run netsocktests testcase
    - selftests: do not require bash for the generated test
    - zram: revalidate disk under init_lock
    - zram: support BDI_CAP_STABLE_WRITES
    - dax: fix deadlock with DAX 4k holes
    - mm: pmd dirty emulation in page fault handler
    - mm: fix devm_memremap_pages crash, use mem_hotplug_{begin, done}
    - ocfs2: fix crash caused by stale lvb with fsdlm plugin
    - mm, memcg: fix the active list aging for lowmem requests when memcg is enabled
    - mm: support anonymous stable page
    - mm/slab.c: fix SLAB freelist randomization duplicate entries
    - mm/hugetlb.c: fix reservation race when freeing surplus pages
    - KVM: x86: fix emulation of "MOV SS, null selector"
    - KVM: eventfd: fix NULL deref irqbypass consumer
    - jump_labels: API for flushing deferred jump label updates
    - KVM: x86: flush pending lapic jump label updates on module unload
    - KVM: x86: fix NULL deref in vcpu_scan_ioapic
    - KVM: x86: add Align16 instruction flag
    - KVM: x86: add asm_safe wrapper
    - KVM: x86: emulate FXSAVE and FXRSTOR
    - KVM: x86: Introduce segmented_write_std
    - efi/libstub/arm*: Pass latest memory map to the kernel
    - efi/x86: Prune invalid memory map entries and fix boot regression
    - x86/efi: Don't allocate memmap through memblock after mm_init()
    - nl80211: fix sched scan netlink socket owner destruction
    - gpio: Move freeing of GPIO hogs before numbing of the device
    - xfs: Timely free truncated dirty pages
    - bridge: netfilter: Fix dropping packets that moving through bridge interface
    - x86/cpu/AMD: Clean up cpu_llc_id assignment per topology feature
    - x86/bugs: Separate AMD E400 erratum and C1E bug
    - x86/CPU/AMD: Fix Bulldozer topology
    - wusbcore: Fix one more crypto-on-the-stack bug
    - usb: musb: fix runtime PM in debugfs
    - USB: serial: kl5kusb105: fix line-state error handling
    - USB: serial: ch341: fix initial modem-control state
    - USB: serial: ch341: fix resume after reset
    - USB: serial: ch341: fix open error handling
    - USB: serial: ch341: fix control-message error handling
    - USB: serial: ch341: fix open and resume after B0
    - Input: elants_i2c - avoid divide by 0 errors on bad touchscreen data
    - i2c: print correct device invalid address
    - i2c: fix kern...