linux-kernel - Re: printk NMI splat on boot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <36ccb46d-5041-47ce-b419-f49ccaeece9b@kernel.dk>
Date: Tue, 20 May 2025 14:41:40 -0600
From: Jens Axboe <axboe@...nel.dk>
To: John Ogness <john.ogness@...utronix.de>,
 LKML <linux-kernel@...r.kernel.org>
Cc: Petr Mladek <pmladek@...e.com>, Steven Rostedt <rostedt@...dmis.org>,
 "senozhatsky@...omium.org" <senozhatsky@...omium.org>,
 "Paul E. McKenney" <paulmck@...nel.org>
Subject: Re: printk NMI splat on boot

On 5/20/25 2:18 PM, Jens Axboe wrote:
>> What values are you using for CONFIG_RCU_EXP_CPU_STALL_TIMEOUT and
>> CONFIG_RCU_CPU_STALL_TIMEOUT?
> 
> CONFIG_RCU_CPU_STALL_TIMEOUT=21
> CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=2

This was =20 btw, guess it could cut a bit too much...

Changed them to:

CONFIG_RCU_CPU_STALL_TIMEOUT=100
CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=0

and complaining is gone.

-- 
Jens Axboe