Searched refs:lockup (Results 1 – 25 of 28) sorted by relevance
12
80 par->lockup = 1; in nvidiafb_safe_mode()124 while (par->dmaFree < size && --count && !par->lockup) { in NVDmaWait()140 par->lockup = 1; in NVDmaWait()289 if (!par->lockup) in nvidiafb_sync()292 if (!par->lockup) in nvidiafb_sync()305 if (par->lockup) { in nvidiafb_copyarea()326 if (par->lockup) { in nvidiafb_fillrect()414 if (image->depth == 1 && !par->lockup) in nvidiafb_imageblit()
121 int lockup; member
311 This value controls the hard lockup detector behavior when a hard312 lockup condition is detected as to whether or not to gather further325 when a hard lockup is detected.327 0 - don't panic on hard lockup328 1 - panic on hard lockup330 See Documentation/admin-guide/lockup-watchdogs.rst for more information. This can479 (i.e. the hard lockup detector) on x86 systems.481 0 - disable the hard lockup detector483 1 - enable the hard lockup detector485 The hard lockup detector monitors each CPU for its ability to respond to[all …]
9 as standard AMBA device. Reading it's CID or PID can cause machine lockup.
22 hard lockup.
522 static int lockup; in ecard_check_lockup() local534 lockup += 1; in ecard_check_lockup()535 if (lockup > 1000000) { in ecard_check_lockup()543 lockup = 0; in ecard_check_lockup()
107 lockup-watchdogs
99 14 _/L 16384 soft lockup occurred155 14) ``L`` if a soft lockup has previously occurred on the system.
36 The soft and hard lockup detectors are built on top of the hrtimer and
1371 [KNL] Should the hard-lockup detector generate2909 To disable both hard and soft lockup detectors,3167 nosoftlockup [KNL] Disable the soft-lockup detector.3171 nowatchdog [KNL] Disable both lockup detectors, i.e.3172 soft-lockup and NMI watchdog (hard-lockup).4423 [KNL] Should the soft-lockup detector generate panics.4426 A nonzero value instructs the soft-lockup detector4427 to panic the machine when a soft-lockup occurs. This4433 [KNL] Should the soft-lockup detector generate5318 Set the hard lockup detector stall duration[all …]
5 error, possibly resulting in an unrecoverable CPU lockup, when an
197 lockup related problems for dma-buffers shared across multiple
281 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
204 A detected lockup causes system panic with message
95 what it believes to be lockup conditions.846 lockup has been detected. This feature is useful for848 where a lockup must be resolved ASAP.865 # hard lockup detection which runs too fast due to turbo modes.872 # lockup detector rather than the perf based detector.
183 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
1076 * lockup detectors) and so should be last resort.
1107 * lockup detectors) and so should be last resort.
611 the correct address. Wrong address here may lead to hardware lockup.
681 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
470 If a hard lockup is detected and "NMI watchdog" is configured, the system
517 vi. Fix bug in the management module, which causes a system lockup when the
91 seleted via the generic lockup detector menu which is why we
836 symptoms ranging from device ICRC error to random device lockup, and,
900 This complete lockup is easy to diagnose: on SMP boxes the watchdog
