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
330 when a hard lockup is detected.333 0 Don't panic on hard lockup.334 1 Panic on hard lockup.604 0 Disable the hard lockup detector.605 1 Enable the hard lockup detector.1320 when a soft lockup is detected.1323 0 Don't panic on soft lockup.1324 1 Panic on soft lockup.1337 1 Enable the soft lockup detector.1574 0 Disable both lockup detectors.[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()
110 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
1648 [KNL] Should the hard-lockup detector generate3567 To disable both hard and soft lockup detectors,3863 nosoftlockup [KNL] Disable the soft-lockup detector.3867 nowatchdog [KNL] Disable both lockup detectors, i.e.3868 soft-lockup and NMI watchdog (hard-lockup).5707 A value of 1 instructs the soft-lockup detector5708 to panic the machine when a soft-lockup occurs. It is5714 [KNL] Should the soft-lockup detector generate6886 Set the hard lockup detector stall duration6887 threshold in seconds. The soft lockup detector[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
170 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
106 what it believes to be lockup conditions.1022 lockup has been detected. This feature is useful for1024 where a lockup must be resolved ASAP.1034 # hard lockup detection which runs too fast due to turbo modes.1041 # lockup detector rather than the perf based detector.1132 that watchdogs and lockup detectors are working properly.1135 lockup, "hung task", or locking arbitrary lock for a long time.
233 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
Completed in 57 milliseconds