Bug ID 1202727
Summary Upstream kernel commit 30de14b1884ba makes s390 to stop working on qemu
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware S/390-64
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Kernel
Assignee kernel-bugs@opensuse.org
Reporter mpdesouza@suse.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

If the following commit is reverted

  commit 30de14b1884ba609fc1acfba5b40309e3a6ccefe
  Author: Sven Schnelle <svens@linux.ibm.com>
  Date:   Fri Apr 8 14:51:26 2022 +0200

      s390: current_stack_pointer shouldn't be a function

qemu can boot a s390 correct. The commit was added in 5.18-rc3. With this
commit reverted qemu-kvm can boot v6.0-rc2 without any problem.

I found this bug while trying to debug a livepatch issue:
https://github.com/SUSE/qa_test_klp/issues/17

I enabled dyndebug while runnig the livepatch testing, but it didn't show
anything useful for the bug:

[  863.108916] livepatch: enabling patch 'klp_tc_10_livepatch'
[  863.112892] livepatch: 'klp_tc_10_livepatch': starting patching transition
[  864.310918] livepatch: 'klp_tc_10_livepatch': patching complete
[  864.972595] livepatch: 'klp_tc_10_livepatch': starting unpatching transition
[  866.395047] livepatch: 'klp_tc_10_livepatch': unpatching complete
[ 1003.993309] livepatch: enabling patch 'klp_tc_10_livepatch'
[ 1003.993320] livepatch: 'klp_tc_10_livepatch': initializing patching
transition
[ 1003.997171] livepatch: 'klp_tc_10_livepatch': starting patching transition
[ 1003.997396] livepatch: klp_try_switch_task: swapper/1:0 is running
[ 1003.997435] livepatch: klp_try_switch_task: swapper/2:0 is running
[ 1003.997467] livepatch: klp_try_switch_task: swapper/3:0 is running
[ 1003.997485] livepatch: klp_try_switch_task: swapper/4:0 is running
[ 1003.997504] livepatch: klp_try_switch_task: swapper/5:0 is running
[ 1003.997509] livepatch: klp_try_switch_task: swapper/6:0 is running
[ 1003.997542] livepatch: klp_try_switch_task: swapper/7:0 is running
[ 1003.997575] livepatch: klp_try_switch_task: swapper/8:0 is running
[ 1003.997610] livepatch: klp_try_switch_task: swapper/9:0 is running
[ 1005.430335] livepatch: 'klp_tc_10_livepatch': completing patching transition
[ 1005.430843] livepatch: 'klp_tc_10_livepatch': patching complete
[ 1006.878375] livepatch: 'klp_tc_10_livepatch': initializing unpatching
transition
[ 1006.878421] livepatch: 'klp_tc_10_livepatch': starting unpatching transition
[ 1006.878644] livepatch: klp_try_switch_task: swapper/1:0 is running
[ 1006.878664] livepatch: klp_try_switch_task: swapper/2:0 is running
[ 1006.878693] livepatch: klp_try_switch_task: swapper/3:0 is running
[ 1006.878722] livepatch: klp_try_switch_task: swapper/4:0 is running
[ 1006.878748] livepatch: klp_try_switch_task: swapper/5:0 is running
[ 1006.878780] livepatch: klp_try_switch_task: swapper/6:0 is running
[ 1006.878811] livepatch: klp_try_switch_task: swapper/7:0 is running
[ 1006.878830] livepatch: klp_try_switch_task: swapper/8:0 is running
[ 1006.878853] livepatch: klp_try_switch_task: swapper/9:0 is running
[ 1008.390362] livepatch: 'klp_tc_10_livepatch': completing unpatching
transition
[ 1008.394954] livepatch: 'klp_tc_10_livepatch': unpatching complete

I believe that maybe the two issues can be linked, due to the nature of the
patch, which can have some impacts on ftrace. Any advice would be welcome.
Thanks!


You are receiving this mail because: