bionic/linux-raspi-5.4: 5.4.0-1028.31~18.04.1 -proposed tracker

[Kelsey Steele]

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
built:
  main: build#1
  meta: build#1
kernel-stable-master-bug: 1911311
packages:
  main: linux-raspi-5.4
  meta: linux-meta-raspi-5.4
phase: Complete
phase-changed: Thursday, 28. January 2021 17:39 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
synthetic:
  :promote-to-as-proposed: Fix Released
variant: debs
versions:
  main: 5.4.0-1028.31~18.04.1
  meta: 5.4.0.1028.31

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Gavin Lin (gavin.lin)]

Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here:
Rpi2b-armhf: https://certification.canonical.com/hardware/201608-25030/submission/198223/
Rpi3b-arm64: https://certification.canonical.com/hardware/201907-27197/submission/198219/
Rpi3b-armhf: https://certification.canonical.com/hardware/201811-26649/submission/198241/
Rpi3a+-arm64: https://certification.canonical.com/hardware/201907-27199/submission/198213/
Rpi3a+-armhf: https://certification.canonical.com/hardware/201901-26785/submission/198214/
Rpi3b+-arm64: https://certification.canonical.com/hardware/201810-26542/submission/198231/
Rpi3b+-armhf: https://certification.canonical.com/hardware/201907-27198/submission/198235/
Rpi4b-1g-arm64: https://certification.canonical.com/hardware/201911-27471/submission/198205/
Rpi4b-1g-armhf: https://certification.canonical.com/hardware/201911-27471/submission/198308/
Rpi4b-2g-arm64: https://certification.canonical.com/hardware/201911-27506/submission/198211/
Rpi4b-2g-armhf: https://certification.canonical.com/hardware/201911-27506/submission/198301/
Rpi4b-4g-arm64: https://certification.canonical.com/hardware/201911-27455/submission/198206/
Rpi4b-4g-armhf: https://certification.canonical.com/hardware/201911-27456/submission/198228/
Rpi4b-8g-arm64: https://certification.canonical.com/hardware/202004-27866/submission/198208/
Rpi4b-8g-armhf: https://certification.canonical.com/hardware/202004-27866/submission/198229/
CM3-arm64: https://certification.canonical.com/hardware/201711-25992/submission/198220/
CM3-armhf: https://certification.canonical.com/hardware/201711-25992/submission/198246/
CM3+-arm64: https://certification.canonical.com/hardware/201908-27277/submission/198215/
CM3+-armhf: https://certification.canonical.com/hardware/201908-27277/submission/198239/

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-raspi-5.4 - 5.4.0-1028.31~18.04.1

---------------
linux-raspi-5.4 (5.4.0-1028.31~18.04.1) bionic; urgency=medium

  * bionic/linux-raspi-5.4: 5.4.0-1028.31~18.04.1 -proposed tracker
    (LP: #1911310)

  [ Ubuntu: 5.4.0-1028.31 ]

  * focal/linux-raspi: 5.4.0-1028.31 -proposed tracker (LP: #1911311)
  * focal/linux: 5.4.0-63.71 -proposed tracker (LP: #1911333)
  * overlay: permission regression in 5.4.0-51.56 due to patches related to
    CVE-2020-16120 (LP: #1900141)
    - ovl: do not fail because of O_NOATIME
  * Focal update: v5.4.79 upstream stable release (LP: #1907151)
    - net/mlx5: Use async EQ setup cleanup helpers for multiple EQs
    - net/mlx5: poll cmd EQ in case of command timeout
    - net/mlx5: Fix a race when moving command interface to events mode
    - net/mlx5: Add retry mechanism to the command entry index allocation
  * Kernel 5.4.0-56 Wi-Fi does not connect (LP: #1906770)
    - mt76: fix fix ampdu locking
  * [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports
    topology where zoning is enabled in expander (LP: #1899802)
    - scsi: mpt3sas: Define hba_port structure
    - scsi: mpt3sas: Allocate memory for hba_port objects
    - scsi: mpt3sas: Rearrange _scsih_mark_responding_sas_device()
    - scsi: mpt3sas: Update hba_port's sas_address & phy_mask
    - scsi: mpt3sas: Get device objects using sas_address & portID
    - scsi: mpt3sas: Rename transport_del_phy_from_an_existing_port()
    - scsi: mpt3sas: Get sas_device objects using device's rphy
    - scsi: mpt3sas: Update hba_port objects after host reset
    - scsi: mpt3sas: Set valid PhysicalPort in SMPPassThrough
    - scsi: mpt3sas: Handling HBA vSES device
    - scsi: mpt3sas: Add bypass_dirty_port_flag parameter
    - scsi: mpt3sas: Handle vSES vphy object during HBA reset
    - scsi: mpt3sas: Add module parameter multipath_on_hba
    - scsi: mpt3sas: Bump driver version to 35.101.00.00
  * focal/linux: 5.4.0-62.70 -proposed tracker (LP: #1911144)
  * CVE-2020-28374
    - SAUCE: target: fix XCOPY NAA identifier lookup
  * Packaging resync (LP: #1786013)
    - update dkms package versions

  [ Ubuntu: 5.4.0-1027.30 ]

  * focal/linux-raspi: 5.4.0-1027.30 -proposed tracker (LP: #1910016)
  * rpi3b+ wifi doesn't get used if ethernet disconnected (LP: #1890487)
    - net: lan78xx: Ack pending PHY ints when resetting
  * focal/linux-raspi: Upstream raspberrypi patchset 2020-12-10 (LP: #1908077)
    - ARM: dts: Limit BT modem baud rate on 3B
    - configs: Enable CHACHA20POLY1305=m
    - overlays: Update i2c0 overlay to disable the i2c0mux.
    - dt: Remove duplicate assignment for i2c0 pinctrl config
    - overlays: Add option for composite to vc4-kms-v3d-pi4.
    - minor typo in directions
    - overlays: Regenerate upstream-pi4 overlay
    - overlays: Add parameters to adafruit18, sainsmart18
    - rpivid_h265: Fix width/height typo
    - overlays: Add extra CMA sizes (up to 512M)
    - overlays: Add note to BCM2711 overlays
    - overlays: adafruit18,sainsmart18: default bgr to off
    - configs: Remove I2C_BRCMSTB from the kernel
    - net: bcmgenet: Reset RBUF on first open
    - ASoC: cs42xx8...

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

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