Home
last modified time | relevance | path

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

12

/openbmc/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
/openbmc/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.rst70 lockup-watchdogs
/openbmc/linux/Documentation/admin-guide/sysctl/
H A Dkernel.rst315 This value controls the hard lockup detector behavior when a hard
316 lockup condition is detected as to whether or not to gather further
330 when a hard lockup is detected.
333 0 Don't panic on hard lockup.
334 1 Panic on hard lockup.
337 See Documentation/admin-guide/lockup-watchdogs.rst for more information.
630 (i.e. the hard lockup detector) on x86 systems.
633 0 Disable the hard lockup detector.
634 1 Enable the hard lockup detector.
637 The hard lockup detector monitors each CPU for its ability to respond to
[all …]
/openbmc/linux/drivers/bcma/
H A DREADME9 as standard AMBA device. Reading it's CID or PID can cause machine lockup.
/openbmc/linux/Documentation/translations/zh_TW/admin-guide/
H A Dindex.rst104 lockup-watchdogs
/openbmc/linux/arch/alpha/
H A DKconfig.debug22 hard lockup.
/openbmc/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()
543 lockup = 0; in ecard_check_lockup()
/openbmc/linux/Documentation/admin-guide/
H A Dindex.rst110 lockup-watchdogs
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.txt1723 [KNL] Should the hard-lockup detector generate
3680 To disable both hard and soft lockup detectors,
3925 nosoftlockup [KNL] Disable the soft-lockup detector.
3970 nowatchdog [KNL] Disable both lockup detectors, i.e.
3971 soft-lockup and NMI watchdog (hard-lockup).
5920 [KNL] Should the soft-lockup detector generate panics.
5923 A value of 1 instructs the soft-lockup detector
5924 to panic the machine when a soft-lockup occurs. It is
5930 [KNL] Should the soft-lockup detector generate
7125 Set the hard lockup detector stall duration
[all …]
/openbmc/docs/designs/
H A Dnmi-dbus-interface.md94 module driver to create hard lockup/hang and then check the scenario is good.
H A Dbmc-service-failure-debug-and-recovery.md140 lockup conditions can be configured to trigger panics, which in-turn trigger
189 detecting a kernel lockup have failed. Had they not failed, we would have
192 experience. Given this and the kernel's own lockup detection and data collection
/openbmc/u-boot/doc/
H A DREADME.xtensa86 Accessing first type of invalid addresses may result in hardware lockup,
/openbmc/linux/Documentation/admin-guide/hw-vuln/
H A Dmultihit.rst5 error, possibly resulting in an unrecoverable CPU lockup, when an
/openbmc/linux/arch/parisc/
H A DKconfig311 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
/openbmc/linux/drivers/base/
H A DKconfig216 lockup related problems for dma-buffers shared across multiple
/openbmc/linux/arch/sparc/
H A DKconfig173 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
/openbmc/linux/kernel/power/
H A DKconfig233 A detected lockup causes system panic with message
/openbmc/linux/lib/
H A DKconfig.debug106 what it believes to be lockup conditions.
1038 lockup has been detected. This feature is useful for
1040 where a lockup must be resolved ASAP.
1129 # hard lockup detection which runs too fast due to turbo modes.
1221 that watchdogs and lockup detectors are working properly.
1224 lockup, "hung task", or locking arbitrary lock for a long time.
/openbmc/linux/arch/sh/
H A DKconfig589 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
/openbmc/linux/arch/arm/boot/dts/samsung/
H A Dexynos5420-peach-pit.dts1119 * lockup detectors) and so should be last resort.
H A Dexynos5800-peach-pi.dts1101 * lockup detectors) and so should be last resort.

12