Searched refs:lockup (Results 1 – 25 of 31) 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
3 :Original: Documentation/admin-guide/lockup-watchdogs.rst60 的cpu即使在内核产生了lockup问题我们也无法检测到。不过，至少我们可以允许watchdog
70 lockup-watchdogs
312 This value controls the hard lockup detector behavior when a hard313 lockup condition is detected as to whether or not to gather further327 when a hard lockup is detected.330 0 Don't panic on hard lockup.331 1 Panic on hard lockup.334 See Documentation/admin-guide/lockup-watchdogs.rst for more information.579 (i.e. the hard lockup detector) on x86 systems.582 0 Disable the hard lockup detector.583 1 Enable the hard lockup detector.586 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.
104 lockup-watchdogs
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()
99 lockup-watchdogs
99 14 _/L 16384 soft lockup occurred175 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
1647 [KNL] Should the hard-lockup detector generate3556 To disable both hard and soft lockup detectors,3831 nosoftlockup [KNL] Disable the soft-lockup detector.3835 nowatchdog [KNL] Disable both lockup detectors, i.e.3836 soft-lockup and NMI watchdog (hard-lockup).5671 [KNL] Should the soft-lockup detector generate panics.5674 A value of 1 instructs the soft-lockup detector5675 to panic the machine when a soft-lockup occurs. It is5681 [KNL] Should the soft-lockup detector generate6794 Set the hard lockup detector stall duration[all …]
5 error, possibly resulting in an unrecoverable CPU lockup, when an
216 lockup related problems for dma-buffers shared across multiple
280 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
106 what it believes to be lockup conditions.1056 lockup has been detected. This feature is useful for1058 where a lockup must be resolved ASAP.1068 # hard lockup detection which runs too fast due to turbo modes.1075 # lockup detector rather than the perf based detector.1166 that watchdogs and lockup detectors are working properly.1169 lockup, "hung task", or locking arbitrary lock for a long time.
170 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
234 A detected lockup causes system panic with message
613 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
1115 * lockup detectors) and so should be last resort.
1097 * lockup detectors) and so should be last resort.
535 the correct address. Wrong address here may lead to hardware lockup.
515 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