Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Admin message
The migration is almost done, at least the rest should happen in the background. There are still a few technical difference between the old cluster and the new ones, and they are summarized in this issue. Please pay attention to the TL:DR at the end of the comment.
few tests - dmesg-warn/dmesg-fail/incomplete/abort - *ERROR* CRITICAL: Xe has declared device * as wedged
A CI Bug Log filter associated to this bug has been updated by Vinay.
Description:PVC ADL_P LNL: few tests - dmesg-warn/abort - *ERROR* CRITICAL: Xe has declared device 0000:00:02.0* as wedged
Equivalent query: runconfig_tag IS IN ["xe"] AND machine_tag IS IN ["PVC", "LNL", "ADL-P"] AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@xe_pm@s3-vm-bind-prefetch", "igt@xe_wedged@wedged-at-any-timeout", "igt@kms_cursor_crc@cursor-random-512x170", "igt@kms_tiled_display@basic-test-pattern"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["abort", "dmesg-warn"])) AND dmesg ~= '\*ERROR\* CRITICAL: Xe has declared device 0000:00:02.0* as wedged'
Vinay Kumarchanged title from few tests - dmesg-warn/abort - ERROR CRITICAL: Xe has declared device 0000:00:02.0 as wedged to few tests - dmesg-warn/abort - ERROR CRITICAL: Xe has declared device * as wedged
changed title from few tests - dmesg-warn/abort - ERROR CRITICAL: Xe has declared device 0000:00:02.0 as wedged to few tests - dmesg-warn/abort - ERROR CRITICAL: Xe has declared device * as wedged
Vinay Kumarchanged title from few tests - dmesg-warn/abort - ERROR CRITICAL: Xe has declared device * as wedged to few tests - dmesg-warn/dmesg-fail/incomplete/abort - ERROR CRITICAL: Xe has declared device * as wedged
changed title from few tests - dmesg-warn/abort - ERROR CRITICAL: Xe has declared device * as wedged to few tests - dmesg-warn/dmesg-fail/incomplete/abort - ERROR CRITICAL: Xe has declared device * as wedged
A CI Bug Log filter associated to this bug has been updated by adelaryb.
Description: DG2 LNL ADL_P: few tests - dmesg-warn/dmesg-fail/incomplete/abort - *ERROR* CRITICAL: Xe has declared device * as wedged
Equivalent query: runconfig_tag IS IN ["xe"] AND machine_tag IS IN ["DG2", "LNL", "256EU", "ADLNL-P"] AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@xe_wedged@wedged-at-any-timeout", "igt@core_hotunplug@hotunplug-rescan"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["incomplete", "abort", "dmesg-warn", "dmesg-fail"])) AND dmesg ~= '\*ERROR\* CRITICAL: Xe has declared device .* as wedged'
<3> [411.801003] xe 0000:00:02.0: [drm] ERROR CRITICAL: Xe has declared device 0000:00:02.0 as wedged.
IOCTLs and executions are blocked. Only a rebind may clear the failure
Please file a new bug report at https://gitlab.freedesktop.org/drm/xe/kernel/issues/new
Test is passing and GPU is returned to the reliable space.
Question now is how to adjust the CI to understand that this is a valid dmesg message?
A CI Bug Log filter associated to this bug has been updated by dstenka.
Description: DG2 LNL ADL_P: few tests - dmesg-warn/dmesg-fail/incomplete/abort - *ERROR* CRITICAL: Xe has declared device * as wedged
Equivalent query: runconfig_tag IS IN ["xe"] AND machine_tag IS IN ["DG2", "256EU", "LNL", "256EUBMG", "ADL-P"] AND ((testsuite_name = "IGT" AND status_name IS IN ["incomplete", "abort", "dmesg-warn", "dmesg-fail"])) AND dmesg ~= '\*ERROR\* CRITICAL: Xe has declared device .* as wedged'