Lines Matching refs:that
9 options that can be used to fine-tune the detector's operation. Finally,
33 - Booting Linux using a console connection that is too slow to
40 - Anything that prevents RCU's grace-period kthreads from running.
50 that low-priority task is not permitted to run on any other CPU,
56 - A CPU-bound real-time task in a CONFIG_PREEMPT_RT kernel that
67 help avoid this problem. However, please note that doing this
74 Note that certain high-overhead debugging options, for example
82 slow system. Note that thermal throttling and on-demand governors
86 interrupt on a CPU that is not in dyntick-idle mode. This
90 - A hardware or software issue that prevents time-based wakeups
99 - A low-level kernel issue that either fails to invoke one of the
102 hand, or that invokes one of them too many times on the other.
115 leading the realization that the CPU had failed.
118 Note that SRCU does *not* have CPU stall warnings. Please note that
127 that portion of the stack which remains the same from trace to trace.
139 CPU stall detector, which detects conditions that unduly delay RCU grace
149 that RCU will wait from the beginning of a grace period until it
202 For non-RCU-tasks flavors of RCU, when a CPU detects that some other
210 This message indicates that CPU 32 detected that CPUs 2 and 16 were both
211 causing stalls, and that the stall was affecting RCU-sched. This message
212 will normally be followed by stack dumps for each CPU. Please note that
213 PREEMPT_RCU builds can be stalled by tasks as well as by CPUs, and that
220 CPU 2's "(3 GPs behind)" indicates that this CPU has not interacted with
222 ticks this GP)" indicates that this CPU has not taken any scheduling-clock
234 handlers that the stalled CPU has executed. The number before the "/"
235 is the number that had executed since boot at the time that this CPU
239 time period). The number after the "/" is the number that have executed
241 across repeated stall-warning messages, it is possible that RCU's softirq
247 detection passes that the grace-period kthread has made across this
248 CPU since the last time that this CPU noted the beginning of a grace
265 rcu_prepare_for_idle(). "dyntick_enabled: 1" indicates that dyntick-idle
277 interact. Please note that it is not possible to entirely eliminate this
287 The "23807" indicates that it has been more than 23 thousand jiffies
289 indicates how frequently that kthread should run, giving the number
305 to the grace-period kthread, the "RCU_GP_WAIT_FQS" indicates that the
307 task_struct ->state field, and the "cpu" indicates that the grace-period
315 The "23804" indicates that kthread's timer expired more than 23 thousand
323 Here "cpu" indicates that the grace-period kthread last ran on CPU 4,
331 of the stall, keeping in mind that the CPU detecting the stall will have
332 an interrupt frame that is mainly devoted to detecting the stall.
340 longer intervals, so that the time between (say) the first and second
354 This indicates that CPU 7 has failed to respond to a reschedule IPI.
355 The three periods (".") following the CPU number indicate that the CPU
357 that the CPU was online at the beginning of the expedited grace period
358 (otherwise the second period would have instead been "o"), and that
361 indicates that the expedited grace period has been going on for 21,119
362 jiffies. The number following the "s:" indicates that the expedited
363 grace-period sequence counter is 73. The fact that this last value is
364 odd indicates that an expedited grace period is in flight. The number
365 following "root:" is a bitmask that indicates which children of the root
366 rcu_node structure correspond to CPUs and/or tasks that are blocking the
372 tasks as well as by CPUs, and that the tasks will be indicated by PID,