The problem, per commit fc98c3c8c9dc ("printk: use rcuidle console tracepoint"), was printk usage from the cpuidle path where RCU was already disabled.
Per the patches earlier in this series, this is no longer the case. Signed-off-by: Peter Zijlstra (Intel) <pet...@infradead.org> Reviewed-by: Sergey Senozhatsky <senozhat...@chromium.org> Acked-by: Petr Mladek <pmla...@suse.com> Acked-by: Rafael J. Wysocki <rafael.j.wyso...@intel.com> Acked-by: Frederic Weisbecker <frede...@kernel.org> Tested-by: Tony Lindgren <t...@atomide.com> Tested-by: Ulf Hansson <ulf.hans...@linaro.org> --- kernel/printk/printk.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/kernel/printk/printk.c +++ b/kernel/printk/printk.c @@ -2238,7 +2238,7 @@ static u16 printk_sprint(char *text, u16 } } - trace_console_rcuidle(text, text_len); + trace_console(text, text_len); return text_len; }