Comment 13 for bug 1981339

I didn't realize Frank was on that as well :-/
Well now it was tested two times...

In addition the autopkgtests that got reported all are known to be flaky.
I restarted them to see if anything would be reproducible (the logs do not look like it so far). By now three recovered, one is left rerunning again.

For the case itself I ran the testcase and hang (as expected) in trying with jammy as-is.

Then I upgraded to -proposed which worked fine:

root@j:~/linux-5.19.14# apt install qemu-system-s390x qemu-utils qemu-system-data qemu-system-common qemu-block-extra
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested packages:
  debootstrap
The following packages will be upgraded:
  qemu-block-extra qemu-system-common qemu-system-data qemu-system-s390x qemu-utils
5 upgraded, 0 newly installed, 0 to remove and 21 not upgraded.
Need to get 7665 kB of archives.
After this operation, 5120 B of additional disk space will be used.
Get:1 http://ports.ubuntu.com/ubuntu-ports jammy-proposed/main s390x qemu-block-extra s390x 1:6.2+dfsg-2ubuntu6.5 [65.6 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports jammy-proposed/main s390x qemu-system-data all 1:6.2+dfsg-2ubuntu6.5 [1431 kB]
Get:3 http://ports.ubuntu.com/ubuntu-ports jammy-proposed/main s390x qemu-system-s390x s390x 1:6.2+dfsg-2ubuntu6.5 [2777 kB]
Get:4 http://ports.ubuntu.com/ubuntu-ports jammy-proposed/main s390x qemu-system-common s390x 1:6.2+dfsg-2ubuntu6.5 [1930 kB]
Get:5 http://ports.ubuntu.com/ubuntu-ports jammy-proposed/main s390x qemu-utils s390x 1:6.2+dfsg-2ubuntu6.5 [1461 kB]
Fetched 7665 kB in 1s (7003 kB/s)
(Reading database ... 78617 files and directories currently installed.)
Preparing to unpack .../qemu-block-extra_1%3a6.2+dfsg-2ubuntu6.5_s390x.deb ...
Unpacking qemu-block-extra (1:6.2+dfsg-2ubuntu6.5) over (1:6.2+dfsg-2ubuntu6.4) ...
Preparing to unpack .../qemu-system-data_1%3a6.2+dfsg-2ubuntu6.5_all.deb ...
Unpacking qemu-system-data (1:6.2+dfsg-2ubuntu6.5) over (1:6.2+dfsg-2ubuntu6.4) ...
Preparing to unpack .../qemu-system-s390x_1%3a6.2+dfsg-2ubuntu6.5_s390x.deb ...
Unpacking qemu-system-s390x (1:6.2+dfsg-2ubuntu6.5) over (1:6.2+dfsg-2ubuntu6.4) ...
Preparing to unpack .../qemu-system-common_1%3a6.2+dfsg-2ubuntu6.5_s390x.deb ...
Unpacking qemu-system-common (1:6.2+dfsg-2ubuntu6.5) over (1:6.2+dfsg-2ubuntu6.4) ...
Preparing to unpack .../qemu-utils_1%3a6.2+dfsg-2ubuntu6.5_s390x.deb ...
Unpacking qemu-utils (1:6.2+dfsg-2ubuntu6.5) over (1:6.2+dfsg-2ubuntu6.4) ...
Setting up qemu-system-common (1:6.2+dfsg-2ubuntu6.5) ...
Setting up qemu-system-data (1:6.2+dfsg-2ubuntu6.5) ...
Setting up qemu-utils (1:6.2+dfsg-2ubuntu6.5) ...
Setting up qemu-system-s390x (1:6.2+dfsg-2ubuntu6.5) ...
Setting up qemu-block-extra (1:6.2+dfsg-2ubuntu6.5) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Scanning processes...
No services need to be restarted.
No containers need to be restarted.
No user sessions are running outdated binaries.
No VM guests are running outdated hypervisor (qemu) binaries on this host.
root@j:~/linux-5.19.14#

Now I ran the test again...
10 loops passed, no hang -> verified