Home
last modified time | relevance | path

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

12

/linux/drivers/video/fbdev/nvidia/
H A Dnv_accel.c80 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()
H A Dnv_type.h121 int lockup; member
/linux/Documentation/translations/zh_CN/admin-guide/
H A Dlockup-watchdogs.rst3 :Original: Documentation/admin-guide/lockup-watchdogs.rst
60 的cpu即使在内核产生了lockup问题我们也无法检测到。不过，至少我们可以允许watchdog
H A Dindex.rst69 lockup-watchdogs
/linux/Documentation/translations/zh_TW/admin-guide/
H A Dlockup-watchdogs.rst3 :Original: Documentation/admin-guide/lockup-watchdogs.rst
60 的cpu即使在內核產生了lockup問題我們也無法檢測到。不過，至少我們可以允許watchdog
H A Dindex.rst72 lockup-watchdogs
/linux/Documentation/admin-guide/sysctl/
H A Dkernel.rst344 This value controls the hard lockup detector behavior when a hard
345 lockup condition is detected as to whether or not to gather further
359 when a hard lockup is detected.
362 0 Don't panic on hard lockup.
363 1 Panic on hard lockup.
366 See Documentation/admin-guide/lockup-watchdogs.rst for more information.
668 (i.e. the hard lockup detector) on x86 systems.
671 0 Disable the hard lockup detector.
672 1 Enable the hard lockup detector.
675 The hard lockup detector monitors each CPU for its ability to respond to
[all …]
/linux/drivers/gpu/drm/ci/xfails/
H A Dmsm-apq8096-skips.txt26 # watchdog: BUG: soft lockup - CPU#0 stuck for 26s! [kworker/u16:3:46]
/linux/drivers/bcma/
H A DREADME9 as standard AMBA device. Reading it's CID or PID can cause machine lockup.
/linux/arch/alpha/
H A DKconfig.debug22 hard lockup.
/linux/arch/arm/mach-rpc/
H A Decard.c522 static int lockup; in ecard_check_lockup() local
534 lockup += 1; in ecard_check_lockup()
535 if (lockup > 1000000) { in ecard_check_lockup()
536 printk(KERN_ERR "\nInterrupt lockup detected - " in ecard_check_lockup()
543 lockup = 0; in ecard_check_lockup()
/linux/Documentation/admin-guide/
H A Dtainted-kernels.rst99 14 _/L 16384 soft lockup occurred
175 14) ``L`` if a soft lockup has previously occurred on the system.
H A Dlockup-watchdogs.rst36 The soft and hard lockup detectors are built on top of the hrtimer and
H A Dkernel-parameters.txt1792 [KNL] Should the hard-lockup detector generate
4015 To disable both hard and soft lockup detectors,
4243 nosoftlockup [KNL] Disable the soft-lockup detector.
4291 nowatchdog [KNL] Disable both lockup detectors, i.e.
4292 soft-lockup and NMI watchdog (hard-lockup).
6533 [KNL] Should the soft-lockup detector generate panics.
6536 A value of 1 instructs the soft-lockup detector
6537 to panic the machine when a soft-lockup occurs. It is
6543 [KNL] Should the soft-lockup detector generate
7848 Set the hard lockup detector stall duration
[all …]
/linux/Documentation/admin-guide/hw-vuln/
H A Dmultihit.rst5 error, possibly resulting in an unrecoverable CPU lockup, when an
/linux/drivers/base/
H A DKconfig216 lockup related problems for dma-buffers shared across multiple
/linux/arch/sparc/
H A DKconfig171 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
/linux/arch/arm/boot/dts/samsung/
H A Dexynos5420-peach-pit.dts1120 * lockup detectors) and so should be last resort.
H A Dexynos5800-peach-pi.dts1102 * lockup detectors) and so should be last resort.
/linux/lib/
H A DKconfig.debug106 what it believes to be lockup conditions.
1109 lockup has been detected. This feature is useful for
1111 where a lockup must be resolved ASAP.
1200 # hard lockup detection which runs too fast due to turbo modes.
1292 that watchdogs and lockup detectors are working properly.
1295 lockup, "hung task", or locking arbitrary lock for a long time.
/linux/Documentation/scsi/
H A DChangeLog.megaraid517 vi. Fix bug in the management module, which causes a system lockup when the
/linux/arch/xtensa/
H A DKconfig555 the correct address. Wrong address here may lead to hardware lockup.
/linux/Documentation/driver-api/
H A Dlibata.rst799 symptoms ranging from device ICRC error to random device lockup, and,
/linux/arch/powerpc/
H A DKconfig98 selected via the generic lockup detector menu which is why we
/linux/Documentation/kernel-hacking/
H A Dlocking.rst894 This complete lockup is easy to diagnose: on SMP boxes the watchdog

12