Lines Matching +full:runs +full:- +full:on

14 "softlockup_panic" (see "Documentation/admin-guide/kernel-parameters.rst" for
26 (see "Documentation/admin-guide/kernel-parameters.rst" for details).
36 The soft and hard lockup detectors are built on top of the hrtimer and
41 A periodic hrtimer runs to generate interrupts and kick the watchdog
43 (compile-time initialized to 10 and configurable through sysctl of the
47 generate a kernel warning or call panic, depending on the
64 event. The right value for a particular environment is a trade-off
67 By default, the watchdog runs on all online cores.  However, on a
68 kernel configured with NO_HZ_FULL, by default the watchdog runs only
69 on the housekeeping cores, not the cores specified in the "nohz_full"
70 boot argument.  If we allowed the watchdog to run by default on
73 from protecting the user code on those cores from the kernel.
74 Of course, disabling it by default on the nohz_full cores means that
77 to continue to run on the housekeeping (non-tickless) cores means
78 that we will continue to detect lockups properly on those cores.
83 kernel seems to be hanging on the nohz_full cores.