igt@i915_selftest@live@* - dmesg-warn - *ERROR* GT0: GUC: Bad context sched_state 0x0, ctx_id *

https://gfx-ci.igk.intel.com/cibuglog-ng/testresult/1810586670?query_key=37f5ed515722eef860b023637bc270ac30caf2ce

<6> [582.739120] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
<6> [582.740989] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.20.0
<7> [582.749596] i915 0000:00:02.0: [drm:intel_guc_fw_upload [i915]] GT0: GUC: init took 7ms, freq = 2250MHz, before = 2250MHz, status = 0x8002F034, count = 0, ret = 0
<7> [582.750197] i915 0000:00:02.0: [drm:guc_enable_communication [i915]] GT0: GUC: communication enabled
<6> [582.753248] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
<6> [582.753250] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
<6> [582.754623] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.20.0
<7> [582.764604] i915 0000:00:02.0: [drm:intel_guc_fw_upload [i915]] GT0: GUC: init took 8ms, freq = 2250MHz, before = 1050MHz, status = 0x8002F034, count = 0, ret = 0
<7> [582.765209] i915 0000:00:02.0: [drm:guc_enable_communication [i915]] GT0: GUC: communication enabled
<6> [582.767915] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
<6> [582.767917] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
<3> [582.769257] i915 0000:00:02.0: [drm] *ERROR* GT0: GUC: Bad context sched_state 0x0, ctx_id 4099
<3> [582.769501] i915 0000:00:02.0: [drm] *ERROR* GT0: GUC: CT: Failed to process request 1002 (-EPROTO)
<3> [582.769507] i915 0000:00:02.0: [drm] *ERROR* GT0: GUC: CT: Failed to process CT message (-EPROTO) 03 00 00 00 02 10 00 90 03 10 00 00 01 00 00 00
<6> [582.769643] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.20.0
<7> [582.777592] i915 0000:00:02.0: [drm:intel_guc_fw_upload [i915]] GT0: GUC: init took 7ms, freq = 2250MHz, before = 2250MHz, status = 0x8002F034, count = 0, ret = 0
<7> [582.778196] i915 0000:00:02.0: [drm:guc_enable_communication [i915]] GT0: GUC: communication enabled
<6> [582.781300] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
<6> [582.781301] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
<6> [582.783015] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.20.0
<7> [582.791592] i915 0000:00:02.0: [drm:intel_guc_fw_upload [i915]] GT0: GUC: init took 7ms, freq = 2250MHz, before = 2250MHz, status = 0x8002F034, count = 0, ret = 0
<7> [582.792215] i915 0000:00:02.0: [drm:guc_enable_communication [i915]] GT0: GUC: communication enabled
<6> [582.795274] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
<6> [582.795276] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
<6> [582.797044] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.20.0
<7> [582.805592] i915 0000:00:02.0: [drm:intel_guc_fw_upload [i915]] GT0: GUC: init took 7ms, freq = 2250MHz, before = 2250MHz, status = 0x8002F034, count = 0, ret = 0
<7> [582.806217] i915 0000:00:02.0: [drm:guc_enable_communication [i915]] GT0: GUC: communication enabled
<6> [582.809071] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
<6> [582.809074] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
<6> [582.810861] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.20.0
<7> [582.820597] i915 0000:00:02.0: [drm:intel_guc_fw_upload [i915]] GT0: GUC: init took 8ms, freq = 2250MHz, before = 1100MHz, status = 0x8002F034, count = 0, ret = 0

added BAT_BUG feature: GEM platform: ARL_S platform: MTL_P labels

The CI Bug Log issue associated to this bug has been updated by Vinay.

New filters associated

• ARL_S MTL_P: igt@i915_selftest@live@hangcheck - dmesg-warn - ERROR GT0: GUC: Bad context sched_state 0x0, ctx_id *
  • https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_11230/bat-arls-3/igt@i915_selftest@live@hangcheck.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_134411v3/bat-arls-4/igt@i915_selftest@live@hangcheck.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1579/bat-arls-3/igt@i915_selftest@live@hangcheck.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_134680v1/bat-mtlp-9/igt@i915_selftest@live@hangcheck.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/IGT_7882/bat-mtlp-9/igt@i915_selftest@live@hangcheck.html

A CI Bug Log filter associated to this bug has been updated by Vinay.

Description: ARL_S MTL_P: igt@i915_selftest@live@hangcheck* - dmesg-warn - *ERROR* GT0: GUC: Bad context sched_state 0x0, ctx_id *

Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND machine_tag IS IN ["ARL-S", "MTL-P"] AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@i915_selftest@live@hangcheck", "igt@i915_selftest@live@gt_mocs"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["dmesg-warn"])) AND dmesg ~= '\*ERROR\* GT0: GUC: Bad context sched_state 0x0, ctx_id .*'

New failures caught by the filter:

• https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_14924/bat-mtlp-8/igt@i915_selftest@live@gt_mocs.html

changed title from **igt@i915_selftest@live@hangcheck - dmesg-warn - ERROR GT0: GUC: Bad context sched_state 0x0, ctx_id *** to **igt@i915_selftest@live@* - dmesg-warn - ERROR GT0: GUC: Bad context sched_state 0x0, ctx_id ***

A CI Bug Log filter associated to this bug has been updated by dstenka.

Description: ARL_S MTL_P: igt@i915_selftest@live@* - dmesg-warn - *ERROR* GT0: GUC: Bad context sched_state 0x0, ctx_id *

Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND machine_tag IS IN ["ARL-S", "MTL-P", "ARL-H", "DG2"] AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@i915_selftest@live@hangcheck", "igt@i915_selftest@live@gt_mocs", "igt@i915_selftest@live@workarounds"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["dmesg-warn"])) AND dmesg ~= '\*ERROR\* GT0: GUC: Bad context sched_state 0x0, ctx_id .*'

New failures caught by the filter:

• https://intel-gfx-ci.01.org/tree/drm-tip/IGT_7890/bat-arlh-1/igt@i915_selftest@live@hangcheck.html
• https://intel-gfx-ci.01.org/tree/drm-tip/IGT_7890/bat-dg2-14/igt@i915_selftest@live@workarounds.html

mentioned in issue #12303 (closed)

mentioned in issue #12439 (closed)

GuC to host communication is interrupt driven, the handling has 3 parts: interrupt context, tasklet and request queue worker. During GuC reset prepare, interrupt is disabled before destroy contexts steps start. The IRQ and worker flushed to finish in progress message handling if there are. The tasklet flush is missing, it might causes 2 race conditions:

1. Tasklet runs after IRQ flushed, add request to queue after worker flush started, causes unexpected G2H message request processing, meanwhile, reset prepare code already get the context destroyed. This will causes error reported about bad context state. (This issue and #12303 (closed))
2. Tasklet runs after intel_guc_submission_reset_prepare, ct_try_receive_message start to run, while intel_uc_reset_prepare already finished guc sanitize and set ct->enable to false. This will causes warning on incorrect ct->enable state. (#12439 (closed))

Add the missing tasklet flush to flush all 3 parts.

Patch sent for review: https://patchwork.freedesktop.org/series/140741/

The CI Bug Log issue associated to this bug has been updated by dstenka.

New filters associated

• DG2 ADL_M: few tests - dmesg-warn - ERROR GT0: GUC: Context is NULL, ctx_id* (No new failures associated)

mentioned in issue #12696 (closed)

mentioned in commit b939a08b

Patch merged: b939a08b Issue closed

closed

The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.