rcu self-detected stall messages on OMAP3, 4 boards
Paul Walmsley
paul at pwsan.com
Fri Sep 21 14:59:58 EDT 2012
Hi
Just did a test with CONFIG_NO_HZ=n, and no rcu_sched stall messages
appeared for 60 minutes.
Following is the diff from omap2plus_defconfig.
- Paul
--- .config 2012-09-21 12:51:19.114938954 -0600
+++ .testconfig 2012-09-21 12:51:15.686926318 -0600
@@ -69,7 +69,7 @@
# Timers subsystem
#
CONFIG_TICK_ONESHOT=y
-CONFIG_NO_HZ=y
+# CONFIG_NO_HZ is not set
CONFIG_HIGH_RES_TIMERS=y
#
@@ -80,7 +80,6 @@
CONFIG_RCU_FANOUT=32
CONFIG_RCU_FANOUT_LEAF=16
# CONFIG_RCU_FANOUT_EXACT is not set
-# CONFIG_RCU_FAST_NO_HZ is not set
# CONFIG_TREE_RCU_TRACE is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
@@ -2535,7 +2534,7 @@
# CONFIG_BOOT_PRINTK_DELAY is not set
# CONFIG_RCU_TORTURE_TEST is not set
CONFIG_RCU_CPU_STALL_TIMEOUT=60
-# CONFIG_RCU_CPU_STALL_INFO is not set
+CONFIG_RCU_CPU_STALL_INFO=y
# CONFIG_RCU_TRACE is not set
# CONFIG_KPROBES_SANITY_TEST is not set
# CONFIG_BACKTRACE_SELF_TEST is not set
More information about the linux-arm-kernel
mailing list