Problems with HVCS and hotplugging

[bugproxy]

SRU Justification:
==================

[Impact]

 * HVCS (Hypervisor Virtual Console Server) is broken because the
   virtual terminal mkvterm fails, caused by pvmutil failing.

 * When mkvterm is ran, it ultimately fails because it calls pvmutil
   which fails.
   pvmutil calls drmgr, and drmgr is adding a slot correctly.
   However, when drmgr writes the slot information to ?/add_slot,
   the return is -ENODEV.

 * This leads to HVCS never having probe() called.

 * In addition, HVCS is missing patches/fixes, and is broken without them.

[Fix]

 * Fix one and two is required for focal only, all other for focal and jammy:

 * 57409d4fb12c 57409d4fb12c185b2c0689e0496878c8f6bb5b58
   "powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry"

 * c5e76fa05b2d c5e76fa05b2df519b9f08571cc57e623c1569faa
   "powerpc/pseries: Fix of_read_drc_info_cell() to point at next record"

 * 6a9a733edd46 6a9a733edd46732e906d976dc21a42dd361e53cc
   "hvcs: Fix hvcs port reference counting"

 * 760aa5e81f33 760aa5e81f33e0da82512c4288489739a6d1c556
   "hvcs: Use dev_groups to manage hvcs device attributes"

 * 503a90dd619d 503a90dd619d52dcac2cc68bd742aa914c7cd47a
   "hvcs: Use driver groups to manage driver attributes"

 * 3a8d3b366ce4 3a8d3b366ce47024bf274eac783f8af5df2780f5
   "hvcs: Get reference to tty in remove"

 * d432228bc7b1 d432228bc7b1b3f0ed06510278ff5a77b3749fe6
   "hvcs: Use vhangup in hotplug remove"

 * 28d49f8cbe9c 28d49f8cbe9c7966f91ee1b5ec2f997f6e55bf9f
   "hvcs: Synchronize hotplug remove with port free"

[Test Plan]

 * The high level test plan is to run mkvterm with an id.

 * mkvterm will fail because /dev/hvcs* device nodes are missing.

 * Details see https://bugs.launchpad.net/bugs/2023243 for more information.
   Especially the script provided by IBM
   (see original bug description: `---Steps to Reproduce---`).

 * IBM will (stress) test the updated kernel(s) provided in -proposed.

[Where problems could occur]

 * The first two commits affect arch/powerpc/platforms/pseries/of_helpers.c
   and are needed to fix the hotplugging issue seen when drmgr goes to write
   the slot information to /sys/bus/pci/slots/control/add_slot.
   In case of issues here hotplugging with drmgr might break.

 * The issue lies in rpadlpar_io and rpaphp calling an of helper function
   of_read_drc_info_cell(). Without these commits, the value stored
   drc_index_start is incorrect.
   This ultimately results in the entire SLOT string being incorrect,
   and rpaphp never finding the newly added slot by drmgr.
   rpadlpar then returns -ENODEV.
   Therefore, HVCS is never probed, and the device nodes are never created.

 * HVCS, rpadlpar_io, and rpaphp should ideally not even need to be loaded
   prior to drmgr adding a vio slot.
   If rpadlpar_io and rpaphp are not loaded, drmgr will load them.
   In addition, if rpadlpar_io and rpaphp register the new slot correctly,
   rpadlpar_io will call dlpar_add_vio_slot(),
   which calls vio_register_device_node() with the device node.
   This is what tells the driver core to init and probe HVCS
   (which is needed to create the device nodes).

 * The remaning 6 commits are needed for HVCS, that is essentially
   broken without them.
   Overall, issues they fix are race conditions, hotplug remove issues,
   as well as memory leaks.

 * Please notice that this is entirely ppc64el architecture-specifc.

[Other Info]

 * All the commits listed above are included in mantic and noble.
   Hence these are set to Invalid.

 * Meanwhile these requested commits have been added to other
   kernels and distros.
