Your message dated Thu, 20 Feb 2025 13:10:27 +0100 (CET)
with message-id <20250220121027.1f269be2...@eldamar.lan>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #961838,
regarding s390x 5.6.0 kernel unusable on qemu-system-s390x TCG
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
961838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-5.6.0-2-s390x
Source: linux
Version: 5.6.14-1
5.5 worked correctly:
# qemu-system-s390x -M s390-ccw-virtio -cpu max -m 512 -kernel
vmlinuz-5.5.0-0.bpo.2-s390x -display none -serial mon:stdio
qemu-system-s390x: warning: 'msa5-base' requires 'kimd-sha-512'.
qemu-system-s390x: warning: 'msa5-base' requires 'klmd-sha-512'.
KASLR disabled: CPU has no PRNG
[ 1.617782] Linux version 5.5.0-0.bpo.2-s390x
(debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP
Debian 5.5.17-1~bpo10+1 (2020-04-23)
[ 1.618669] setup: Linux is running under KVM in 64-bit mode
[ 1.619472] setup: The maximum memory size is 512MB
[ 1.620515] cpu: 1 configured CPUs, 0 standby CPUs
[...]
But 5.6 appears to stop immediately:
# qemu-system-s390x -M s390-ccw-virtio -cpu max -m 512 -kernel
vmlinuz-5.6.0-2-s390x -display none -serial mon:stdio
qemu-system-s390x: warning: 'msa5-base' requires 'kimd-sha-512'.
qemu-system-s390x: warning: 'msa5-base' requires 'klmd-sha-512'.
KASLR disabled: CPU has no PRNG
# echo $?
0
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a very old kernel or the bug is old itself
without resolution.
If you can reproduce it with
- the current version in unstable/testing
- the latest kernel from backports
please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Regards,
Salvatore
--- End Message ---
