Home
last modified time | relevance | path

Searched refs:lockup (Results 1 – 21 of 21) sorted by relevance

/linux-4.1.27/drivers/video/fbdev/nvidia/
Dnv_accel.c78 par->lockup = 1; in nvidiafb_safe_mode()
122 while (par->dmaFree < size && --count && !par->lockup) { in NVDmaWait()
138 par->lockup = 1; in NVDmaWait()
287 if (!par->lockup) in nvidiafb_sync()
290 if (!par->lockup) in nvidiafb_sync()
303 if (par->lockup) { in nvidiafb_copyarea()
324 if (par->lockup) { in nvidiafb_fillrect()
412 if (image->depth == 1 && !par->lockup) in nvidiafb_imageblit()
Dnv_type.h120 int lockup; member
/linux-4.1.27/Documentation/sysctl/
Dkernel.txt423 (i.e. the hard lockup detector) on x86 systems.
425 0 - disable the hard lockup detector
426 1 - enable the hard lockup detector
428 The hard lockup detector monitors each CPU for its ability to respond to
814 This value controls the soft lockup detector thread's behavior
815 when a soft lockup condition is detected as to whether or not
830 This parameter can be used to control the soft lockup detector.
832 0 - disable the soft lockup detector
833 1 - enable the soft lockup detector
835 The soft lockup detector monitors CPUs for threads that are hogging the CPUs
[all …]
/linux-4.1.27/drivers/bcma/
DREADME9 as standard AMBA device. Reading it's CID or PID can cause machine lockup.
/linux-4.1.27/arch/alpha/
DKconfig.debug24 hard lockup.
/linux-4.1.27/arch/arm/mach-rpc/
Decard.c520 static int lockup; in ecard_check_lockup() local
532 lockup += 1; in ecard_check_lockup()
533 if (lockup > 1000000) { in ecard_check_lockup()
541 lockup = 0; in ecard_check_lockup()
/linux-4.1.27/Documentation/
Dlockup-watchdogs.txt34 The soft and hard lockup detectors are built on top of the hrtimer and
D00-INDEX290 lockup-watchdogs.txt
291 - info on soft and hard lockup detectors (aka nmi_watchdog).
Doops-tracing.txt271 15: 'L' if a soft lockup has previously occurred on the system.
Dkernel-parameters.txt2495 nosoftlockup [KNL] Disable the soft-lockup detector.
2503 nowatchdog [KNL] Disable both lockup detectors, i.e.
2504 soft-lockup and NMI watchdog (hard-lockup).
3436 [KNL] Should the soft-lockup detector generate panics.
3440 [KNL] Should the soft-lockup detector generate
/linux-4.1.27/arch/blackfin/
DKconfig.debug212 bool "Enable NMI watchdog to help debugging lockup on SMP"
218 information. This information can be used to debug the lockup.
/linux-4.1.27/kernel/power/
DKconfig183 A detected lockup causes system panic with message
/linux-4.1.27/drivers/base/
DKconfig247 lockup related problems for dma-buffers shared across multiple
/linux-4.1.27/arch/xtensa/
DKconfig450 the correct address. Wrong address here may lead to hardware lockup.
/linux-4.1.27/lib/
DKconfig.debug45 what it believes to be lockup conditions.
701 The frequency of hrtimer and NMI events and the soft and hard lockup
738 lockup has been detected. This feature is useful for
740 where a lockup must be resolved ASAP.
/linux-4.1.27/arch/arm/boot/dts/
Dexynos5420-peach-pit.dts1058 * lockup detectors) and so should be last resort.
Dexynos5800-peach-pi.dts1021 * lockup detectors) and so should be last resort.
/linux-4.1.27/Documentation/kdump/
Dkdump.txt428 If a hard lockup is detected and "NMI watchdog" is configured, the system
/linux-4.1.27/Documentation/scsi/
DChangeLog.megaraid517 vi. Fix bug in the management module, which causes a system lockup when the
DChangeLog.1992-199773 device lockup simulation via /proc/scsi interface.
/linux-4.1.27/Documentation/virtual/kvm/
Dapi.txt2097 from the soft lockup watchdog. The flag is part of the pvclock structure that
2103 where the guest will clear the flag: when the soft lockup watchdog timer resets
2104 itself or when a soft lockup is detected. This ioctl can be called any time