__________

---Problem Description---
Issues with HVCS and hotplugging issues.

When working on Canonical bug 2023243, it was discovered that mkvterm was not working for multiple reasons. This bug will cover the issues found in HVCS, and hotplugging issues found when drmgr writes the slot information to .../add_slot.

When mkvterm is ran, it ultimately fails because it calls pvmutil which fails. pvmutil calls drmgr, and drmgr is adding a slot correctly. However, when drmgr writes the slot information to ?/add_slot, the return is -ENODEV. This leads to HVCS never having probe() called. In addition, HVCS is missing patches, and is broken without them. 8 kernel patches have been identified to fix these issues.

---uname output---
Linux neop91.pok.stglabs.ibm.com 5.4.0-173-generic #191-Ubuntu SMP Fri Feb 2 13:54:35 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux

---Steps to Reproduce---
 Run mkvterm with an id. mkvterm will fail because /dev/hvcs* device nodes are missing. See https://bugs.launchpad.net/ubuntu/+source/powerpc-utils/+bug/2023243 for more information.

------------------------

2 commits made to arch/powerpc/platforms/pseries/of_helpers.c are needed. These commits fix the hotplugging issue seen when drmgr goes to write the slot information to /sys/bus/pci/slots/control/add_slot. This is also why the HVCS device nodes were not being created, as mentioned in the previous bug.

The issue lies in rpadlpar_io and rpaphp calling an of helper function of_read_drc_info_cell(). Without these commits, the value stored drc_index_start is incorrect. This ultimately results in the entire SLOT string being incorrect, and rpaphp never finding the newly added slot by drmgr. rpadlpar then returns -ENODEV. Therefore, HVCS is never probed, and the device nodes are never created.

Ideally - HVCS, rpadlpar_io, and rpaphp should not even need to be loaded prior to drmgr adding a vio slot. If rpadlpar_io and rpaphp are not loaded, drmgr will load them. In addition, if rpadlpar_io and rpaphp register the new slot correctly, rpadlpar_io will call dlpar_add_vio_slot(), which calls vio_register_device_node() with the device node. This is what tells the driver core to init and probe HVCS (which is needed to create the device nodes).

In addition to the 2 commits mentioned above, 6 HVCS commits are needed. HVCS is essentially broken without them. Issues include race conditions, hotplug remove issues, as well as memory leaks. These commits have been added to other distros after multiple issues were seen. Without these commits, 20.04 will experience the same issues. IBM plans on stress testing these changes after an updated kernel is provided in focal-proposed.

-------

2 commits that make changes to arch/powerpc/platforms/pseries/of_helpers.c:

powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=57409d4fb12c185b2c0689e0496878c8f6bb5b58

powerpc/pseries: Fix of_read_drc_info_cell() to point at next record
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c5e76fa05b2df519b9f08571cc57e623c1569faa

HVCS commits:

hvcs: Fix hvcs port reference counting
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a9a733edd46732e906d976dc21a42dd361e53cc

hvcs: Use dev_groups to manage hvcs device attributes
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=760aa5e81f33e0da82512c4288489739a6d1c556

hvcs: Use driver groups to manage driver attributes
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=503a90dd619d52dcac2cc68bd742aa914c7cd47a

hvcs: Get reference to tty in remove
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3a8d3b366ce47024bf274eac783f8af5df2780f5

hvcs: Use vhangup in hotplug remove
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d432228bc7b1b3f0ed06510278ff5a77b3749fe6

hvcs: Synchronize hotplug remove with port free
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=28d49f8cbe9c7966f91ee1b5ec2f997f6e55bf9f

[Frank Heimes (fheimes)]

Hello and many thanks for raising these HVCS issue.

I first of all analyzed the commits upstream and in the specific Ubuntu kernel trees and found that focal and to some extend jammy are affected. Mantic and noble are not affected:

