Lines Matching refs:that
5 options that can be used to fine-tune the detector's operation. Finally,
31 o Booting Linux using a console connection that is too slow to
38 o Anything that prevents RCU's grace-period kthreads from running.
48 that low-priority task is not permitted to run on any other CPU,
54 o A CPU-bound real-time task in a CONFIG_PREEMPT_RT kernel that
66 Note that certain high-overhead debugging options, for example
74 slow system. Note that thermal throttling and on-demand governors
78 interrupt on a CPU that is not in dyntick-idle mode. This
88 leading the realization that the CPU had failed.
91 warning. Note that SRCU does -not- have CPU stall warnings. Please note
92 that RCU only detects CPU stalls when there is a grace period in progress.
100 that portion of the stack which remains the same from trace to trace.
111 CPU stall detector, which detects conditions that unduly delay RCU grace
120 that RCU will wait from the beginning of a grace period until it
169 For non-RCU-tasks flavors of RCU, when a CPU detects that it is stalling,
177 This message indicates that CPU 32 detected that CPUs 2 and 16 were both
178 causing stalls, and that the stall was affecting RCU-sched. This message
179 will normally be followed by stack dumps for each CPU. Please note that
180 PREEMPT_RCU builds can be stalled by tasks as well as by CPUs, and that
186 CPU 2's "(3 GPs behind)" indicates that this CPU has not interacted with
188 ticks this GP)" indicates that this CPU has not taken any scheduling-clock
200 handlers that the stalled CPU has executed. The number before the "/"
201 is the number that had executed since boot at the time that this CPU
205 time period. The number after the "/" is the number that have executed
207 across repeated stall-warning messages, it is possible that RCU's softirq
213 detection passes that the grace-period kthread has made across this
214 CPU since the last time that this CPU noted the beginning of a grace
233 Finally, an "L" indicates that there are currently no non-lazy callbacks
234 ("." is printed otherwise, as shown above) and "D" indicates that
247 interact. Please note that it is not possible to entirely eliminate this
257 The "23807" indicates that it has been more than 23 thousand jiffies
259 indicates how frequently that kthread should run, giving the number
274 to the grace-period kthread, the "RCU_GP_WAIT_FQS" indicates that the
276 task_struct ->state field, and the "cpu" indicates that the grace-period
284 longer intervals, so that the time between (say) the first and second
296 This indicates that CPU 7 has failed to respond to a reschedule IPI.
297 The three periods (".") following the CPU number indicate that the CPU
299 that the CPU was online at the beginning of the expedited grace period
300 (otherwise the second period would have instead been "o"), and that
303 indicates that the expedited grace period has been going on for 21,119
304 jiffies. The number following the "s:" indicates that the expedited
305 grace-period sequence counter is 73. The fact that this last value is
306 odd indicates that an expedited grace period is in flight. The number
307 following "root:" is a bitmask that indicates which children of the root
308 rcu_node structure correspond to CPUs and/or tasks that are blocking the
314 tasks as well as by CPUs, and that the tasks will be indicated by PID,