linux: 3.13.0-45.74 -proposed tracker

Bug #1410384 reported by Seth Forshee
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Kernel SRU Workflow
Fix Released
Medium
Unassigned
Automated-testing
Fix Released
Medium
Canonical Kernel Team
Certification-testing
Fix Released
Medium
Taihsiang Ho
Prepare-package
Fix Released
Medium
Seth Forshee
Prepare-package-meta
Fix Released
Medium
Seth Forshee
Prepare-package-signed
Fix Released
Medium
Seth Forshee
Promote-to-proposed
Fix Released
Medium
Chris J Arges
Promote-to-security
Invalid
Medium
Ubuntu Stable Release Updates Team
Promote-to-updates
Fix Released
Medium
Adam Conrad
Regression-testing
Fix Released
Medium
Canonical Platform QA Team
Security-signoff
Invalid
Medium
John Johansen
Verification-testing
Fix Released
Medium
Canonical Kernel Team
linux (Ubuntu)
Invalid
Undecided
Unassigned
Trusty
Fix Released
Undecided
Unassigned

Bug Description

This bug is for tracking the 3.13.0-45.74 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-stable-Prepare-package-start:Tuesday, 13. January 2015 17:34 UTC
kernel-stable-Prepare-package-end:Wednesday, 14. January 2015 02:05 UTC
kernel-stable-Promote-to-proposed-start:Wednesday, 14. January 2015 02:05 UTC
ppa-package-testing-start:Wednesday, 14. January 2015 02:05 UTC
kernel-stable-Promote-to-proposed-end:Friday, 16. January 2015 17:48 UTC
kernel-stable-Verification-testing-start:Friday, 16. January 2015 19:01 UTC
kernel-stable-Certification-testing-start:Friday, 16. January 2015 19:02 UTC
kernel-stable-Security-signoff-start:Friday, 16. January 2015 19:02 UTC
kernel-stable-Regression-testing-start:Friday, 16. January 2015 19:02 UTC
kernel-stable-Verification-testing-end:Monday, 26. January 2015 19:35 UTC
kernel-stable-Regression-testing-end:Monday, 26. January 2015 19:35 UTC
kernel-stable-Certification-testing-end:Tuesday, 27. January 2015 07:01 UTC
kernel-stable-Promote-to-updates-start:Wednesday, 28. January 2015 16:01 UTC
kernel-stable-Security-signoff-end:Wednesday, 28. January 2015 16:01 UTC
kernel-stable-Promote-to-updates-end:Friday, 30. January 2015 16:01 UTC
kernel-stable-phase:Released
kernel-stable-phase-changed:Friday, 30. January 2015 17:03 UTC

Seth Forshee (sforshee)
tags: added: kernel-release-tracking-bug
tags: added: trusty
Changed in kernel-sru-workflow:
status: New → In Progress
importance: Undecided → Medium
Changed in linux (Ubuntu):
status: New → Invalid
Revision history for this message
Brad Figg (brad-figg) wrote : Packages available

All builds are complete, packages in this bug can be copied to -proposed.

Derivative packages from packages here can be worked on, the following tracking bugs were opened for them:
linux-keystone - bug 1410600

Backport packages from packages here can be worked on, the following tracking bugs were opened for them:
linux-lts-trusty (precise1) - bug 1410601

description: updated
Revision history for this message
Chris J Arges (arges) wrote :

Promoted to proposed:
 linux | 3.13.0-45.74 | trusty-proposed | source
 linux-meta | 3.13.0.45.52 | trusty-proposed | source
 linux-signed | 3.13.0-45.74 | trusty-proposed | source

Brad Figg (brad-figg)
description: updated
Brad Figg (brad-figg)
description: updated
Brad Figg (brad-figg)
tags: added: qa-testing-passed
Brad Figg (brad-figg)
description: updated
Revision history for this message
Taihsiang Ho (tai271828) wrote :

The Hardware Certification team have completed testing this -proposed kernel. No regressions were observed.
The report is available at:
http://people.canonical.com/~hwcert/sru-testing/trusty/3.13.0-45.74/trusty-proposed.html

tags: added: certification-testing-passed
Brad Figg (brad-figg)
description: updated
Revision history for this message
John Johansen (jjohansen) wrote :

No CVEs

Brad Figg (brad-figg)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (9.0 KiB)

This bug was fixed in the package linux - 3.13.0-45.74

