From 20339ac07485a6b20dfe1598821b1f6acda097e2 Mon Sep 17 00:00:00 2001 From: "Paul E. McKenney" Date: Sun, 2 Oct 2011 17:21:18 -0700 Subject: [PATCH] --- yaml --- r: 277198 b: refs/heads/master c: 2c01531f08f8ba663a20d8472a3032f6df133b6e h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/RCU/stallwarn.txt | 5 +++++ 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/[refs] b/[refs] index 751903beb202..881b8e4bbd93 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 91afaf300269aa99a4d646969b3258b74294ac4d +refs/heads/master: 2c01531f08f8ba663a20d8472a3032f6df133b6e diff --git a/trunk/Documentation/RCU/stallwarn.txt b/trunk/Documentation/RCU/stallwarn.txt index 4e959208f736..f3e0625f4290 100644 --- a/trunk/Documentation/RCU/stallwarn.txt +++ b/trunk/Documentation/RCU/stallwarn.txt @@ -101,6 +101,11 @@ o A CPU-bound real-time task in a CONFIG_PREEMPT_RT kernel that CONFIG_TREE_PREEMPT_RCU case, you might see stall-warning messages. +o A hardware or software issue shuts off the scheduler-clock + interrupt on a CPU that is not in dyntick-idle mode. This + problem really has happened, and seems to be most likely to + result in RCU CPU stall warnings for CONFIG_NO_HZ=n kernels. + o A bug in the RCU implementation. o A hardware failure. This is quite unlikely, but has occurred