Searched refs:lockup (Results 1 – 25 of 27) 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
309 This value controls the hard lockup detector behavior when a hard310 lockup condition is detected as to whether or not to gather further322 when a hard lockup is detected.324 0 - don't panic on hard lockup325 1 - panic on hard lockup327 See Documentation/lockup-watchdogs.txt for more information. This can475 (i.e. the hard lockup detector) on x86 systems.477 0 - disable the hard lockup detector478 1 - enable the hard lockup detector480 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.
518 static int lockup; in ecard_check_lockup() local530 lockup += 1; in ecard_check_lockup()531 if (lockup > 1000000) { in ecard_check_lockup()539 lockup = 0; in ecard_check_lockup()
51 15) ``L`` if a soft lockup has previously occurred on the system.
1321 [KNL] Should the hard-lockup detector generate2698 default). To disable both hard and soft lockup detectors,2945 nosoftlockup [KNL] Disable the soft-lockup detector.2949 nowatchdog [KNL] Disable both lockup detectors, i.e.2950 soft-lockup and NMI watchdog (hard-lockup).4149 [KNL] Should the soft-lockup detector generate panics.4152 A nonzero value instructs the soft-lockup detector4153 to panic the machine when a soft-lockup occurs. This4159 [KNL] Should the soft-lockup detector generate
36 The soft and hard lockup detectors are built on top of the hrtimer and
237 lockup-watchdogs.txt238 - info on soft and hard lockup detectors (aka nmi_watchdog).
278 See also <file:Documentation/lockup-watchdogs.txt> and the SMP-HOWTO
191 lockup related problems for dma-buffers shared across multiple
194 A detected lockup causes system panic with message
77 what it believes to be lockup conditions.822 lockup has been detected. This feature is useful for824 where a lockup must be resolved ASAP.841 # hard lockup detection which runs too fast due to turbo modes.848 # lockup detector rather than the perf based detector.
179 See also <file:Documentation/lockup-watchdogs.txt> and the SMP-HOWTO
1072 * lockup detectors) and so should be last resort.
1103 * lockup detectors) and so should be last resort.
569 the correct address. Wrong address here may lead to hardware lockup.
450 If a hard lockup is detected and "NMI watchdog" is configured, the system
688 See also <file:Documentation/lockup-watchdogs.txt> and the SMP-HOWTO
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
2121 from the soft lockup watchdog. The flag is part of the pvclock structure that2127 where the guest will clear the flag: when the soft lockup watchdog timer resets2128 itself or when a soft lockup is detected. This ioctl can be called any time
