Searched refs:lockup (Results 1 – 25 of 29) sorted by relevance
12
| /kernel/linux/linux-5.10/drivers/video/fbdev/nvidia/ |
| D | nv_accel.c | 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()
|
| D | nv_type.h | 121 int lockup; member
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/sysctl/ |
| D | kernel.rst | 306 This value controls the hard lockup detector behavior when a hard
307 lockup condition is detected as to whether or not to gather further
321 when a hard lockup is detected.
324 0 Don't panic on hard lockup.
325 1 Panic on hard lockup.
328 See :doc:`/admin-guide/lockup-watchdogs` for more information.
567 (i.e. the hard lockup detector) on x86 systems.
570 0 Disable the hard lockup detector.
571 1 Enable the hard lockup detector.
574 The hard lockup detector monitors each CPU for its ability to respond to
[all …]
|
| /kernel/linux/linux-5.10/drivers/bcma/ |
| D | README | 9 as standard AMBA device. Reading it's CID or PID can cause machine lockup.
|
| /kernel/linux/linux-5.10/Documentation/translations/zh_CN/admin-guide/ |
| D | index.rst | 93 lockup-watchdogs
|
| /kernel/linux/linux-5.10/arch/alpha/ |
| D | Kconfig.debug | 22 hard lockup.
|
| /kernel/linux/linux-5.10/arch/arm/mach-rpc/ |
| D | ecard.c | 522 static int lockup; in ecard_check_lockup() local
534 lockup += 1; in ecard_check_lockup()
535 if (lockup > 1000000) { in ecard_check_lockup()
543 lockup = 0; in ecard_check_lockup()
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | index.rst | 96 lockup-watchdogs
|
| D | tainted-kernels.rst | 99 14 _/L 16384 soft lockup occurred
155 14) ``L`` if a soft lockup has previously occurred on the system.
|
| D | lockup-watchdogs.rst | 36 The soft and hard lockup detectors are built on top of the hrtimer and
|
| D | kernel-parameters.txt | 1493 [KNL] Should the hard-lockup detector generate
3165 To disable both hard and soft lockup detectors,
3430 nosoftlockup [KNL] Disable the soft-lockup detector.
3434 nowatchdog [KNL] Disable both lockup detectors, i.e.
3435 soft-lockup and NMI watchdog (hard-lockup).
4977 [KNL] Should the soft-lockup detector generate panics.
4980 A value of 1 instructs the soft-lockup detector
4981 to panic the machine when a soft-lockup occurs. It is
4987 [KNL] Should the soft-lockup detector generate
5952 Set the hard lockup detector stall duration
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/hw-vuln/ |
| D | multihit.rst | 5 error, possibly resulting in an unrecoverable CPU lockup, when an
|
| /kernel/linux/linux-5.10/drivers/base/ |
| D | Kconfig | 202 lockup related problems for dma-buffers shared across multiple
|
| /kernel/linux/linux-5.10/arch/parisc/ |
| D | Kconfig | 290 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
|
| /kernel/linux/linux-5.10/lib/ |
| D | Kconfig.debug | 95 what it believes to be lockup conditions.
950 lockup has been detected. This feature is useful for
952 where a lockup must be resolved ASAP.
969 # hard lockup detection which runs too fast due to turbo modes.
976 # lockup detector rather than the perf based detector.
1081 that watchdogs and lockup detectors are working properly.
1084 lockup, "hung task", or locking arbitrary lock for a long time.
|
| /kernel/linux/linux-5.10/kernel/power/ |
| D | Kconfig | 216 A detected lockup causes system panic with message
|
| /kernel/linux/linux-5.10/arch/sparc/ |
| D | Kconfig | 180 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | exynos5800-peach-pi.dts | 1093 * lockup detectors) and so should be last resort.
|
| D | exynos5420-peach-pit.dts | 1111 * lockup detectors) and so should be last resort.
|
| /kernel/linux/linux-5.10/arch/sh/ |
| D | Kconfig | 620 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/kdump/ |
| D | kdump.rst | 470 If a hard lockup is detected and "NMI watchdog" is configured, the system
|
| /kernel/linux/linux-5.10/arch/xtensa/ |
| D | Kconfig | 447 the correct address. Wrong address here may lead to hardware lockup.
|
| /kernel/linux/linux-5.10/Documentation/scsi/ |
| D | ChangeLog.megaraid | 517 vi. Fix bug in the management module, which causes a system lockup when the
|
| /kernel/linux/linux-5.10/arch/powerpc/ |
| D | Kconfig | 90 seleted via the generic lockup detector menu which is why we
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | libata.rst | 836 symptoms ranging from device ICRC error to random device lockup, and,
|
12