From 28194a719952cbe880a9f0f53f2dda6c86019b07 Mon Sep 17 00:00:00 2001 From: Aleksandr Nogikh Date: Fri, 1 Nov 2024 13:05:28 +0100 Subject: dashboard/config: set RCU_EXP_CPU_STALL_TIMEOUT to 0 The zero values makes the kernel use the RCU_CPU_STALL_TIMEOUT value, which is already set to a big enough value. Context: see the recent LKML discussion at https://lore.kernel.org/all/6723aa4d.050a0220.35b515.0161.GAE@google.com/T/ --- dashboard/config/linux/android-6.1.config | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'dashboard/config/linux/android-6.1.config') diff --git a/dashboard/config/linux/android-6.1.config b/dashboard/config/linux/android-6.1.config index ae7f84fe9..fa8ee2397 100644 --- a/dashboard/config/linux/android-6.1.config +++ b/dashboard/config/linux/android-6.1.config @@ -7963,7 +7963,7 @@ CONFIG_BUG_ON_DATA_CORRUPTION=y # CONFIG_RCU_TORTURE_TEST is not set # CONFIG_RCU_REF_SCALE_TEST is not set CONFIG_RCU_CPU_STALL_TIMEOUT=100 -CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=21000 +CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=0 # CONFIG_RCU_TRACE is not set # CONFIG_RCU_EQS_DEBUG is not set # end of RCU Debugging -- cgit mrf-deployment