Home
last modified time | relevance | path

Searched full:hang (Results 1 – 25 of 738) sorted by relevance

12345678910>>...30

/linux-6.14.4/tools/perf/tests/shell/
Dtest_arm_spe_fork.sh2 # Check Arm SPE doesn't hang when there are forks
44 echo "SPE hang test: FAIL"
47 echo "SPE hang test: PASS"
/linux-6.14.4/drivers/gpu/drm/i915/gt/
Dselftest_hangcheck.c32 struct hang { struct
41 static int hang_init(struct hang *h, struct intel_gt *gt) in hang_init() argument
104 hang_create_request(struct hang *h, struct intel_engine_cs *engine) in hang_create_request()
253 static u32 hws_seqno(const struct hang *h, const struct i915_request *rq) in hws_seqno()
258 static void hang_fini(struct hang *h) in hang_fini()
274 static bool wait_until_running(struct hang *h, struct i915_request *rq) in wait_until_running()
290 struct hang h; in igt_hang_sanitycheck()
443 /* Engine level resets are triggered by GuC when a hang in igt_reset_nop_engine()
689 struct hang h; in __igt_reset_engine()
745 pr_err("[%s] Create hang request failed: %d!\n", in __igt_reset_engine()
[all …]
Dselftest_lrc.c1793 struct i915_request *hang; in __lrc_garbage() local
1800 hang = garbage(ce, prng); in __lrc_garbage()
1801 if (IS_ERR(hang)) { in __lrc_garbage()
1802 err = PTR_ERR(hang); in __lrc_garbage()
1806 if (wait_for_submit(engine, hang, HZ / 2)) { in __lrc_garbage()
1807 i915_request_put(hang); in __lrc_garbage()
1813 garbage_reset(engine, hang); in __lrc_garbage()
1816 if (!hang->fence.error) { in __lrc_garbage()
1817 i915_request_put(hang); in __lrc_garbage()
1824 if (i915_request_wait(hang, 0, HZ / 2) < 0) { in __lrc_garbage()
[all …]
/linux-6.14.4/drivers/net/ethernet/intel/ice/devlink/
Dhealth.h34 * @tx_hang_buf: pre-allocated place to put info for Tx hang reporter from
36 * @tx_ring: ring that the hang occurred on
39 * @vsi_num: VSI owning the queue that the hang occurred on
/linux-6.14.4/drivers/gpu/drm/i915/
DKconfig91 bool "Enable capturing GPU state following a hang"
95 This option enables capturing the GPU state when a hang is detected.
97 Please report any hang for triaging according to:
109 selected and causes any error state captured upon a GPU hang
/linux-6.14.4/drivers/gpu/drm/xe/
Dxe_devcoredump_types.h29 /** @process_name: Name of process that triggered this gpu hang */
31 /** @pid: Process id of process that triggered this gpu hang */
85 /** @captured: The snapshot of the first hang has already been taken */
Dxe_devcoredump.c43 * **Snapshot at hang**:
45 * the hang happened. Due to the driver recovering from resets/crashes, it may
60 * In general, the first hang is the most critical one since the following
61 * hangs can be a consequence of the initial hang. For this reason a snapshot
400 * 120s' kernel hang check feature from firing when printing to a slow target
/linux-6.14.4/drivers/gpu/drm/ci/xfails/
Dmsm-sc7180-trogdor-kingoftown-fails.txt11 kms_flip@flip-vs-modeset-vs-hang,Fail
12 kms_flip@flip-vs-panning-vs-hang,Fail
Dmsm-sc7180-trogdor-lazor-limozeen-fails.txt11 kms_flip@flip-vs-modeset-vs-hang,Fail
12 kms_flip@flip-vs-panning-vs-hang,Fail
Dmsm-sdm845-fails.txt22 kms_flip@flip-vs-modeset-vs-hang,Fail
23 kms_flip@flip-vs-panning-vs-hang,Fail
Dmediatek-mt8173-fails.txt23 kms_flip@flip-vs-modeset-vs-hang,Fail
24 kms_flip@flip-vs-panning-vs-hang,Fail
Dvkms-none-fails.txt21 kms_flip@flip-vs-modeset-vs-hang,Fail
22 kms_flip@flip-vs-panning-vs-hang,Fail
Damdgpu-stoney-fails.txt34 kms_flip@flip-vs-modeset-vs-hang,Fail
35 kms_flip@flip-vs-panning-vs-hang,Fail
Di915-amly-flakes.txt13 i915_hangman@gt-engine-hang
41 i915_hangman@engine-engine-hang
Drockchip-rk3399-fails.txt46 kms_flip@flip-vs-modeset-vs-hang,Fail
49 kms_flip@flip-vs-panning-vs-hang,Fail
Di915-kbl-flakes.txt6 prime_busy@hang
/linux-6.14.4/drivers/gpu/drm/amd/amdgpu/
Damdgpu_reset.c325 snprintf(buf, len, "job hang on ring:%s", in amdgpu_reset_get_desc()
328 strscpy(buf, "job hang", len); in amdgpu_reset_get_desc()
335 strscpy(buf, "MES hang", len); in amdgpu_reset_get_desc()
338 strscpy(buf, "HWS hang", len); in amdgpu_reset_get_desc()
/linux-6.14.4/arch/sparc/kernel/
Dleon_pmc.c52 /* Interrupts need to be enabled to not hang the CPU */ in pmc_leon_idle_fixup()
70 /* Interrupts need to be enabled to not hang the CPU */ in pmc_leon_idle()
/linux-6.14.4/drivers/watchdog/
DiTCO_vendor_support.c64 * If BIOS or CPU fail which may cause SMI hang, then system will
72 * So, if the watchdog timer is 20 seconds, then the maximum hang
73 * time is about 40 seconds, and the minimum hang time is about
/linux-6.14.4/drivers/net/wireless/mediatek/mt76/mt7603/
Ddebugfs.c10 [RESET_CAUSE_TX_HANG] = "TX hang", in mt7603_reset_read()
15 [RESET_CAUSE_MCU_HANG] = "MCU hang", in mt7603_reset_read()
/linux-6.14.4/drivers/gpu/drm/amd/include/
Ddm_pp_interface.h94 /* Controller Index of primary display - used in MCLK SMC switching hang
97 /* htotal*1000/pixelclk - used in MCLK SMC switching hang SW Workaround*/
/linux-6.14.4/tools/testing/selftests/perf_events/
Dremove_on_exec.c162 while (signal_count == tmp); /* Should not hang! */ in TEST_F()
195 while (signal_count == tmp); /* Should not hang! */ in TEST_F()
245 /* Should hang here until killed. */ in exec_child()
/linux-6.14.4/drivers/tty/hvc/
Dhvc_iucv.c216 * hang up (that is issued by the HVC layer).
230 * HVC layer to hang up the tty device. */ in hvc_iucv_write()
556 * hvc_iucv_hangup() - Sever IUCV path and schedule hvc tty hang up
561 * The hang-up occurs only if an IUCV communication path is established;
562 * otherwise there is no need to hang up the terminal device.
564 * The IUCV HVC hang-up is separated into two steps:
568 * IUCV_SEVERED state causes the tty hang-up in the HVC layer.
573 * the HVC layer to hang up the tty and, if so, wake up the HVC thread
577 * Hang-up: 1. do_tty_hangup() replaces file ops (= hung_up_tty_fops)
650 * client if we disconnect on hang up) */ in hvc_iucv_notifier_hangup()
[all …]
/linux-6.14.4/drivers/gpu/drm/amd/display/dc/
Ddm_services_types.h206 /*Controller Index of primary display - used in MCLK SMC switching hang
209 /*htotal*1000/pixelclk - used in MCLK SMC switching hang SW Workaround*/
/linux-6.14.4/Documentation/sound/cards/
Dvia82xx-mixer.rst6 Setting it to ``Input2`` on such boards will cause recording to hang, or fail

12345678910>>...30