commit 57409d4fb12c got upstream accepted with v5.5(-rc1)
commit c5e76fa05b2d got upstream accepted with v5.7(-rc1)
commit 6a9a733edd46 got upstream accepted with v6.3(-rc1)
commit 760aa5e81f33 got upstream accepted with v6.3(-rc1)
commit 503a90dd619d got upstream accepted with v6.3(-rc1)
commit 3a8d3b366ce4 got upstream accepted with v6.3(-rc1)
commit d432228bc7b1 got upstream accepted with v6.3(-rc1)
commit 28d49f8cbe9c got upstream accepted with v6.3(-rc1)

commits/release focal jammy mantic noble
57409d4fb12c n y y y
c5e76fa05b2d n y y y
6a9a733edd46 n n y y
760aa5e81f33 n n y y
503a90dd619d n n y y
3a8d3b366ce4 n n y y
d432228bc7b1 n n y y
28d49f8cbe9c n n y y

So I'm adding focal and jammy as targets.

[Frank Heimes (fheimes)]

Currently test kernels are being build for focal/20.04 and jammy/22.04 in this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp2056373

[Frank Heimes (fheimes)]

SRU request submitted to the Ubuntu kernel team mailing list for mantic, lunar and jammy.
https://lists.ubuntu.com/archives/kernel-team/2024-March/thread.html#149437
Changing status to 'In Progress' for jammy and focal.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2024-03-11 14:00 EDT-------
Thank you Frank for providing a test kernel! I have installed the test kernel and everything appears to be working smoothly.

---
root@neop91:/home/neo# mkvterm --id 2
vterm for partition 2 is active. Press Control+] to exit.
IBM Virtual I/O Server

login:
Cleaning up...
vterm closed
---

syslog:

---
Mar 11 17:52:13 neop91 kernel: [ 50.767514] HVCS: Driver registered.
Mar 11 17:52:13 neop91 drmgr: drmgr: -c slot -s U9080.M9S.13073A8-V1-C6 -a -w 3
Mar 11 17:52:13 neop91 kernel: [ 50.853870] rpaphp: RPA HOT Plug PCI Controller Driver version: 0.1
Mar 11 17:52:13 neop91 kernel: [ 51.030821] HVCS: vty-server@30000006 added to the vio bus.
Mar 11 17:52:13 neop91 kernel: [ 51.030860] rpadlpar_io: slot U9080.M9S.13073A8-V1-C6 added
Mar 11 17:52:16 neop91 kernel: [ 53.899124] HVCS: vty-server@30000006 connection opened.
Mar 11 17:52:23 neop91 kernel: [ 61.344106] HVCS: Closed vty-server@30000006 and partner vty@30000000:2 connection.
Mar 11 17:52:24 neop91 drmgr: drmgr: -c slot -s U9080.M9S.13073A8-V1-C6 -r -w 3
Mar 11 17:52:24 neop91 kernel: [ 61.468923] HVCS: Destroyed hvcs_struct for vty-server@30000006.
Mar 11 17:52:24 neop91 kernel: [ 61.468925] HVCS: vty-server@30000006 removed from the vio bus.
Mar 11 17:52:24 neop91 kernel: [ 61.468971] rpadlpar_io: slot U9080.M9S.13073A8-V1-C6 removed
---

HVCS is being probed and rpadlpar_io is adding the slot information correctly. When mkvterm closes the connection with Ctrl+], HVCS is closing the connection properly and behaving as expected.

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

This bug is awaiting verification that the linux/5.4.0-176.196 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux' to 'verification-done-focal-linux'. If the problem still exists, change the tag 'verification-needed-focal-linux' to 'verification-failed-focal-linux'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2024-03-29 11:18 EDT-------
I tested to see if mkvterm was performing as expected with the kernel in focal-proposed, and the behavior was correct. Ritu in Novalink did as well.

