Lines Matching full:that
5 options that can be used to fine-tune the detector's operation. Finally,
28 o Booting Linux using a console connection that is too slow to
35 o Anything that prevents RCU's grace-period kthreads from running.
45 that low-priority task is not permitted to run on any other CPU,
51 o A CPU-bound real-time task in a CONFIG_PREEMPT_RT kernel that
62 help avoid this problem. However, please note that doing this
69 Note that certain high-overhead debugging options, for example
77 slow system. Note that thermal throttling and on-demand governors
81 interrupt on a CPU that is not in dyntick-idle mode. This
91 leading the realization that the CPU had failed.
94 Note that SRCU does -not- have CPU stall warnings. Please note that
103 that portion of the stack which remains the same from trace to trace.
114 CPU stall detector, which detects conditions that unduly delay RCU grace
123 that RCU will wait from the beginning of a grace period until it
172 For non-RCU-tasks flavors of RCU, when a CPU detects that it is stalling,
180 This message indicates that CPU 32 detected that CPUs 2 and 16 were both
181 causing stalls, and that the stall was affecting RCU-sched. This message
182 will normally be followed by stack dumps for each CPU. Please note that
183 PREEMPT_RCU builds can be stalled by tasks as well as by CPUs, and that
188 CPU 2's "(3 GPs behind)" indicates that this CPU has not interacted with
190 ticks this GP)" indicates that this CPU has not taken any scheduling-clock
202 handlers that the stalled CPU has executed. The number before the "/"
203 is the number that had executed since boot at the time that this CPU
207 time period. The number after the "/" is the number that have executed
209 across repeated stall-warning messages, it is possible that RCU's softirq
215 detection passes that the grace-period kthread has made across this
216 CPU since the last time that this CPU noted the beginning of a grace
234 status, so that an "l" indicates that all callbacks were lazy at the start
235 of the last idle period and an "L" indicates that there are currently
237 shown above) and "D" indicates that dyntick-idle processing is enabled
250 interact. Please note that it is not possible to entirely eliminate this
260 The "23807" indicates that it has been more than 23 thousand jiffies
262 indicates how frequently that kthread should run, giving the number
277 to the grace-period kthread, the "RCU_GP_WAIT_FQS" indicates that the
279 task_struct ->state field, and the "cpu" indicates that the grace-period
287 longer intervals, so that the time between (say) the first and second
299 This indicates that CPU 7 has failed to respond to a reschedule IPI.
300 The three periods (".") following the CPU number indicate that the CPU
302 that the CPU was online at the beginning of the expedited grace period
303 (otherwise the second period would have instead been "o"), and that
306 indicates that the expedited grace period has been going on for 21,119
307 jiffies. The number following the "s:" indicates that the expedited
308 grace-period sequence counter is 73. The fact that this last value is
309 odd indicates that an expedited grace period is in flight. The number
310 following "root:" is a bitmask that indicates which children of the root
311 rcu_node structure correspond to CPUs and/or tasks that are blocking the
317 tasks as well as by CPUs, and that the tasks will be indicated by PID,