Searched refs:lockup (Results 1 – 25 of 34) 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
72 lockup-watchdogs
3 :Original: Documentation/admin-guide/lockup-watchdogs.rst60 的cpu即使在内核产生了lockup问题我们也无法检测到。不过，至少我们可以允许watchdog
69 lockup-watchdogs
359 when a hard lockup is detected.362 0 Don't panic on hard lockup.363 1 Panic on hard lockup.671 0 Disable the hard lockup detector.672 1 Enable the hard lockup detector.1413 when a soft lockup is detected.1416 0 Don't panic on soft lockup.1417 1 Panic on soft lockup.1430 1 Enable the soft lockup detector.1658 0 Disable both lockup detectors.[all …]
26 # watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [kworker/u16:3:46]
94 # [ 228.161164] watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [gpu-worker:150]
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()
81 lockup-watchdogs
99 14 _/L 16384 soft lockup occurred176 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
5 error, possibly resulting in an unrecoverable CPU lockup, when an
216 lockup related problems for dma-buffers shared across multiple
318 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
171 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
255 A detected lockup causes system panic with message
587 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
1120 * lockup detectors) and so should be last resort.
1102 * lockup detectors) and so should be last resort.
106 what it believes to be lockup conditions.1128 lockup has been detected. This feature is useful for1130 where a lockup must be resolved ASAP.1219 # hard lockup detection which runs too fast due to turbo modes.1322 that watchdogs and lockup detectors are working properly.1325 lockup, "hung task", or locking arbitrary lock for a long time.
477 If a hard lockup is detected and "NMI watchdog" is configured, the system