In addition to that, the kernel was installed on two different lpars, and another engineer within IBM performed basic tests and stress tests. All tests passed. HVCS is working as expected. Many thanks

[Roxana Nicolescu (roxanan)]

Based on this, I'll set the tag to done. Thanks for testing it

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 5.4.0-176.196

---------------
linux (5.4.0-176.196) focal; urgency=medium

  * focal/linux: 5.4.0-176.196 -proposed tracker (LP: #2058756)

  * Problems with HVCS and hotplugging (LP: #2056373)
    - powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry
    - powerpc/pseries: Fix of_read_drc_info_cell() to point at next record
    - hvcs: Fix hvcs port reference counting
    - hvcs: Use dev_groups to manage hvcs device attributes
    - hvcs: Use driver groups to manage driver attributes
    - hvcs: Get reference to tty in remove
    - hvcs: Use vhangup in hotplug remove
    - hvcs: Synchronize hotplug remove with port free

linux (5.4.0-175.195) focal; urgency=medium

  * focal/linux: 5.4.0-175.195 -proposed tracker (LP: #2055684)

  * Packaging resync (LP: #1786013)
    - [Packaging] drop ABI data
    - [Packaging] update annotations scripts
    - debian.master/dkms-versions -- update from kernel-versions (main/2024.03.04)

  * Drop ABI checks from kernel build (LP: #2055686)
    - [Packaging] Remove in-tree abi checks
    - [Packaging] Bring back install-<flavour> prerequisite for checks-<flavour>
    - [Packaging] Remove abi-check from final-checks

  * Cranky update-dkms-versions rollout (LP: #2055685)
    - [Packaging] remove update-dkms-versions
    - Move debian/dkms-versions to debian.master/dkms-versions
    - [Packaging] Replace debian/dkms-versions with $(DEBIAN)/dkms-versions
    - [Packaging] remove update-version-dkms

  * linux-tools-common: man page of usbip[d] is misplaced (LP: #2054094)
    - [Packaging] rules: Put usbip manpages in the correct directory

  * CVE-2024-23851
    - dm ioctl: log an error if the ioctl structure is corrupted
    - dm: limit the number of targets and parameter size area

  * Focal update: v5.4.268 upstream stable release (LP: #2055075)
    - f2fs: explicitly null-terminate the xattr list
    - pinctrl: lochnagar: Don't build on MIPS
    - ALSA: hda - Fix speaker and headset mic pin config for CHUWI CoreBook XPro
    - ASoC: Intel: Skylake: Fix mem leak in few functions
    - ASoC: nau8822: Fix incorrect type in assignment and cast to restricted
      __be16
    - ASoC: Intel: Skylake: mem leak in skl register function
    - ASoC: cs43130: Fix the position of const qualifier
    - ASoC: cs43130: Fix incorrect frame delay configuration
    - ASoC: rt5650: add mutex to avoid the jack detection failure
    - nouveau/tu102: flush all pdbs on vmm flush
    - net/tg3: fix race condition in tg3_reset_task()
    - ASoC: da7219: Support low DC impedance headset
    - nvme: introduce helper function to get ctrl state
    - drm/exynos: fix a potential error pointer dereference
    - drm/exynos: fix a wrong error checking
    - clk: rockchip: rk3128: Fix HCLK_OTG gate register
    - jbd2: correct the printing of write_flags in jbd2_write_superblock()
    - drm/crtc: Fix uninit-value bug in drm_mode_setcrtc
    - neighbour: Don't let neigh_forced_gc() disable preemption for long
    - tracing: Have large events show up as '[LINE TOO BIG]' instead of nothing
    - tracing: Add size check when printing trace_marker output
    - ring-buffer: Do not rec...

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

This bug is awaiting verification that the linux-raspi/5.4.0-1107.119 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-raspi' to 'verification-done-focal-linux-raspi'. If the problem still exists, change the tag 'verification-needed-focal-linux-raspi' to 'verification-failed-focal-linux-raspi'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

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

This bug is awaiting verification that the linux-gkeop/5.4.0-1090.94 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-gkeop' to 'verification-done-focal-linux-gkeop'. If the problem still exists, change the tag 'verification-needed-focal-linux-gkeop' to 'verification-failed-focal-linux-gkeop'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

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

This bug is awaiting verification that the linux-azure/5.4.0-1128.135 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-azure' to 'verification-done-focal-linux-azure'. If the problem still exists, change the tag 'verification-needed-focal-linux-azure' to 'verification-failed-focal-linux-azure'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

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

This bug is awaiting verification that the linux-gcp/5.4.0-1127.136 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-gcp' to 'verification-done-focal-linux-gcp'. If the problem still exists, change the tag 'verification-needed-focal-linux-gcp' to 'verification-failed-focal-linux-gcp'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

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

This bug is awaiting verification that the linux-oracle/5.4.0-1122.131 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-oracle' to 'verification-done-focal-linux-oracle'. If the problem still exists, change the tag 'verification-needed-focal-linux-oracle' to 'verification-failed-focal-linux-oracle'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

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

This bug is awaiting verification that the linux-azure/5.4.0-1128.135 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-azure' to 'verification-done-focal-linux-azure'. If the problem still exists, change the tag 'verification-needed-focal-linux-azure' to 'verification-failed-focal-linux-azure'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

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

This bug is awaiting verification that the linux-hwe-5.4/5.4.0-177.197~18.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic-linux-hwe-5.4' to 'verification-done-bionic-linux-hwe-5.4'. If the problem still exists, change the tag 'verification-needed-bionic-linux-hwe-5.4' to 'verification-failed-bionic-linux-hwe-5.4'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

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

This bug is awaiting verification that the linux-aws/5.4.0-1123.133 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-aws' to 'verification-done-focal-linux-aws'. If the problem still exists, change the tag 'verification-needed-focal-linux-aws' to 'verification-failed-focal-linux-aws'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

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

This bug is awaiting verification that the linux-ibm/5.4.0-1070.75 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-ibm' to 'verification-done-focal-linux-ibm'. If the problem still exists, change the tag 'verification-needed-focal-linux-ibm' to 'verification-failed-focal-linux-ibm'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

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

This bug is awaiting verification that the linux-kvm/5.4.0-1111.118 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-kvm' to 'verification-done-focal-linux-kvm'. If the problem still exists, change the tag 'verification-needed-focal-linux-kvm' to 'verification-failed-focal-linux-kvm'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

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

This bug is awaiting verification that the linux-fips/5.4.0-1097.107 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-fips' to 'verification-done-focal-linux-fips'. If the problem still exists, change the tag 'verification-needed-focal-linux-fips' to 'verification-failed-focal-linux-fips'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

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

This bug is awaiting verification that the linux/5.15.0-104.114 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy-linux' to 'verification-failed-jammy-linux'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

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

This bug is awaiting verification that the linux-bluefield/5.4.0-1083.90 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-bluefield' to 'verification-done-focal-linux-bluefield'. If the problem still exists, change the tag 'verification-needed-focal-linux-bluefield' to 'verification-failed-focal-linux-bluefield'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

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

This bug is awaiting verification that the linux-iot/5.4.0-1035.36 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-iot' to 'verification-done-focal-linux-iot'. If the problem still exists, change the tag 'verification-needed-focal-linux-iot' to 'verification-failed-focal-linux-iot'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

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

This bug is awaiting verification that the linux-xilinx-zynqmp/5.4.0-1042.46 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal-linux-xilinx-zynqmp' to 'verification-done-focal-linux-xilinx-zynqmp'. If the problem still exists, change the tag 'verification-needed-focal-linux-xilinx-zynqmp' to 'verification-failed-focal-linux-xilinx-zynqmp'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!