Lines Matching refs:to

5 The Linux kernel can act as a watchdog to detect both soft and hard
8 A 'softlockup' is defined as a bug that causes the kernel to loop in
10 details), without giving other tasks a chance to run. The current
12 will stay locked up. Alternatively, the kernel can be configured to
18 A 'hardlockup' is defined as a bug that causes the CPU to loop in
20 details), without letting other interrupts have a chance to run.
21 Similarly to the softlockup case, the current stack trace is displayed
30 to cause the system to reboot automatically after a specified amount
40 A periodic hrtimer runs to generate interrupts and kick the watchdog
42 (compile-time initialized to 10 and configurable through sysctl of the
43 same name) seconds to check for hardlockups. If any CPU in the system
53 will dump useful debug information to the system log, after which it
54 will call panic if it was instructed to do so or resume execution of
58 two or three chances to generate an interrupt before the hardlockup
62 administrators to configure the period of the hrtimer and the perf
64 between fast response to lockups and detection overhead.
69 boot argument.  If we allowed the watchdog to run by default on
70 the "nohz_full" cores, we would have to run timer ticks to activate
75 able to detect if they lock up.  However, allowing the watchdog
76 to continue to run on the housekeeping (non-tickless) cores means
77 that we will continue to detect lockups properly on those cores.
82 kernel seems to be hanging on the nohz_full cores.