https://bugzilla.suse.com/show_bug.cgi?id=1202727
https://bugzilla.suse.com/show_bug.cgi?id=1202727#c5
--- Comment #5 from Marcos de Souza ---
To exemplify, I'm testing on a s390x machine. Using the current v6.0-rc4:
commit 7e18e42e4b280c85b76967a9106a13ca61c16179 (HEAD, tag: v6.0-rc4,
origin/master, origin/HEAD)
Author: Linus Torvalds
Date: Sun Sep 4 13:10:01 2022 -0700
Linux 6.0-rc4
And executing qemu-system-s390x, it does not show any output:
qemu-system-s390x -kernel arch/s390/boot/vmlinux -nographic
But, if the problematic commit (30de14b1884ba609fc1acfba5b40309e3a6ccefe) is
reverted on top of 6.0-rc4, it panics as expected:
commit 82364b4f5173954e5e6d324531a950e3b898db09 (HEAD)
Author: Marcos
Date: Mon Sep 5 17:45:27 2022 +0000
Revert "s390: current_stack_pointer shouldn't be a function"
This reverts commit 30de14b1884ba609fc1acfba5b40309e3a6ccefe.
qemu-system-s390x -kernel arch/s390/boot/vmlinux -nographic
KASLR disabled: CPU has no PRNG
[ 0.422349] Linux version 6.0.0-rc4-00001-g82364b4f5173 (kgrtst@s390zlpa)
(gcc (SUSE Linux) 7.5.0, GNU ld (GNU Binutils; SUSE Linux Enterprise 15)
2.35.1.20201123-7.18) #36 SMP Mon Sep 5 17:51:20 UTC 2022
[ 0.423773] setup: Linux is running under KVM in 64-bit mode
[ 0.462163] setup: The maximum memory size is 128MB
[ 0.462679] setup: Relocating AMODE31 section of size 0x00003000
[ 0.464744] cpu: 1 configured CPUs, 0 standby CPUs
...
I hope this helps to explain what is the problem and how to reproduce it.
--
You are receiving this mail because:
You are on the CC list for the bug.