Result:
git-log-oneline igt_runner0 run0 runtimes0 results0.json boot0 dmesg0
| Detail | Value |
|---|---|
| Igt-Version |
IGT-Version: 1.28-g453b9df12 (x86_64) (Linux: 6.7.0-rc1-linus-v6.7-rc1-gb85ea95d0864+ x86_64) |
| Out |
Opened device: /dev/dri/card0 Starting subtest: error-state-basic Subtest error-state-basic: SUCCESS (0.013s) |
| Err |
Starting subtest: error-state-basic Subtest error-state-basic: SUCCESS (0.013s) |
| Dmesg |
<6> [106.085089] Console: switching to colour dummy device 80x25
<6> [106.085220] [IGT] i915_hangman: executing
<7> [106.089961] i915 0000:00:02.0: [drm:i915_gem_open [i915]]
<7> [106.091281] i915 0000:00:02.0: [drm:i915_drop_caches_set [i915]] Dropping caches: 0x000001dc [0x000001dc]
<7> [106.091751] i915 0000:00:02.0: [drm:i915_gem_open [i915]]
<7> [106.092534] i915 0000:00:02.0: [drm:i915_gem_open [i915]]
<5> [106.099439] i915 0000:00:02.0: [drm] rcs0 heartbeat interval adjusted to a non-default value which may cause engine resets to target innocent contexts!
<5> [106.101982] i915 0000:00:02.0: [drm] bcs0 heartbeat interval adjusted to a non-default value which may cause engine resets to target innocent contexts!
<5> [106.103521] i915 0000:00:02.0: [drm] vcs0 heartbeat interval adjusted to a non-default value which may cause engine resets to target innocent contexts!
<5> [106.105093] i915 0000:00:02.0: [drm] vecs0 heartbeat interval adjusted to a non-default value which may cause engine resets to target innocent contexts!
<6> [106.106031] [IGT] i915_hangman: starting subtest error-state-basic
<7> [106.106142] i915 0000:00:02.0: [drm:error_state_write [i915]] Resetting error state
<6> [106.109041] i915 0000:00:02.0: [drm] GPU HANG: ecode 11:0:00000000
<6> [106.109049] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
<6> [106.109053] Please file a _new_ bug report at https://gitlab.freedesktop.org/drm/intel/issues/new.
<6> [106.109056] Please see https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs for details.
<6> [106.109060] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
<6> [106.109063] The GPU crash dump is required to analyze GPU hangs, so please always attach it.
<6> [106.109067] GPU crash dump saved to /sys/class/drm/card0/error
<5> [106.114250] i915 0000:00:02.0: [drm] GT0: Resetting chip for Manually reset engine mask to 1
<7> [106.118203] i915 0000:00:02.0: [drm:error_state_write [i915]] Resetting error state
<6> [106.118981] [IGT] i915_hangman: finished subtest error-state-basic, SUCCESS
<6> [106.123369] [IGT] i915_hangman: exiting, ret=0
<7> [106.123793] i915 0000:00:02.0: [drm:i915_drop_caches_set [i915]] Dropping caches: 0x000001dc [0x000001dc]
<7> [106.125410] i915 0000:00:02.0: [drm:intel_power_well_enable [i915]] enabling DC_off
<7> [106.125886] i915 0000:00:02.0: [drm:gen9_set_dc_state.part.0 [i915]] Setting DC state from 02 to 00
<6> [106.142811] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4
<4> [106.142830] pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
<4> [106.142834] pcieport 0000:00:1c.4: device [8086:4dbc] error status/mask=00000001/00002000
<4> [106.142838] pcieport 0000:00:1c.4: [ 0] RxErr
<6> [106.144269] Console: switching to colour frame buffer device 400x112
<6> [106.169372] pcieport 0000:00:1c.4: AER: Corrected error received: 0000:02:00.0
<4> [106.169407] nvme 0000:02:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
<4> [106.169411] nvme 0000:02:00.0: device [15b7:5006] error status/mask=00000001/0000e000
<4> [106.169415] nvme 0000:02:00.0: [ 0] RxErr
|