On Thu 2025-02-13 20:32:19, Yafang Shao wrote: > On Thu, Feb 13, 2025 at 7:19 PM Petr Mladek <pmladek@xxxxxxxx> wrote: > > > > On Tue 2025-02-11 14:24:36, Yafang Shao wrote: > > > I encountered a hard lockup when attempting to reproduce the panic issue > > > occurred on our production servers [0]. The hard lockup is as follows, > > > > > > [15852778.150191] livepatch: klp_try_switch_task: grpc_executor:421106 is sleeping on function do_exit > > > [15852778.169471] livepatch: klp_try_switch_task: grpc_executor:421244 is sleeping on function do_exit > > > [15852778.188746] livepatch: klp_try_switch_task: grpc_executor:421457 is sleeping on function do_exit > > > [15852778.208021] livepatch: klp_try_switch_task: grpc_executor:422407 is sleeping on function do_exit > > > [15852778.227292] livepatch: klp_try_switch_task: grpc_executor:423184 is sleeping on function do_exit > > > [15852778.246576] livepatch: klp_try_switch_task: grpc_executor:423582 is sleeping on function do_exit > > > [15852778.265863] livepatch: klp_try_switch_task: grpc_executor:423738 is sleeping on function do_exit > > > [15852778.285149] livepatch: klp_try_switch_task: grpc_executor:423739 is sleeping on function do_exit > > > [15852778.304446] livepatch: klp_try_switch_task: grpc_executor:423833 is sleeping on function do_exit > > > [15852778.323738] livepatch: klp_try_switch_task: grpc_executor:423893 is sleeping on function do_exit > > > [15852778.343017] livepatch: klp_try_switch_task: grpc_executor:423894 is sleeping on function do_exit > > > [15852778.362292] livepatch: klp_try_switch_task: grpc_executor:423976 is sleeping on function do_exit > > > [15852778.381565] livepatch: klp_try_switch_task: grpc_executor:423977 is sleeping on function do_exit > > > [15852778.400847] livepatch: klp_try_switch_task: grpc_executor:424610 is sleeping on function do_exit > > > > This message does not exist in vanilla kernel. It looks like an extra > > debug message. And many extra messages might create stalls on its own. > > Right, the dynamic_debug is enabled: > > $ echo 'file kernel/* +p' > /sys/kernel/debug/dynamic_debug/control > > > > > AFAIK, your reproduced the problem even without these extra messages. > > There are two issues during the KLP transition: > 1. RCU warnings > 2. hard lockup > > RCU stalls can be easily reproduced without the extra messages. > However, hard lockups cannot be reproduced unless dynamic debugging is > enabled. OK, I would ignore the hard lockup for now. I believe that it is related to flushing the debug messages on the console. And a solution for the RCU stall might likely solve this as well. Also the debug messages are not enabled on production systems... We should debug the RCU warning without these debug messages! Best Regards, Petr
