Starting at CI_DRM_3099, which is the first 4.14.0-rc1 freeze. Various em_exec_reloc@basic-* tests sporadically hit dmesg-warn: [ 247.492370] [drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request. More data: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3099/fi-kbl-7500u/igt@gem_exec_reloc@basic-gtt-read.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3099/fi-kbl-7500u/igt@gem_exec_store@basic-all.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3099/fi-kbl-7500u/igt@gem_exec_reloc@basic-cpu-read.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3104/fi-kbl-7500u/igt@gem_exec_reloc@basic-gtt-read-noreloc.html
Probably related to #102850; causal relationship unclear.
(In reply to Chris Wilson from comment #1) > Probably related to #102850; causal relationship unclear. Well, so far all runs where the gem_exec_reloc hit the "[drm:fw_domains_get [i915]] *ERROR* render: timed out waiting for forcewake ack request" there is incomplete on igt@gem_exec_suspend@basic-s3. This pattern is also visible on: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3106/fi-kbl-7500u/igt@gem_exec_reloc@basic-write-cpu.html
Also seen in: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_5776/ https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_5760/ https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_5792/
So is there any chance of getting a bisect for this? We are reasonably confident it started with the rc1 merge.
(In reply to Chris Wilson from comment #4) > So is there any chance of getting a bisect for this? We are reasonably > confident it started with the rc1 merge. We haven't seen the issue on any 4.14.0-rc2 based drm-tip in BAT.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.