bionic/linux-hwe-5.4: 5.4.0-58.64~18.04.1 -proposed tracker

[Khaled El Mously]

This bug will contain status and test results related to a kernel source (or snap) as stated in the title.

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
kernel-stable-master-bug: 1907390
packages:
  lrm: linux-restricted-modules-hwe-5.4
  main: linux-hwe-5.4
  meta: linux-meta-hwe-5.4
  signed: linux-signed-hwe-5.4
phase: Complete
phase-changed: Saturday, 12. December 2020 09:45 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
synthetic:
  :promote-to-as-proposed: Fix Released
variant: debs
versions:
  lrm: 5.4.0-58.64~18.04.1
  main: 5.4.0-58.64~18.04.1
  meta: 5.4.0.58.64~18.04.53
  signed: 5.4.0-58.64~18.04.1

[Kleber Sacilotto de Souza (kleber-souza)]

Certification-testing not needed for this kernel re-spin.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

The following packages ended up in the wrong component in the Proposed pocket:

linux-modules-nvidia-390-oem-osp1 5.4.0-58.64~18.04.1 - is in multiverse instead of restricted
linux-modules-nvidia-418-oem-osp1 5.4.0-58.64~18.04.1 - is in multiverse instead of restricted

Once this is fixed, set the promote-to-proposed to Fix Released again

[Kleber Sacilotto de Souza (kleber-souza)]

Boot tests completed successfully, setting regression-testing as 'Fix Released'.

[Kleber Sacilotto de Souza (kleber-souza)]

Manually setting automated-testing to 'Fix Released' as running all tests is not necessary for this re-spin.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-hwe-5.4 - 5.4.0-58.64~18.04.1

---------------
linux-hwe-5.4 (5.4.0-58.64~18.04.1) bionic; urgency=medium

  * bionic/linux-hwe-5.4: 5.4.0-58.64~18.04.1 -proposed tracker (LP: #1907389)

  [ Ubuntu: 5.4.0-58.64 ]

  * focal/linux: 5.4.0-58.64 -proposed tracker (LP: #1907390)
  * Packaging resync (LP: #1786013)
    - update dkms package versions
  * raid10: discard leads to corrupted file system (LP: #1907262)
    - Revert "dm raid: remove unnecessary discard limits for raid10"
    - Revert "dm raid: fix discard limits for raid1 and raid10"
    - Revert "md/raid10: improve discard request for far layout"
    - Revert "md/raid10: improve raid10 discard request"
    - Revert "md/raid10: pull codes that wait for blocked dev into one function"
    - Revert "md/raid10: extend r10bio devs to raid disks"
    - Revert "md: add md_submit_discard_bio() for submitting discard bio"

 -- Stefan Bader <email address hidden> Wed, 09 Dec 2020 12:06:57 +0100

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

All tasks have been completed and the bug is being set to Fix Released