---------------
linux (3.13.0-45.74) trusty; urgency=low

  [ Seth Forshee ]

  * Release Tracking Bug
    - LP: #1410384

  [ Jesse Barnes ]

  * SAUCE: drm/i915/vlv: assert and de-assert sideband reset at boot and
    resume v3
    - LP: #1401963

  [ K. Y. Srinivasan ]

  * SAUCE: storvsc: force SPC-3 compliance on win8 and win8 r2 hosts
    - LP: #1406867

  [ Timo Aaltonen ]

  * SAUCE: Switch VLV/BYT to use i915_bdw.
    - LP: #1401963

  [ Upstream Kernel Changes ]

  * Revert "xhci: clear root port wake on bits if controller isn't wake-up
    capable"
    - LP: #1408779
  * KVM: PPC: BOOK3S: HV: CMA: Reserve cma region only in hypervisor mode
    - LP: #1400209
  * e1000e: Fix no connectivity when driver loaded with cable out
    - LP: #1400365
  * net/mlx4_core: Enable CQE/EQE stride support
    - LP: #1400127
  * net/mlx4_core: Cache line EQE size support
    - LP: #1400127
  * net/mlx4_en: Add mlx4_en_get_cqe helper
    - LP: #1400127
  * net/mlx4_core: Introduce mlx4_get_module_info for cable module info
    reading
    - LP: #1400127
  * ethtool, net/mlx4_en: Cable info, get_module_info/eeprom ethtool
    support
    - LP: #1400127
  * net/mlx4_core: Introduce ACCESS_REG CMD and eth_prot_ctrl dev cap
    - LP: #1400127
  * net/mlx4_core: Add ethernet backplane autoneg device capability
    - LP: #1400127
  * ethtool, net/mlx4_en: Add 100M, 20G, 56G speeds ethtool reporting
    support
    - LP: #1400127
  * net/mlx4_en: Use PTYS register to query ethtool settings
    - LP: #1400127
  * net/mlx4_en: Use PTYS register to set ethtool settings (Speed)
    - LP: #1400127
  * net/mlx4_en: Add support for setting rxvlan offload OFF/ON
    - LP: #1400127
  * net/mlx4_en: Add ethtool support for [rx|tx]vlan offload set to OFF/ON
    - LP: #1400127
  * net/mlx4_core: Prevent VF from changing port configuration
    - LP: #1400127
  * net/mlx4_en: mlx4_en_set_settings() always fails when autoneg is set
    - LP: #1400127
  * ipv4: fix nexthop attlen check in fib_nh_match
    - LP: #1408779
  * vxlan: fix a use after free in vxlan_encap_bypass
    - LP: #1408779
  * vxlan: using pskb_may_pull as early as possible
    - LP: #1408779
  * vxlan: fix a free after use
    - LP: #1408779
  * ipv4: fix a potential use after free in ip_tunnel_core.c
    - LP: #1408779
  * ax88179_178a: fix bonding failure
    - LP: #1408779
  * tcp: md5: do not use alloc_percpu()
    - LP: #1408779
  * ipv4: dst_entry leak in ip_send_unicast_reply()
    - LP: #1408779
  * drivers/net, ipv6: Select IPv6 fragment idents for virtio UFO packets
    - LP: #1408779
  * drivers/net: macvtap and tun depend on INET
    - LP: #1408779
  * ip6_tunnel: Use ip6_tnl_dev_init as the ndo_init function.
    - LP: #1408779
  * vti6: Use vti6_dev_init as the ndo_init function.
    - LP: #1408779
  * sit: Use ipip6_tunnel_init as the ndo_init function.
    - LP: #1408779
  * gre6: Move the setting of dev->iflink into the ndo_init functions.
    - LP: #1408779
  * vxlan: Do not reuse sockets for a different address family
    - LP: #1408779
  * net: sctp: fix memory leak in auth key management
    - LP: #1408779
  * smsc911x: power-...

Read more...

Changed in linux (Ubuntu Trusty):
status: New → Fix Released
Brad Figg (brad-figg)
description: updated
Revision history for this message
Brad Figg (brad-figg) wrote : Package Released!

The package has been published and the bug is being set to Fix Released

Changed in kernel-sru-workflow:
status: In Progress → Fix Released
description: updated
Revision history for this message
Erick Brunzell (lbsolost) wrote :

This kernel results in bug #1412602 but I'm not tech savvy enough to parse the changelogs other than noticing a few mentions of MSI.

Revision history for this message
Brad Figg (brad-figg) wrote : cavac (amd64) - tests ran: 147, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : rainier (amd64) - tests ran: 147, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : larsen (amd64) - tests ran: 147, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : cavac (i386) - tests ran: 147, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : tarf (amd64) - tests ran: 149, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : rainier (i386) - tests ran: 147, failed: 2
Revision history for this message
Brad Figg (brad-figg) wrote : larsen (i386) - tests ran: 147, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : tarf (i386) - tests ran: 149, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : zmeu (amd64) - tests ran: 149, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : rizzo (amd64) - tests ran: 149, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : zmeu (i386) - tests ran: 149, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : rizzo (i386) - tests ran: 149, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : tarf (amd64) - tests ran: 248, failed: 31
Revision history for this message
Brad Figg (brad-figg) wrote : tarf (amd64) - tests ran: 180, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : fozzie (amd64) - tests ran: 180, failed: 1
Revision history for this message
Brad Figg (brad-figg) wrote : ms10-35-mcdivittB0 (arm64) - tests ran: 153, failed: 4
Revision history for this message
Brad Figg (brad-figg) wrote : onza (amd64) - tests ran: 180, failed: 2
Revision history for this message
Brad Figg (brad-figg) wrote : tarf (i386) - tests ran: 153, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : fozzie (i386) - tests ran: 153, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : larsen (amd64) - tests ran: 180, failed: 5
Revision history for this message
Brad Figg (brad-figg) wrote : onza (i386) - tests ran: 153, failed: 0
Revision history for this message
Brad Figg (brad-figg) wrote : larsen (i386) - tests ran: 153, failed: 0
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.