Home
last modified time | relevance | path

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

12

/OK3568_Linux_fs/kernel/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
/OK3568_Linux_fs/kernel/Documentation/admin-guide/sysctl/
H A Dkernel.rst306 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 …]
/OK3568_Linux_fs/kernel/Documentation/translations/zh_CN/admin-guide/
H A Dindex.rst93 lockup-watchdogs
/OK3568_Linux_fs/kernel/drivers/bcma/
H A DREADME9 as standard AMBA device. Reading it's CID or PID can cause machine lockup.
/OK3568_Linux_fs/kernel/arch/alpha/
H A DKconfig.debug22 hard lockup.
/OK3568_Linux_fs/kernel/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()
/OK3568_Linux_fs/kernel/Documentation/admin-guide/
H A Dindex.rst96 lockup-watchdogs
H A Dtainted-kernels.rst99 14 _/L 16384 soft lockup occurred
155 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.txt1529 [KNL] Should the hard-lockup detector generate
3246 To disable both hard and soft lockup detectors,
3525 nosoftlockup [KNL] Disable the soft-lockup detector.
3529 nowatchdog [KNL] Disable both lockup detectors, i.e.
3530 soft-lockup and NMI watchdog (hard-lockup).
5097 [KNL] Should the soft-lockup detector generate panics.
5100 A value of 1 instructs the soft-lockup detector
5101 to panic the machine when a soft-lockup occurs. It is
5107 [KNL] Should the soft-lockup detector generate
6078 Set the hard lockup detector stall duration
[all …]
/OK3568_Linux_fs/u-boot/doc/
H A DREADME.xtensa86 Accessing first type of invalid addresses may result in hardware lockup,
/OK3568_Linux_fs/kernel/Documentation/admin-guide/hw-vuln/
H A Dmultihit.rst5 error, possibly resulting in an unrecoverable CPU lockup, when an
/OK3568_Linux_fs/kernel/drivers/base/
H A DKconfig204 lockup related problems for dma-buffers shared across multiple
/OK3568_Linux_fs/kernel/arch/parisc/
H A DKconfig291 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
/OK3568_Linux_fs/kernel/lib/
H A DKconfig.debug99 what it believes to be lockup conditions.
957 lockup has been detected. This feature is useful for
959 where a lockup must be resolved ASAP.
976 # hard lockup detection which runs too fast due to turbo modes.
983 # lockup detector rather than the perf based detector.
1099 that watchdogs and lockup detectors are working properly.
1102 lockup, "hung task", or locking arbitrary lock for a long time.
/OK3568_Linux_fs/kernel/kernel/power/
H A DKconfig216 A detected lockup causes system panic with message
/OK3568_Linux_fs/kernel/arch/sparc/
H A DKconfig180 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
/OK3568_Linux_fs/kernel/arch/arm/boot/dts/
H A Dexynos5800-peach-pi.dts1093 * lockup detectors) and so should be last resort.
H A Dexynos5420-peach-pit.dts1111 * lockup detectors) and so should be last resort.
/OK3568_Linux_fs/kernel/arch/sh/
H A DKconfig620 See also <file:Documentation/admin-guide/lockup-watchdogs.rst> and the SMP-HOWTO
/OK3568_Linux_fs/kernel/Documentation/admin-guide/kdump/
H A Dkdump.rst470 If a hard lockup is detected and "NMI watchdog" is configured, the system
/OK3568_Linux_fs/kernel/arch/xtensa/
H A DKconfig447 the correct address. Wrong address here may lead to hardware lockup.
/OK3568_Linux_fs/kernel/Documentation/scsi/
H A DChangeLog.megaraid517 vi. Fix bug in the management module, which causes a system lockup when the
/OK3568_Linux_fs/kernel/arch/powerpc/
H A DKconfig90 seleted via the generic lockup detector menu which is why we

12