Lines Matching refs:warning

16 So your kernel printed an RCU CPU stall warning.  The next question is
37 	RCU CPU stall warning messages.  Especially if you have added
54 	memory, you might see stall-warning messages.
62 	CONFIG_PREEMPT_RCU case, you might see stall-warning
79 -	Testing a workload on a fast system, tuning the stall-warning
81 	running the same workload with the same stall-warning timeout on a
119 CPU stall warning.  Note that SRCU does *not* have CPU stall warnings.
151 	issues an RCU CPU stall warning.  This time period is normally
159 	*next* stall, or the following warning for the current stall
161 	timing of the next warning for the current stall.
163 	Stall-warning messages may be enabled and disabled completely via
172 	grace period until it issues an RCU CPU stall warning. This time
183 	Stall-warning messages may be enabled and disabled completely via
192 	giving an RCU CPU stall warning message.  (This is a cpp
210 	RCU-tasks-trace stall warning intervals.  A value of zero or less
212 	stall-warning interval in seconds.  An RCU-tasks stall warning
220 	An RCU-tasks-trace stall warning starts (and continues) similarly:
268 across repeated stall-warning messages, it is possible that RCU's softirq
284 If the grace period ends just as the stall warning starts printing,
285 there will be a spurious stall-warning message, which will include
292 on how the stall warning and the grace-period initialization happen to
298 grace period has nevertheless failed to end, the stall-warning splat
311 the stall warning, as was the case in the "All QSes seen" line above,
354 If a stall lasts long enough, multiple stall-warning messages will
399 is supplied with each RCU CPU stall warning::
482    If this type of RCU CPU stall warning can be reproduced, you can