I can validate with spec_rstack_overflow=off boot parameter instead of recompiling, which has the same runtime effect as disabling CONFIG_MITIGATION_SRSO. I'm currently testing with processor.max_cstate=1 which avoids the crash path (cpuidle deep states → sched_tick → srso_safe_ret). If the crashes still occur, I'll test with spec_rstack_overflow=off next and report back. Full kdump vmcores are available if needed for deeper analysis.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2160457 Title: Kernel panic in srso_safe_ret / kick_ilb during sched_tick on AMD Ryzen 7 4800U (Zen2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160457/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
