drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on'
Subsystems (2)
PATCH 1/1 drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on'
DGFX platforms has lmem and cpu can access the lmem objects via mmap and i915 internal i915_gem_object_pin_map() for i915 own usages. Both of these methods has pre-requisite requirement to keep GFX PCI endpoint in D0 for a supported iomem transaction over PCI link. (Refer PCIe specs 5.3.1.4.1)
Both DG1/DG2 have a hardware bug that violates the PCIe specs and support the iomem read write transaction over PCIe bus despite endpoint is D3 state.
Due to above H/W bug, we had never observed any issue with i915 runtime PM versus lmem access.
But this issue becomes visible when PCIe gfx endpoint's upstream bridge enters to D3, at this point any lmem read/write access will be returned as unsupported request. But again this issue is not observed on every platform because it has been observed on few host machines DG1/DG2 endpoint's upstream bridge does not bind with pcieport driver. which really disables the PCIe power savings and leaves the bridge at D0 state.
Till we fix all issues related to runtime PM, we need
to keep autosupend control to 'on' on all discrete platforms with lmem.
--- drivers/gpu/drm/i915/intel_runtime_pm.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-)
drivers/gpu/drm/i915/intel_runtime_pm.c +9 -2
@@ -591,8 +591,15 @@ void intel_runtime_pm_enable(struct intel_runtime_pm *rpm)pm_runtime_use_autosuspend (kdev); } -/* Enable by default */ -pm_runtime_allow (kdev); +/* +* FIXME: Temp hammer to keep autosupend disable on lmem supported platforms. +* As per PCIe specs 5.3.1.4.1, all iomem read write request over a PCIe +* function will be unsupported in case PCIe endpoint function is in D3. +* Let's keep i915 autosuspend control 'on' till we fix all known issue +* with lmem access in D3. +*/ +if (!HAS_LMEM (i915)) +pm_runtime_allow (kdev);/* * The core calls the driver load handler with an RPM reference held.
Signature · 1 line
2.25.1
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on'
== Series Details ==
== Series Details ==
Series: drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on'
URL : https://patchwork.freedesktop.org/series/109612/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12236 -> Patchwork_109612v1
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/index.html
Participating hosts (44 -> 42)
------------------------------
Additional (1): fi-tgl-dsi
Missing (3): fi-ctg-p8600 fi-rkl-11600 fi-icl-u2
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_109612v1:
### IGT changes ###
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* igt@i915_selftest@live@gt_heartbeat:
- {fi-tgl-dsi}: NOTRUN -> [DMESG-FAIL][1]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/fi-tgl-dsi/igt@i915_selftest@live@gt_heartbeat.html
Known issues
------------
Here are the changes found in Patchwork_109612v1 that come from known issues:
### IGT changes ###
#### Possible fixes ####
* igt@fbdev@read:
- {bat-rpls-2}: [SKIP][2] ([i915#2582]) -> [PASS][3] +4 similar issues
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/bat-rpls-2/igt@[email protected]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/bat-rpls-2/igt@[email protected]
* igt@gem_exec_suspend@basic-s0@smem:
- {bat-adlm-1}: [DMESG-WARN][4] ([i915#2867]) -> [PASS][5]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/bat-adlm-1/igt@gem_exec_suspend@[email protected]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/bat-adlm-1/igt@gem_exec_suspend@[email protected]
* igt@gem_huc_copy@huc-copy:
- {bat-dg2-8}: [FAIL][6] ([i915#7029]) -> [PASS][7]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/bat-dg2-8/igt@[email protected]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/bat-dg2-8/igt@[email protected]
* igt@i915_module_load@load:
- {bat-dg2-8}: [DMESG-WARN][8] ([i915#7031]) -> [PASS][9]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/bat-dg2-8/igt@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/bat-dg2-8/igt@[email protected]
* igt@i915_module_load@reload:
- {bat-rpls-2}: [DMESG-WARN][10] ([i915#5537]) -> [PASS][11]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/bat-rpls-2/igt@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/bat-rpls-2/igt@[email protected]
- {fi-tgl-mst}: [WARN][12] ([i915#6596]) -> [PASS][13]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/fi-tgl-mst/igt@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/fi-tgl-mst/igt@[email protected]
* igt@i915_pm_rpm@module-reload:
- fi-cfl-8109u: [DMESG-FAIL][14] ([i915#62]) -> [PASS][15]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/fi-cfl-8109u/igt@[email protected]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/fi-cfl-8109u/igt@[email protected]
* igt@i915_selftest@live@gt_pm:
- {bat-rpls-2}: [DMESG-FAIL][16] ([i915#4258]) -> [PASS][17]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/bat-rpls-2/igt@i915_selftest@live@gt_pm.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/bat-rpls-2/igt@i915_selftest@live@gt_pm.html
* igt@i915_selftest@live@late_gt_pm:
- fi-cfl-8109u: [DMESG-WARN][18] ([i915#5904]) -> [PASS][19] +30 similar issues
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/fi-cfl-8109u/igt@i915_selftest@live@late_gt_pm.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/fi-cfl-8109u/igt@i915_selftest@live@late_gt_pm.html
* igt@i915_selftest@live@slpc:
- {bat-adln-1}: [DMESG-FAIL][20] ([i915#6997]) -> [PASS][21]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/bat-adln-1/igt@i915_selftest@[email protected]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/bat-adln-1/igt@i915_selftest@[email protected]
* igt@i915_suspend@basic-s2idle-without-i915:
- fi-cfl-8109u: [DMESG-WARN][22] ([i915#5904] / [i915#62]) -> [PASS][23]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/fi-cfl-8109u/igt@[email protected]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/fi-cfl-8109u/igt@[email protected]
* igt@kms_frontbuffer_tracking@basic:
- fi-cfl-8109u: [DMESG-WARN][24] ([i915#62]) -> [PASS][25] +13 similar issues
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/fi-cfl-8109u/igt@[email protected]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/fi-cfl-8109u/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1759]: https://gitlab.freedesktop.org/drm/intel/issues/1759
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582
[i915#2867]: https://gitlab.freedesktop.org/drm/intel/issues/2867
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4258]: https://gitlab.freedesktop.org/drm/intel/issues/4258
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#5122]: https://gitlab.freedesktop.org/drm/intel/issues/5122
[i915#5537]: https://gitlab.freedesktop.org/drm/intel/issues/5537
[i915#5904]: https://gitlab.freedesktop.org/drm/intel/issues/5904
[i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
[i915#6434]: https://gitlab.freedesktop.org/drm/intel/issues/6434
[i915#6559]: https://gitlab.freedesktop.org/drm/intel/issues/6559
[i915#6596]: https://gitlab.freedesktop.org/drm/intel/issues/6596
[i915#6816]: https://gitlab.freedesktop.org/drm/intel/issues/6816
[i915#6997]: https://gitlab.freedesktop.org/drm/intel/issues/6997
[i915#7029]: https://gitlab.freedesktop.org/drm/intel/issues/7029
[i915#7031]: https://gitlab.freedesktop.org/drm/intel/issues/7031
Build changes
-------------
* Linux: CI_DRM_12236 -> Patchwork_109612v1
CI-20190529: 20190529
CI_DRM_12236: 242d83e5eafbf1194e6d8b1cabc021d2549c15dc @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7009: cf55acdeea3747c668074a8734029364960e5f5e @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_109612v1: 242d83e5eafbf1194e6d8b1cabc021d2549c15dc @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
a9572c79b81b drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on'
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/index.html
Hi Anshuman,
Quoted 19 lines · Anshuman Gupta
DGFX platforms has lmem and cpu can access the lmem objects via mmap and i915 internal
i915_gem_object_pin_map()for i915 own usages. Both of these methods has pre-requisite requirement to keep GFX PCI endpoint in D0 for a supported iomem transaction over PCI link. (Refer PCIe specs 5.3.1.4.1)Both DG1/DG2 have a hardware bug that violates the PCIe specs and support the iomem read write transaction over PCIe bus despite endpoint is D3 state.
Due to above H/W bug, we had never observed any issue with i915 runtime PM versus lmem access.
But this issue becomes visible when PCIe gfx endpoint's upstream bridge enters to D3, at this point any lmem read/write access will be returned as unsupported request. But again this issue is not observed on every platform because it has been observed on few host machines DG1/DG2 endpoint's upstream bridge does not bind with pcieport driver. which really disables the PCIe power savings and leaves the bridge at D0 state.
Quoted 2 lines
Till we fix all issues related to runtime PM, we need
to keep autosupend control to 'on' on all discrete platforms with lmem.
if it's only DG1 and DG2... why do we need to do it for every platform?
Besides... is this a hack, workaround, permanent solution?
Andi
Rodrigo Vivi
maintainerQuoted 22 lines · Andi Shyti
Hi Anshuman,
Quoted 19 lines · Anshuman Gupta
DGFX platforms has lmem and cpu can access the lmem objects via mmap and i915 internal
i915_gem_object_pin_map()for i915 own usages. Both of these methods has pre-requisite requirement to keep GFX PCI endpoint in D0 for a supported iomem transaction over PCI link. (Refer PCIe specs 5.3.1.4.1)Both DG1/DG2 have a hardware bug that violates the PCIe specs and support the iomem read write transaction over PCIe bus despite endpoint is D3 state.
Due to above H/W bug, we had never observed any issue with i915 runtime PM versus lmem access.
But this issue becomes visible when PCIe gfx endpoint's upstream bridge enters to D3, at this point any lmem read/write access will be returned as unsupported request. But again this issue is not observed on every platform because it has been observed on few host machines DG1/DG2 endpoint's upstream bridge does not bind with pcieport driver. which really disables the PCIe power savings and leaves the bridge at D0 state.
Quoted 5 lines
Quoted 2 lines
Till we fix all issues related to runtime PM, we need
to keep autosupend control to 'on' on all discrete platforms with lmem.if it's only DG1 and DG2... why do we need to do it for every platform?
The HW bug on DG1 and DG2 makes our sw to work well so we didn't noticed that! But the SW bug exist in all the dgfx
Quoted 2 lines
Besides... is this a hack, workaround, permanent solution?
Yeap, probably better to move the "temporary hammer" from the subject to the commit message.
Also the FIXME comment in the code states the temporary hack nature of it.
Quoted 2 lines
Andi
Quoted 19 lines · Anshuman Gupta
DGFX platforms has lmem and cpu can access the lmem objects via mmap and i915 internal
i915_gem_object_pin_map()for i915 own usages. Both of these methods has pre-requisite requirement to keep GFX PCI endpoint in D0 for a supported iomem transaction over PCI link. (Refer PCIe specs 5.3.1.4.1)Both DG1/DG2 have a hardware bug that violates the PCIe specs and support the iomem read write transaction over PCIe bus despite endpoint is D3 state.
Due to above H/W bug, we had never observed any issue with i915 runtime PM versus lmem access.
But this issue becomes visible when PCIe gfx endpoint's upstream bridge enters to D3, at this point any lmem read/write access will be returned as unsupported request. But again this issue is not observed on every platform because it has been observed on few host machines DG1/DG2 endpoint's upstream bridge does not bind with pcieport driver. which really disables the PCIe power savings and leaves the bridge at D0 state.
Quoted 4 lines
Till we fix all issues related to runtime PM, we need
to keep autosupend control to 'on' on all discrete platforms with lmem.Fixes 527bab0473f2 ("drm/i915/rpm: Enable runtime pm autosuspend by default")
So with this change all the runtime pm stuff is disabled on dgfx? i.e intel_runtime_pm_get() always returns zero or so? Wondering if we should also revert ad74457a6b5a ("drm/i915/dgfx: Release mmap on rpm suspend") for now, since that still needs some more fixes...
Quoted 28 lines
Suggested-by Rodrigo Vivi <[email protected]>Signed-off-by Anshuman Gupta <[email protected]>--- drivers/gpu/drm/i915/intel_runtime_pm.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-)drivers/gpu/drm/i915/intel_runtime_pm.c +9
-2@@ -591,8 +591,15 @@ void intel_runtime_pm_enable(struct intel_runtime_pm *rpm)pm_runtime_use_autosuspend (kdev); } -/* Enable by default */ -pm_runtime_allow (kdev); +/* +* FIXME: Temp hammer to keep autosupend disable on lmem supported platforms. +* As per PCIe specs 5.3.1.4.1, all iomem read write request over a PCIe +* function will be unsupported in case PCIe endpoint function is in D3. +* Let's keep i915 autosuspend control 'on' till we fix all known issue +* with lmem access in D3. +*/ +if (!HAS_LMEM (i915)) +pm_runtime_allow (kdev);/* * The core calls the driver load handler with an RPM reference held.
Rodrigo Vivi
maintainerQuoted 23 lines · Matthew Auld
Quoted 22 lines · Anshuman Gupta
DGFX platforms has lmem and cpu can access the lmem objects via mmap and i915 internal
i915_gem_object_pin_map()for i915 own usages. Both of these methods has pre-requisite requirement to keep GFX PCI endpoint in D0 for a supported iomem transaction over PCI link. (Refer PCIe specs 5.3.1.4.1)Both DG1/DG2 have a hardware bug that violates the PCIe specs and support the iomem read write transaction over PCIe bus despite endpoint is D3 state.
Due to above H/W bug, we had never observed any issue with i915 runtime PM versus lmem access.
But this issue becomes visible when PCIe gfx endpoint's upstream bridge enters to D3, at this point any lmem read/write access will be returned as unsupported request. But again this issue is not observed on every platform because it has been observed on few host machines DG1/DG2 endpoint's upstream bridge does not bind with pcieport driver. which really disables the PCIe power savings and leaves the bridge at D0 state.Till we fix all issues related to runtime PM, we need
to keep autosupend control to 'on' on all discrete platforms with lmem.
Quoted 6 lines
Quoted 1 line
Fixes 527bab0473f2 ("drm/i915/rpm: Enable runtime pm autosuspend by default")So with this change all the runtime pm stuff is disabled on dgfx? i.e
intel_runtime_pm_get()always returns zero or so? Wondering if we should also revertad74457a6b5a("drm/i915/dgfx: Release mmap on rpm suspend") for now, since that still needs some more fixes...
I don't believe we need to revert that. That's already one step forward towards the final solution. It is not complete but it is not wrong.
And it is orthogonal to this protection right now.
Quoted 27 lines
Quoted 27 lines
Suggested-by Rodrigo Vivi <[email protected]>Signed-off-by Anshuman Gupta <[email protected]>--- drivers/gpu/drm/i915/intel_runtime_pm.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-)drivers/gpu/drm/i915/intel_runtime_pm.c +9
-2@@ -591,8 +591,15 @@ void intel_runtime_pm_enable(struct intel_runtime_pm *rpm)pm_runtime_use_autosuspend (kdev); } -/* Enable by default */ -pm_runtime_allow (kdev); +/* +* FIXME: Temp hammer to keep autosupend disable on lmem supported platforms. +* As per PCIe specs 5.3.1.4.1, all iomem read write request over a PCIe +* function will be unsupported in case PCIe endpoint function is in D3. +* Let's keep i915 autosuspend control 'on' till we fix all known issue +* with lmem access in D3. +*/ +if (!HAS_LMEM (i915)) +pm_runtime_allow (kdev);/* * The core calls the driver load handler with an RPM reference held.
Quoted 26 lines · Rodrigo Vivi
Quoted 25 lines · Matthew Auld
Quoted 23 lines · Anshuman Gupta
DGFX platforms has lmem and cpu can access the lmem objects via mmap and i915 internal
i915_gem_object_pin_map()for i915 own usages. Both of these methods has pre-requisite requirement to keep GFX PCI endpoint in D0 for a supported iomem transaction over PCI link. (Refer PCIe specs 5.3.1.4.1)Both DG1/DG2 have a hardware bug that violates the PCIe specs and support the iomem read write transaction over PCIe bus despite endpoint is D3 state.
Due to above H/W bug, we had never observed any issue with i915 runtime PM versus lmem access.
But this issue becomes visible when PCIe gfx endpoint's upstream bridge enters to D3, at this point any lmem read/write access will be returned as unsupported request. But again this issue is not observed on every platform because it has been observed on few host machines DG1/DG2 endpoint's upstream bridge does not bind with pcieport driver. which really disables the PCIe power savings and leaves the bridge at D0 state.Till we fix all issues related to runtime PM, we need
to keep autosupend control to 'on' on all discrete platforms with lmem.Fixes 527bab0473f2 ("drm/i915/rpm: Enable runtime pm autosuspend by default")
Quoted 8 lines
Quoted 4 lines
So with this change all the runtime pm stuff is disabled on dgfx? i.e
intel_runtime_pm_get()always returns zero or so? Wondering if we should also revertad74457a6b5a("drm/i915/dgfx: Release mmap on rpm suspend") for now, since that still needs some more fixes...I don't believe we need to revert that. That's already one step forward towards the final solution. It is not complete but it is not wrong.
And it is orthogonal to this protection right now.
That commit has some known bugs though, see https://patchwork.freedesktop.org/patch/504444/?series=108972&rev=1. But that patch appears stuck for a while now, so my question was if we should just revert for now, or does this patch now effectively make those known bugs a non-issue...
Quoted 28 lines
Quoted 28 lines
Quoted 28 lines
Suggested-by Rodrigo Vivi <[email protected]>Signed-off-by Anshuman Gupta <[email protected]>--- drivers/gpu/drm/i915/intel_runtime_pm.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-)drivers/gpu/drm/i915/intel_runtime_pm.c +9
-2@@ -591,8 +591,15 @@ void intel_runtime_pm_enable(struct intel_runtime_pm *rpm)pm_runtime_use_autosuspend (kdev); } -/* Enable by default */ -pm_runtime_allow (kdev); +/* +* FIXME: Temp hammer to keep autosupend disable on lmem supported platforms. +* As per PCIe specs 5.3.1.4.1, all iomem read write request over a PCIe +* function will be unsupported in case PCIe endpoint function is in D3. +* Let's keep i915 autosuspend control 'on' till we fix all known issue +* with lmem access in D3. +*/ +if (!HAS_LMEM (i915)) +pm_runtime_allow (kdev);/* * The core calls the driver load handler with an RPM reference held.
Quoted 3 lines · Matthew Auld
So with this change all the runtime pm stuff is disabled on dgfx? i.e
intel_runtime_pm_get()always returns zero or so?
I guess it should always return non-zero (or the wakeref) since the device is always on...
Quoted 11 lines
-----Original Message-----
From: Dixit, Ashutosh <[email protected]>
Sent: Wednesday, October 12, 2022 8:49 PM
To: Auld, Matthew <[email protected]>
Cc: Gupta, Anshuman <[email protected]>; intel- [email protected]; Vivi, Rodrigo <[email protected]>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on'
Quoted 7 lines
Quoted 3 lines · Matthew Auld
So with this change all the runtime pm stuff is disabled on dgfx? i.e
intel_runtime_pm_get()always returns zero or so?I guess it should always return non-zero (or the wakeref) since the device is always on...
This patch does not disable runtime PM completely, it just disables autosuspend i.e by grabbing the wakeref(device usage_count) at PM core level. intel_runtime_pm_get() is orthogonal to it and will get a wakeref and will increment the PM core device usage_count.
This just changes default behavior of i915, our igt rpm tests still overrides the autosuspend control to 'auto'.
I915 driver still vulnerable to any lmem access without a valid wakeref with our CI execution.
Thanks,
Anshuman Gupta.
Quoted 35 lines
-----Original Message-----
From: Auld, Matthew <[email protected]>
Sent: Wednesday, October 12, 2022 3:19 PM
To: Gupta, Anshuman <[email protected]>; intel- [email protected]
Cc: [email protected]; [email protected]; Vivi, Rodrigo <[email protected]>
Subject: Re: [PATCH] drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on'Quoted 22 lines · Anshuman Gupta
DGFX platforms has lmem and cpu can access the lmem objects via mmap and i915 internal
i915_gem_object_pin_map()for
i915 own usages. Both of these methods has pre-requisite requirement to keep GFX PCI endpoint in D0 for a supported iomem transaction over PCI link. (Refer PCIe specs 5.3.1.4.1)Both DG1/DG2 have a hardware bug that violates the PCIe specs and support the iomem read write transaction over PCIe bus despite endpoint is D3 state.
Due to above H/W bug, we had never observed any issue with i915 runtime PM versus lmem access.
But this issue becomes visible when PCIe gfx endpoint's upstream bridge enters to D3, at this point any lmem read/write access will be returned as unsupported request. But again this issue is not observed on every platform because it has been observed on few host machines DG1/DG2 endpoint's upstream bridge does not bind with pcieport driver. which really disables the PCIe power savings and leaves the bridge at D0 state.Till we fix all issues related to runtime PM, we need to keep autosupend control to 'on' on all discrete platforms with lmem.
Quoted 7 lines
Quoted 2 lines
Fixes 527bab0473f2 ("drm/i915/rpm: Enable runtime pm autosuspend bydefault")
So with this change all the runtime pm stuff is disabled on dgfx? i.e
intel_runtime_pm_get()always returns zero or so? Wondering if we should also revertad74457a6b5a("drm/i915/dgfx: Release mmap on rpm suspend") for now, since that still needs some more fixes...
Hi Matt,
This patch just keeps autosupend to 'on' as i915 default.
User can change it to 'auto' by echo 'auto' > /sys/bus/pci/devices/bdf/power/control , so we need the above mentioned commit and need to fix the issues with it. Thanks,
Anshuman Gupta.
Quoted 32 lines
drivers/gpu/drm/i915/intel_runtime_pm.c void intel_runtime_pm_enable(struct
Quoted 13 lines
Suggested-by Rodrigo Vivi <[email protected]>Signed-off-by Anshuman Gupta <[email protected]>--- drivers/gpu/drm/i915/intel_runtime_pm.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-)drivers/gpu/drm/i915/intel_runtime_pm.c +0
-0@@ -591,8 +591,15 @@ void intel_runtime_pm_enable(struct
intel_runtime_pm*rpm)drivers/gpu/drm/i915/intel_runtime_pm.c void intel_runtime_pm_enable(struct intel_runtime_pm *rpm)
Quoted 7 lines
drivers/gpu/drm/i915/intel_runtime_pm.c +2
-2pm_runtime_use_autosuspend (kdev); } -/* Enable by default */ -pm_runtime_allow (kdev); +/* +* FIXME: Temp hammer to keep autosupend disable on lmem supported platforms.
Quoted 10 lines
drivers/gpu/drm/i915/intel_runtime_pm.c +7
-0+* As per PCIe specs 5.3.1.4.1, all iomem read write request over a PCIe +* function will be unsupported in case PCIe endpoint function is in D3. +* Let's keep i915 autosuspend control 'on' till we fix all known issue +* with lmem access in D3. +*/ +if (!HAS_LMEM (i915)) +pm_runtime_allow (kdev);/* * The core calls the driver load handler with an RPM reference held.
Joonas Lahtinen
maintainerI think I commented on this already, but the patch subject should really be as informative as possible like: "Disable PCI runtime PM on dGPUs" as that is exactly what the patch does.
Also bit unsure if the Fixes: tag should really point to the runtime PM commit but maybe instead to the introduction of LMEM commit.
Regards, Joonas
Quoting Anshuman Gupta (2022-10-12 11:34:02)
Quoted 54 lines
DGFX platforms has lmem and cpu can access the lmem objects via mmap and i915 internal
i915_gem_object_pin_map()for i915 own usages. Both of these methods has pre-requisite requirement to keep GFX PCI endpoint in D0 for a supported iomem transaction over PCI link. (Refer PCIe specs 5.3.1.4.1)Both DG1/DG2 have a hardware bug that violates the PCIe specs and support the iomem read write transaction over PCIe bus despite endpoint is D3 state.
Due to above H/W bug, we had never observed any issue with i915 runtime PM versus lmem access.
But this issue becomes visible when PCIe gfx endpoint's upstream bridge enters to D3, at this point any lmem read/write access will be returned as unsupported request. But again this issue is not observed on every platform because it has been observed on few host machines DG1/DG2 endpoint's upstream bridge does not bind with pcieport driver. which really disables the PCIe power savings and leaves the bridge at D0 state.Till we fix all issues related to runtime PM, we need
to keep autosupend control to 'on' on all discrete platforms with lmem.Fixes 527bab0473f2 ("drm/i915/rpm: Enable runtime pm autosuspend by default")Suggested-by Rodrigo Vivi <[email protected]>Signed-off-by Anshuman Gupta <[email protected]>--- drivers/gpu/drm/i915/intel_runtime_pm.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-)drivers/gpu/drm/i915/intel_runtime_pm.c +9
-2@@ -591,8 +591,15 @@ void intel_runtime_pm_enable(struct intel_runtime_pm *rpm)pm_runtime_use_autosuspend (kdev); } -/* Enable by default */ -pm_runtime_allow (kdev); +/* +* FIXME: Temp hammer to keep autosupend disable on lmem supported platforms. +* As per PCIe specs 5.3.1.4.1, all iomem read write request over a PCIe +* function will be unsupported in case PCIe endpoint function is in D3. +* Let's keep i915 autosuspend control 'on' till we fix all known issue +* with lmem access in D3. +*/ +if (!HAS_LMEM (i915)) +pm_runtime_allow (kdev);/* * The core calls the driver load handler with an RPM reference held. Signature · 1 line
2.25.1
Quoted 3 lines · Joonas Lahtinen
I think I commented on this already, but the patch subject should really be as informative as possible like: "Disable PCI runtime PM on dGPUs" as that is exactly what the patch does.
+1 here.
Quoted 3 lines
Also bit unsure if the Fixes: tag should really point to the runtime PM commit but maybe instead to the introduction of LMEM commit.
indeed. if the runtime_pm by default came earlier then the LMEM, the HAS_LMEM() won't even exist and it will break the ports.
So, I'd say to go to whatever patch is the most recent between the 2.
With those changes:
Quoted 58 lines
Regards, Joonas
Quoting Anshuman Gupta (2022-10-12 11:34:02)
Quoted 54 lines
DGFX platforms has lmem and cpu can access the lmem objects via mmap and i915 internal
i915_gem_object_pin_map()for i915 own usages. Both of these methods has pre-requisite requirement to keep GFX PCI endpoint in D0 for a supported iomem transaction over PCI link. (Refer PCIe specs 5.3.1.4.1)Both DG1/DG2 have a hardware bug that violates the PCIe specs and support the iomem read write transaction over PCIe bus despite endpoint is D3 state.
Due to above H/W bug, we had never observed any issue with i915 runtime PM versus lmem access.
But this issue becomes visible when PCIe gfx endpoint's upstream bridge enters to D3, at this point any lmem read/write access will be returned as unsupported request. But again this issue is not observed on every platform because it has been observed on few host machines DG1/DG2 endpoint's upstream bridge does not bind with pcieport driver. which really disables the PCIe power savings and leaves the bridge at D0 state.Till we fix all issues related to runtime PM, we need
to keep autosupend control to 'on' on all discrete platforms with lmem.Fixes 527bab0473f2 ("drm/i915/rpm: Enable runtime pm autosuspend by default")Suggested-by Rodrigo Vivi <[email protected]>Signed-off-by Anshuman Gupta <[email protected]>--- drivers/gpu/drm/i915/intel_runtime_pm.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-)drivers/gpu/drm/i915/intel_runtime_pm.c +9
-2@@ -591,8 +591,15 @@ void intel_runtime_pm_enable(struct intel_runtime_pm *rpm)pm_runtime_use_autosuspend (kdev); } -/* Enable by default */ -pm_runtime_allow (kdev); +/* +* FIXME: Temp hammer to keep autosupend disable on lmem supported platforms. +* As per PCIe specs 5.3.1.4.1, all iomem read write request over a PCIe +* function will be unsupported in case PCIe endpoint function is in D3. +* Let's keep i915 autosuspend control 'on' till we fix all known issue +* with lmem access in D3. +*/ +if (!HAS_LMEM (i915)) +pm_runtime_allow (kdev);/* * The core calls the driver load handler with an RPM reference held. Signature · 1 line
2.25.1
Quoted 12 lines
-----Original Message-----
From: Vivi, Rodrigo <[email protected]>
Sent: Wednesday, October 12, 2022 8:31 PM
To: Joonas Lahtinen <[email protected]>
Cc: Gupta, Anshuman <[email protected]>; intel- [email protected]; [email protected]; Auld, Matthew <[email protected]>
Subject: Re: [PATCH] drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on'
Quoted 6 lines
Quoted 3 lines · Joonas Lahtinen
I think I commented on this already, but the patch subject should really be as informative as possible like: "Disable PCI runtime PM on dGPUs" as that is exactly what the patch does.
+1 here.
Hi Joonas & Rodrigo,
This patch don't disable runtime PM, it just keep autosupend control to 'on' , user or IGT tests can still enable autosupend by writing echo 'auto' > /sys/bus/pci/devices/bdf/power/control.
So I believe I should keep the subject something like "Keep PCI autosupend 'on' dGPU"
Other similar patch (https://patchwork.freedesktop.org/series/108477/) will disable the runtime PM completely.
Quoted 5 lines
Quoted 4 lines
Also bit unsure if the Fixes: tag should really point to the runtime PM commit but maybe instead to the introduction of LMEM commit.
I will remove the Fixes tag and replace it with introduction of LMEM tag.
Quoted 2 lines
indeed. if the
runtime_pmby default came earlier then the LMEM, theHAS_LMEM()won't even exist and it will break the ports.
So here I should use IS_DGFX() instead of HAS_LMEM() ? Thanks,
Anshuman Gupta.
Quoted 71 lines
So, I'd say to go to whatever patch is the most recent between the 2.
With those changes:
Reviewed-by Rodrigo Vivi <[email protected]>Quoted 35 lines
Regards, Joonas
Quoting Anshuman Gupta (2022-10-12 11:34:02)
Quoted 31 lines
DGFX platforms has lmem and cpu can access the lmem objects via mmap and i915 internal
i915_gem_object_pin_map()for
i915 own usages. Both of these methods has pre-requisite requirement to keep GFX PCI endpoint in D0 for a supported iomem transaction over PCI link. (Refer PCIe specs 5.3.1.4.1)Both DG1/DG2 have a hardware bug that violates the PCIe specs and support the iomem read write transaction over PCIe bus despite endpoint is D3 state.
Due to above H/W bug, we had never observed any issue with i915 runtime PM versus lmem access.
But this issue becomes visible when PCIe gfx endpoint's upstream bridge enters to D3, at this point any lmem read/write access will be returned as unsupported request. But again this issue is not observed on every platform because it has been observed on few host machines
DG1/DG2 endpoint's upstream bridge does not bind with pcieport driver. which really disables the PCIe power savings and leaves the bridge at D0 state.Till we fix all issues related to runtime PM, we need to keep autosupend control to 'on' on all discrete platforms with lmem.
Fixes 527bab0473f2 ("drm/i915/rpm: Enable runtime pm autosuspend bydefault")
Suggested-by Rodrigo Vivi <[email protected]>Signed-off-by Anshuman Gupta <[email protected]>--- drivers/gpu/drm/i915/intel_runtime_pm.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-)Quoted 6 lines
drivers/gpu/drm/i915/intel_runtime_pm.c void intel_runtime_pm_enable(struct
Quoted 6 lines
drivers/gpu/drm/i915/intel_runtime_pm.c +0
-0@@ -591,8 +591,15 @@ void intel_runtime_pm_enable(struct
intel_runtime_pm*rpm)Quoted 7 lines
drivers/gpu/drm/i915/intel_runtime_pm.c void intel_runtime_pm_enable(struct intel_runtime_pm *rpm)
Quoted 7 lines
drivers/gpu/drm/i915/intel_runtime_pm.c +2
-2pm_runtime_use_autosuspend (kdev); } -/* Enable by default */ -pm_runtime_allow (kdev); +/* +* FIXME: Temp hammer to keep autosupend disable on lmem supported platforms.
Quoted 13 lines
Quoted 13 lines
drivers/gpu/drm/i915/intel_runtime_pm.c +7
-1+* As per PCIe specs 5.3.1.4.1, all iomem read write request over a PCIe +* function will be unsupported in case PCIe endpoint function is in D3. +* Let's keep i915 autosuspend control 'on' till we fix all known issue +* with lmem access in D3. +*/ +if (!HAS_LMEM (i915)) +pm_runtime_allow (kdev);/* * The core calls the driver load handler with an RPM reference held. -- 2.25.1
Patchwork
CI[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on'
In reply to Anshuman Gupta== Series Details ==
== Series Details ==
Series: drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on'
URL : https://patchwork.freedesktop.org/series/109612/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12236_full -> Patchwork_109612v1_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_109612v1_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_109612v1_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Participating hosts (9 -> 9)
------------------------------
No changes in participating hosts
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_109612v1_full:
### IGT changes ###
#### Possible regressions ####
* igt@gem_exec_capture@pi@vcs0:
- shard-skl: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-skl9/igt@gem_exec_capture@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl3/igt@gem_exec_capture@[email protected]
* igt@i915_selftest@live@guc_multi_lrc:
- shard-skl: NOTRUN -> [INCOMPLETE][3]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl6/igt@i915_selftest@live@guc_multi_lrc.html
Known issues
------------
Here are the changes found in Patchwork_109612v1_full that come from known issues:
### CI changes ###
#### Possible fixes ####
* boot:
- shard-glk: ([PASS][4], [PASS][5], [PASS][6], [PASS][7], [PASS][8], [PASS][9], [PASS][10], [PASS][11], [PASS][12], [PASS][13], [PASS][14], [PASS][15], [PASS][16], [PASS][17], [PASS][18], [PASS][19], [PASS][20], [FAIL][21], [PASS][22], [FAIL][23], [PASS][24], [PASS][25], [PASS][26], [PASS][27], [PASS][28]) ([i915#4392]) -> ([PASS][29], [PASS][30], [PASS][31], [PASS][32], [PASS][33], [PASS][34], [PASS][35], [PASS][36], [PASS][37], [PASS][38], [PASS][39], [PASS][40], [PASS][41], [PASS][42], [PASS][43], [PASS][44], [PASS][45], [PASS][46], [PASS][47], [PASS][48], [PASS][49], [PASS][50], [PASS][51], [PASS][52], [PASS][53])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk1/boot.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk1/boot.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk1/boot.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk2/boot.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk2/boot.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk2/boot.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk3/boot.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk3/boot.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk5/boot.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk5/boot.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk5/boot.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk6/boot.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk6/boot.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk6/boot.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk7/boot.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk7/boot.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk7/boot.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk8/boot.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk8/boot.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk8/boot.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk8/boot.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk8/boot.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk9/boot.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk9/boot.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk9/boot.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk2/boot.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk2/boot.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk1/boot.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk1/boot.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk7/boot.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk8/boot.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk9/boot.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk8/boot.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk9/boot.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk9/boot.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk9/boot.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk8/boot.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk1/boot.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk2/boot.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk3/boot.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk3/boot.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk3/boot.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk5/boot.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk5/boot.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk5/boot.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk6/boot.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk6/boot.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk6/boot.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk7/boot.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk7/boot.html
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_exec@basic-nohangcheck:
- shard-tglb: [PASS][54] -> [FAIL][55] ([i915#6268])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-tglb1/igt@[email protected]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-tglb5/igt@[email protected]
* igt@gem_ctx_persistence@hang:
- shard-skl: NOTRUN -> [SKIP][56] ([fdo#109271]) +88 similar issues
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl1/igt@[email protected]
* igt@gem_exec_balancer@parallel-out-fence:
- shard-iclb: [PASS][57] -> [SKIP][58] ([i915#4525]) +3 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-iclb2/igt@[email protected]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-iclb3/igt@[email protected]
* igt@gem_exec_fair@basic-flow@rcs0:
- shard-tglb: [PASS][59] -> [FAIL][60] ([i915#2842]) +1 similar issue
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-tglb5/igt@gem_exec_fair@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-tglb7/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none-vip@rcs0:
- shard-glk: NOTRUN -> [FAIL][61] ([i915#2842])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk8/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none@vecs0:
- shard-glk: [PASS][62] -> [FAIL][63] ([i915#2842])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk8/igt@gem_exec_fair@[email protected]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk9/igt@gem_exec_fair@[email protected]
* igt@gem_lmem_swapping@heavy-verify-multi-ccs:
- shard-skl: NOTRUN -> [SKIP][64] ([fdo#109271] / [i915#4613]) +1 similar issue
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl1/igt@[email protected]
* igt@gem_lmem_swapping@verify-random-ccs:
- shard-apl: NOTRUN -> [SKIP][65] ([fdo#109271] / [i915#4613]) +1 similar issue
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-apl7/igt@[email protected]
- shard-glk: NOTRUN -> [SKIP][66] ([fdo#109271] / [i915#4613]) +2 similar issues
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk8/igt@[email protected]
* igt@gem_pread@exhaustion:
- shard-glk: NOTRUN -> [WARN][67] ([i915#2658])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk3/igt@[email protected]
* igt@gem_render_copy@x-tiled-to-vebox-yf-tiled:
- shard-apl: NOTRUN -> [SKIP][68] ([fdo#109271]) +41 similar issues
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-apl7/igt@[email protected]
* igt@gem_tiled_wb:
- shard-skl: NOTRUN -> [TIMEOUT][69] ([i915#6990] / [i915#7065])
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl6/igt@gem_tiled_wb.html
* igt@gem_userptr_blits@input-checking:
- shard-skl: NOTRUN -> [DMESG-WARN][70] ([i915#4991])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl1/igt@[email protected]
* igt@i915_pm_dc@dc9-dpms:
- shard-iclb: [PASS][71] -> [SKIP][72] ([i915#4281])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-iclb2/igt@[email protected]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-iclb3/igt@[email protected]
* igt@kms_big_fb@4-tiled-16bpp-rotate-270:
- shard-glk: NOTRUN -> [SKIP][73] ([fdo#109271]) +67 similar issues
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk8/igt@[email protected]
* igt@kms_big_fb@linear-16bpp-rotate-180:
- shard-iclb: [PASS][74] -> [DMESG-FAIL][75] ([i915#1888] / [i915#6020])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-iclb6/igt@[email protected]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-iclb2/igt@[email protected]
* igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc:
- shard-apl: NOTRUN -> [SKIP][76] ([fdo#109271] / [i915#3886]) +2 similar issues
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-apl7/igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_rc_ccs_cc:
- shard-skl: NOTRUN -> [SKIP][77] ([fdo#109271] / [i915#3886]) +2 similar issues
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl6/igt@kms_ccs@pipe-b-bad-rotation-90-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-c-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs_cc:
- shard-glk: NOTRUN -> [SKIP][78] ([fdo#109271] / [i915#3886]) +4 similar issues
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk3/igt@kms_ccs@pipe-c-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_chamelium@hdmi-hpd-enable-disable-mode:
- shard-skl: NOTRUN -> [SKIP][79] ([fdo#109271] / [fdo#111827]) +1 similar issue
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl1/igt@[email protected]
* igt@kms_chamelium@vga-hpd-after-suspend:
- shard-glk: NOTRUN -> [SKIP][80] ([fdo#109271] / [fdo#111827]) +2 similar issues
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk3/igt@[email protected]
* igt@kms_chamelium@vga-hpd-without-ddc:
- shard-apl: NOTRUN -> [SKIP][81] ([fdo#109271] / [fdo#111827]) +3 similar issues
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-apl7/igt@[email protected]
* igt@kms_content_protection@atomic-dpms@pipe-a-dp-1:
- shard-apl: NOTRUN -> [INCOMPLETE][82] ([i915#7121])
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-apl7/igt@kms_content_protection@[email protected]
* igt@kms_cursor_crc@cursor-suspend@pipe-a-dp-1:
- shard-apl: [PASS][83] -> [DMESG-WARN][84] ([i915#180]) +3 similar issues
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-apl7/igt@kms_cursor_crc@[email protected]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-apl2/igt@kms_cursor_crc@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions-varying-size:
- shard-glk: NOTRUN -> [FAIL][85] ([i915#2346]) +1 similar issue
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk3/igt@kms_cursor_legacy@[email protected]
- shard-skl: NOTRUN -> [FAIL][86] ([i915#2346]) +1 similar issue
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl6/igt@kms_cursor_legacy@[email protected]
* igt@kms_flip@flip-vs-expired-vblank-interruptible@b-edp1:
- shard-skl: [PASS][87] -> [FAIL][88] ([i915#79]) +4 similar issues
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-skl3/igt@kms_flip@[email protected]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl10/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-expired-vblank-interruptible@c-hdmi-a2:
- shard-glk: [PASS][89] -> [FAIL][90] ([i915#79])
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk8/igt@kms_flip@[email protected]
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk5/igt@kms_flip@[email protected]
* igt@kms_flip@plain-flip-ts-check@c-edp1:
- shard-skl: [PASS][91] -> [FAIL][92] ([i915#2122]) +2 similar issues
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-skl10/igt@kms_flip@[email protected]
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl3/igt@kms_flip@[email protected]
* igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-32bpp-yftileccs-downscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][93] ([i915#6375])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-iclb2/igt@kms_flip_scaled_crc@flip-32bpp-yftile-to-32bpp-yftileccs-downscaling@pipe-a-default-mode.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][94] ([i915#2672])
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-iclb2/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-upscaling@pipe-a-default-mode.html
* igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tiledg2rcccs-downscaling@pipe-a-valid-mode:
- shard-iclb: NOTRUN -> [SKIP][95] ([i915#2587] / [i915#2672]) +2 similar issues
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-iclb1/igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tiledg2rcccs-downscaling@pipe-a-valid-mode.html
* igt@kms_flip_scaled_crc@flip-64bpp-xtile-to-32bpp-xtile-downscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][96] ([i915#3555]) +2 similar issues
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-xtile-to-32bpp-xtile-downscaling@pipe-a-default-mode.html
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilercccs-downscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][97] ([i915#2672] / [i915#3555])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-32bpp-ytilercccs-downscaling@pipe-a-default-mode.html
* igt@kms_pipe_crc_basic@suspend-read-crc@pipe-b-edp-1:
- shard-skl: [PASS][98] -> [INCOMPLETE][99] ([i915#4939])
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-skl10/igt@kms_pipe_crc_basic@[email protected]
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl3/igt@kms_pipe_crc_basic@[email protected]
* igt@kms_plane_alpha_blend@alpha-opaque-fb@pipe-a-dp-1:
- shard-apl: NOTRUN -> [FAIL][100] ([i915#4573]) +2 similar issues
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-apl3/igt@kms_plane_alpha_blend@[email protected]
* igt@kms_plane_alpha_blend@alpha-transparent-fb@pipe-c-edp-1:
- shard-skl: NOTRUN -> [FAIL][101] ([i915#4573]) +2 similar issues
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl1/igt@kms_plane_alpha_blend@[email protected]
* igt@kms_plane_scaling@plane-downscale-with-pixel-format-factor-0-25:
- shard-snb: NOTRUN -> [SKIP][102] ([fdo#109271])
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-snb7/igt@kms_plane_scaling@plane-downscale-with-pixel-format-factor-0-25.html
* igt@kms_psr2_sf@cursor-plane-move-continuous-exceed-sf:
- shard-glk: NOTRUN -> [SKIP][103] ([fdo#109271] / [i915#658])
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk3/igt@[email protected]
* igt@kms_psr2_sf@overlay-plane-move-continuous-sf:
- shard-apl: NOTRUN -> [SKIP][104] ([fdo#109271] / [i915#658])
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-apl3/igt@[email protected]
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area:
- shard-skl: NOTRUN -> [SKIP][105] ([fdo#109271] / [i915#658])
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl1/igt@[email protected]
* igt@kms_psr2_su@page_flip-xrgb8888:
- shard-iclb: NOTRUN -> [SKIP][106] ([fdo#109642] / [fdo#111068] / [i915#658])
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-iclb1/igt@kms_psr2_su@page_flip-xrgb8888.html
* igt@kms_psr@psr2_cursor_plane_onoff:
- shard-iclb: [PASS][107] -> [SKIP][108] ([fdo#109441]) +1 similar issue
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-iclb2/igt@kms_psr@psr2_cursor_plane_onoff.html
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-iclb1/igt@kms_psr@psr2_cursor_plane_onoff.html
* igt@kms_universal_plane@cursor-fb-leak-pipe-a:
- shard-snb: [PASS][109] -> [SKIP][110] ([fdo#109271])
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-snb6/igt@[email protected]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-snb7/igt@[email protected]
* igt@perf_pmu@module-unload:
- shard-skl: [PASS][111] -> [DMESG-WARN][112] ([i915#1982])
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-skl10/igt@[email protected]
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl10/igt@[email protected]
* igt@sysfs_clients@sema-10:
- shard-skl: NOTRUN -> [SKIP][113] ([fdo#109271] / [i915#2994])
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl6/igt@[email protected]
* igt@sysfs_heartbeat_interval@mixed@rcs0:
- shard-skl: [PASS][114] -> [FAIL][115] ([i915#1731])
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-skl1/igt@sysfs_heartbeat_interval@[email protected]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl7/igt@sysfs_heartbeat_interval@[email protected]
#### Possible fixes ####
* igt@gem_ctx_persistence@smoketest:
- shard-tglb: [FAIL][116] ([i915#5099]) -> [PASS][117]
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-tglb1/igt@[email protected]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-tglb5/igt@[email protected]
* igt@gem_exec_balancer@parallel:
- shard-iclb: [SKIP][118] ([i915#4525]) -> [PASS][119]
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-iclb7/igt@[email protected]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-iclb1/igt@[email protected]
* igt@gem_exec_suspend@basic-s3@smem:
- shard-apl: [DMESG-WARN][120] ([i915#180]) -> [PASS][121] +1 similar issue
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-apl8/igt@gem_exec_suspend@[email protected]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-apl3/igt@gem_exec_suspend@[email protected]
* igt@gen9_exec_parse@allowed-single:
- shard-glk: [DMESG-WARN][122] ([i915#5566] / [i915#716]) -> [PASS][123]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk5/igt@[email protected]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk7/igt@[email protected]
* igt@i915_selftest@live@gt_heartbeat:
- shard-skl: [DMESG-FAIL][124] ([i915#5334]) -> [PASS][125]
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-skl7/igt@i915_selftest@live@gt_heartbeat.html
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl6/igt@i915_selftest@live@gt_heartbeat.html
* igt@i915_selftest@live@ring_submission:
- shard-skl: [INCOMPLETE][126] -> [PASS][127]
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-skl7/igt@i915_selftest@live@ring_submission.html
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl6/igt@i915_selftest@live@ring_submission.html
* igt@i915_suspend@fence-restore-untiled:
- shard-skl: [INCOMPLETE][128] ([i915#4817] / [i915#4939]) -> [PASS][129]
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-skl6/igt@[email protected]
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl6/igt@[email protected]
* igt@kms_big_fb@linear-max-hw-stride-64bpp-rotate-180:
- shard-skl: [DMESG-WARN][130] ([i915#1982]) -> [PASS][131]
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-skl7/igt@[email protected]
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl6/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor@varying-size:
- shard-iclb: [FAIL][132] ([i915#2346]) -> [PASS][133] +1 similar issue
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-iclb7/igt@kms_cursor_legacy@[email protected]
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-iclb1/igt@kms_cursor_legacy@[email protected]
* igt@kms_cursor_legacy@torture-bo@pipe-c:
- shard-glk: [DMESG-WARN][134] ([i915#118]) -> [PASS][135]
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-glk1/igt@kms_cursor_legacy@[email protected]
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-glk1/igt@kms_cursor_legacy@[email protected]
* igt@kms_fbcon_fbt@fbc-suspend:
- shard-apl: [FAIL][136] ([i915#4767]) -> [PASS][137]
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-apl1/igt@[email protected]
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-apl6/igt@[email protected]
* igt@kms_flip@plain-flip-fb-recreate-interruptible@c-edp1:
- shard-skl: [FAIL][138] ([i915#2122]) -> [PASS][139]
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-skl9/igt@kms_flip@[email protected]
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl9/igt@kms_flip@[email protected]
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile-downscaling@pipe-a-default-mode:
- shard-iclb: [SKIP][140] ([i915#3555]) -> [PASS][141]
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile-downscaling@pipe-a-default-mode.html
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-iclb3/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile-downscaling@pipe-a-default-mode.html
* igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-5@pipe-a-edp-1:
- shard-iclb: [SKIP][142] ([i915#5235]) -> [PASS][143] +2 similar issues
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-iclb2/igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-5@pipe-a-edp-1.html
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-iclb1/igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-5@pipe-a-edp-1.html
* igt@kms_psr@psr2_primary_mmap_gtt:
- shard-iclb: [SKIP][144] ([fdo#109441]) -> [PASS][145]
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-iclb6/igt@kms_psr@psr2_primary_mmap_gtt.html
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-iclb2/igt@kms_psr@psr2_primary_mmap_gtt.html
* igt@kms_psr_stress_test@invalidate-primary-flip-overlay:
- shard-iclb: [SKIP][146] ([i915#5519]) -> [PASS][147]
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-iclb8/igt@[email protected]
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-iclb6/igt@[email protected]
* igt@perf@polling-parameterized:
- shard-iclb: [FAIL][148] ([i915#5639]) -> [PASS][149]
[148]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-iclb7/igt@[email protected]
[149]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-iclb1/igt@[email protected]
* igt@perf_pmu@multi-client@vecs0:
- shard-skl: [FAIL][150] -> [PASS][151]
[150]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-skl3/igt@perf_pmu@[email protected]
[151]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl10/igt@perf_pmu@[email protected]
#### Warnings ####
* igt@kms_content_protection@lic@pipe-a-dp-1:
- shard-apl: [INCOMPLETE][152] ([i915#1982] / [i915#7121]) -> [INCOMPLETE][153] ([i915#7121])
[152]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-apl2/igt@kms_content_protection@[email protected]
[153]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-apl3/igt@kms_content_protection@[email protected]
* igt@kms_flip@flip-vs-expired-vblank-interruptible@c-edp1:
- shard-skl: [FAIL][154] ([i915#2122]) -> [FAIL][155] ([i915#79])
[154]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-skl3/igt@kms_flip@[email protected]
[155]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-skl10/igt@kms_flip@[email protected]
* igt@kms_psr2_sf@overlay-plane-move-continuous-exceed-sf:
- shard-iclb: [SKIP][156] ([i915#2920]) -> [SKIP][157] ([i915#658]) +2 similar issues
[156]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-iclb2/igt@[email protected]
[157]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-iclb1/igt@[email protected]
* igt@kms_psr2_sf@plane-move-sf-dmg-area:
- shard-iclb: [SKIP][158] ([fdo#111068] / [i915#658]) -> [SKIP][159] ([i915#2920]) +1 similar issue
[158]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12236/shard-iclb5/igt@[email protected]
[159]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/shard-iclb2/igt@[email protected]
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1731]: https://gitlab.freedesktop.org/drm/intel/issues/1731
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2587]: https://gitlab.freedesktop.org/drm/intel/issues/2587
[i915#2658]: https://gitlab.freedesktop.org/drm/intel/issues/2658
[i915#2672]: https://gitlab.freedesktop.org/drm/intel/issues/2672
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2920]: https://gitlab.freedesktop.org/drm/intel/issues/2920
[i915#2994]: https://gitlab.freedesktop.org/drm/intel/issues/2994
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#4281]: https://gitlab.freedesktop.org/drm/intel/issues/4281
[i915#4392]: https://gitlab.freedesktop.org/drm/intel/issues/4392
[i915#4525]: https://gitlab.freedesktop.org/drm/intel/issues/4525
[i915#4573]: https://gitlab.freedesktop.org/drm/intel/issues/4573
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4767]: https://gitlab.freedesktop.org/drm/intel/issues/4767
[i915#4817]: https://gitlab.freedesktop.org/drm/intel/issues/4817
[i915#4939]: https://gitlab.freedesktop.org/drm/intel/issues/4939
[i915#4991]: https://gitlab.freedesktop.org/drm/intel/issues/4991
[i915#5099]: https://gitlab.freedesktop.org/drm/intel/issues/5099
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#5334]: https://gitlab.freedesktop.org/drm/intel/issues/5334
[i915#5519]: https://gitlab.freedesktop.org/drm/intel/issues/5519
[i915#5566]: https://gitlab.freedesktop.org/drm/intel/issues/5566
[i915#5639]: https://gitlab.freedesktop.org/drm/intel/issues/5639
[i915#6020]: https://gitlab.freedesktop.org/drm/intel/issues/6020
[i915#6268]: https://gitlab.freedesktop.org/drm/intel/issues/6268
[i915#6375]: https://gitlab.freedesktop.org/drm/intel/issues/6375
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#6990]: https://gitlab.freedesktop.org/drm/intel/issues/6990
[i915#7065]: https://gitlab.freedesktop.org/drm/intel/issues/7065
[i915#7121]: https://gitlab.freedesktop.org/drm/intel/issues/7121
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
Build changes
-------------
* Linux: CI_DRM_12236 -> Patchwork_109612v1
CI-20190529: 20190529
CI_DRM_12236: 242d83e5eafbf1194e6d8b1cabc021d2549c15dc @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7009: cf55acdeea3747c668074a8734029364960e5f5e @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_109612v1: 242d83e5eafbf1194e6d8b1cabc021d2549c15dc @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v1/index.html
PATCH v2 1/1 drm/i915/dgfx: Keep PCI autosuspend control 'on' by default on all dGPU
In reply to Anshuman GuptaDGFX platforms has lmem and cpu can access the lmem objects via mmap and i915 internal i915_gem_object_pin_map() for i915 own usages. Both of these methods has pre-requisite requirement to keep GFX PCI endpoint in D0 for a supported iomem transaction over PCI link. (Refer PCIe specs 5.3.1.4.1)
Both DG1/DG2 have a known hardware bug that violates the PCIe specs and support the iomem read write transaction over PCIe bus despite endpoint is D3 state.
Due to above H/W bug, we had never observed any issue with i915 runtime PM versus lmem access.
But this issue becomes visible when PCIe gfx endpoint's upstream bridge enters to D3, at this point any lmem read/write access will be returned as unsupported request. But again this issue is not observed on every platform because it has been observed on few host machines DG1/DG2 endpoint's upstream bridge does not bind with pcieport driver. which really disables the PCIe power savings and leaves the bridge at D0 state.
We need a unique interface to read/write from lmem with runtime PM wakeref protection something similar to intel_uncore_{read, write}, keep autosuspend control to 'on' on all discrete platforms, until we have a unique interface to read/write from lmem.
This just change the default autosuspend setting of i915 on dGPU, user can still change it to 'auto'.
v2:
- Modified the commit message and subject with more information.
- Changed the Fixes tag to LMEM support commit. [Joonas]
- Changed !HAS_LMEM() Cond to !IS_DGFX(). [Rodrigo]
--- drivers/gpu/drm/i915/intel_runtime_pm.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-)
drivers/gpu/drm/i915/intel_runtime_pm.c +9 -2
@@ -591,8 +591,15 @@ void intel_runtime_pm_enable(struct intel_runtime_pm *rpm)pm_runtime_use_autosuspend (kdev); } -/* Enable by default */ -pm_runtime_allow (kdev); +/* +* FIXME: Temp hammer to keep autosupend disable on lmem supported platforms. +* As per PCIe specs 5.3.1.4.1, all iomem read write request over a PCIe +* function will be unsupported in case PCIe endpoint function is in D3. +* Let's keep i915 autosuspend control 'on' till we fix all known issue +* with lmem access in D3. +*/ +if (!IS_DGFX (i915)) +pm_runtime_allow (kdev);/* * The core calls the driver load handler with an RPM reference held.
Signature · 1 line
2.25.1
Re: [Intel-gfx] [PATCH v2] drm/i915/dgfx: Keep PCI autosuspend control 'on' by default on all dGPU
Quoted 38 lines
-----Original Message-----
From: Gupta, Anshuman <[email protected]>
Sent: Friday, October 14, 2022 5:03 PM
To: [email protected]
Cc: [email protected]; [email protected]; Auld, Matthew <[email protected]>; Vivi, Rodrigo <[email protected]>; Gupta, Anshuman <[email protected]>
Subject: [PATCH v2] drm/i915/dgfx: Keep PCI autosuspend control 'on' by default on all dGPUDGFX platforms has lmem and cpu can access the lmem objects via mmap and i915 internal
i915_gem_object_pin_map()for
i915 own usages. Both of these methods has pre-requisite requirement to keep GFX PCI endpoint in D0 for a supported iomem transaction over PCI link. (Refer PCIe specs 5.3.1.4.1)Both DG1/DG2 have a known hardware bug that violates the PCIe specs and support the iomem read write transaction over PCIe bus despite endpoint is D3 state.
Due to above H/W bug, we had never observed any issue with i915 runtime PM versus lmem access.
But this issue becomes visible when PCIe gfx endpoint's upstream bridge enters to D3, at this point any lmem read/write access will be returned as unsupported request. But again this issue is not observed on every platform because it has been observed on few host machines
DG1/DG2 endpoint's upstream bridge does not bind with pcieport driver. which really disables the PCIe power savings and leaves the bridge at D0 state.We need a unique interface to read/write from lmem with runtime PM wakeref protection something similar to intel_uncore_{read, write}, keep autosuspend control to 'on' on all discrete platforms, until we have a unique interface to read/write from lmem.
This just change the default autosuspend setting of i915 on dGPU, user can still change it to 'auto'.
Quoted 8 lines
v2:
- Modified the commit message and subject with more information.
- Changed the Fixes tag to LMEM support commit. [Joonas]
- Changed !HAS_LMEM() Cond to !IS_DGFX(). [Rodrigo]Fixes b908be543e44 ("drm/i915: support creating LMEM objects")Suggested-by Rodrigo Vivi <[email protected]>Signed-off-by Anshuman Gupta <[email protected]>
Hi Rodrigo ,
I missed to add your conditional RB tag here.
I addressed all comments and changed the Fixes tag to b908be543e44 ("drm/i915: support creating LMEM objects") CI is green, shall I use your RB and merge this tag if nobody else has any further review comment? Thanks,
Anshuman.
Quoted 31 lines
--- drivers/gpu/drm/i915/intel_runtime_pm.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-)drivers/gpu/drm/i915/intel_runtime_pm.c +2
-2@@ -591,8 +591,15 @@ void intel_runtime_pm_enable(struct intel_runtime_pm *rpm)pm_runtime_use_autosuspend (kdev ); } -/* Enable by default */ -pm_runtime_allow (kdev); +/* +* FIXME: Temp hammer to keep autosupend disable on lmem supported platforms.
drivers/gpu/drm/i915/intel_runtime_pm.c +7
-1+* As per PCIe specs 5.3.1.4.1, all iomem read write request over a PCIe +* function will be unsupported in case PCIe endpoint function is in D3. +* Let's keep i915 autosuspend control 'on' till we fix all known issue +* with lmem access in D3. +*/ +if (!IS_DGFX (i915)) +pm_runtime_allow (kdev);/* * The core calls the driver load handler with an RPM reference held. -- 2.25.1
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on' (rev2)
In reply to Anshuman Gupta== Series Details ==
== Series Details ==
Series: drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on' (rev2)
URL : https://patchwork.freedesktop.org/series/109612/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12242 -> Patchwork_109612v2
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/index.html
Participating hosts (45 -> 43)
------------------------------
Additional (3): fi-tgl-u2 fi-icl-u2 fi-pnv-d510
Missing (5): fi-ilk-m540 fi-hsw-4200u fi-kbl-x1275 fi-bsw-nick bat-jsl-1
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_109612v2:
### IGT changes ###
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* igt@kms_pipe_crc_basic@nonblocking-crc@pipe-d-dp-3:
- {bat-dg2-11}: [PASS][1] -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/bat-dg2-11/igt@kms_pipe_crc_basic@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/bat-dg2-11/igt@kms_pipe_crc_basic@[email protected]
Known issues
------------
Here are the changes found in Patchwork_109612v2 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_huc_copy@huc-copy:
- fi-icl-u2: NOTRUN -> [SKIP][3] ([i915#2190])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/fi-icl-u2/igt@[email protected]
- fi-tgl-u2: NOTRUN -> [SKIP][4] ([i915#2190])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/fi-tgl-u2/igt@[email protected]
* igt@gem_lmem_swapping@random-engines:
- fi-icl-u2: NOTRUN -> [SKIP][5] ([i915#4613]) +3 similar issues
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/fi-icl-u2/igt@[email protected]
* igt@kms_chamelium@hdmi-edid-read:
- fi-tgl-u2: NOTRUN -> [SKIP][6] ([fdo#109284] / [fdo#111827]) +7 similar issues
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/fi-tgl-u2/igt@[email protected]
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-icl-u2: NOTRUN -> [SKIP][7] ([fdo#111827]) +8 similar issues
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/fi-icl-u2/igt@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor:
- fi-tgl-u2: NOTRUN -> [SKIP][8] ([i915#4103])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/fi-tgl-u2/igt@[email protected]
- fi-icl-u2: NOTRUN -> [SKIP][9] ([i915#4103])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/fi-icl-u2/igt@[email protected]
* igt@kms_force_connector_basic@force-load-detect:
- fi-tgl-u2: NOTRUN -> [SKIP][10] ([fdo#109285])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/fi-tgl-u2/igt@[email protected]
- fi-icl-u2: NOTRUN -> [SKIP][11] ([fdo#109285])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/fi-icl-u2/igt@[email protected]
* igt@kms_psr@primary_page_flip:
- fi-pnv-d510: NOTRUN -> [SKIP][12] ([fdo#109271]) +43 similar issues
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/fi-pnv-d510/igt@kms_psr@primary_page_flip.html
* igt@kms_setmode@basic-clone-single-crtc:
- fi-icl-u2: NOTRUN -> [SKIP][13] ([i915#3555])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/fi-icl-u2/igt@[email protected]
- fi-tgl-u2: NOTRUN -> [SKIP][14] ([i915#3555])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/fi-tgl-u2/igt@[email protected]
* igt@prime_vgem@basic-userptr:
- fi-icl-u2: NOTRUN -> [SKIP][15] ([fdo#109295] / [i915#3301])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/fi-icl-u2/igt@[email protected]
* igt@runner@aborted:
- fi-bxt-dsi: NOTRUN -> [FAIL][16] ([i915#4312])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/fi-bxt-dsi/igt@[email protected]
#### Possible fixes ####
* igt@gem_exec_suspend@basic-s0@lmem0:
- {bat-dg2-11}: [DMESG-WARN][17] ([i915#6816]) -> [PASS][18] +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/bat-dg2-11/igt@gem_exec_suspend@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/bat-dg2-11/igt@gem_exec_suspend@[email protected]
* igt@i915_module_load@reload:
- {bat-rpls-2}: [DMESG-WARN][19] ([i915#5537]) -> [PASS][20]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/bat-rpls-2/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/bat-rpls-2/igt@[email protected]
* igt@i915_pm_rpm@basic-rte:
- {bat-rplp-1}: [DMESG-WARN][21] ([i915#7077]) -> [PASS][22]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/bat-rplp-1/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/bat-rplp-1/igt@[email protected]
* igt@i915_pm_rpm@module-reload:
- {fi-tgl-mst}: [DMESG-WARN][23] ([i915#5537]) -> [PASS][24]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/fi-tgl-mst/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/fi-tgl-mst/igt@[email protected]
* igt@i915_selftest@live@reset:
- {bat-rpls-2}: [DMESG-FAIL][25] ([i915#4983]) -> [PASS][26]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/bat-rpls-2/igt@i915_selftest@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/bat-rpls-2/igt@i915_selftest@[email protected]
* igt@kms_pipe_crc_basic@suspend-read-crc@pipe-d-dp-3:
- {bat-dg2-11}: [FAIL][27] ([i915#6818]) -> [PASS][28]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/bat-dg2-11/igt@kms_pipe_crc_basic@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/bat-dg2-11/igt@kms_pipe_crc_basic@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582
[i915#2867]: https://gitlab.freedesktop.org/drm/intel/issues/2867
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4983]: https://gitlab.freedesktop.org/drm/intel/issues/4983
[i915#5122]: https://gitlab.freedesktop.org/drm/intel/issues/5122
[i915#5354]: https://gitlab.freedesktop.org/drm/intel/issues/5354
[i915#5537]: https://gitlab.freedesktop.org/drm/intel/issues/5537
[i915#6106]: https://gitlab.freedesktop.org/drm/intel/issues/6106
[i915#6257]: https://gitlab.freedesktop.org/drm/intel/issues/6257
[i915#6367]: https://gitlab.freedesktop.org/drm/intel/issues/6367
[i915#6559]: https://gitlab.freedesktop.org/drm/intel/issues/6559
[i915#6596]: https://gitlab.freedesktop.org/drm/intel/issues/6596
[i915#6621]: https://gitlab.freedesktop.org/drm/intel/issues/6621
[i915#6816]: https://gitlab.freedesktop.org/drm/intel/issues/6816
[i915#6818]: https://gitlab.freedesktop.org/drm/intel/issues/6818
[i915#7077]: https://gitlab.freedesktop.org/drm/intel/issues/7077
Build changes
-------------
* Linux: CI_DRM_12242 -> Patchwork_109612v2
CI-20190529: 20190529
CI_DRM_12242: 075a81b1efd29300194bdf7877e08b6dbe3079d9 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7012: ca6f5bdd537d26692c4b1ca011b8c4f227d95703 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_109612v2: 075a81b1efd29300194bdf7877e08b6dbe3079d9 @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
ea83ea9ac0bf drm/i915/dgfx: Keep PCI autosuspend control 'on' by default on all dGPU
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/index.html
Patchwork
CI[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on' (rev2)
In reply to Anshuman Gupta== Series Details ==
== Series Details ==
Series: drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on' (rev2)
URL : https://patchwork.freedesktop.org/series/109612/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12242_full -> Patchwork_109612v2_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Participating hosts (9 -> 11)
------------------------------
Additional (2): shard-rkl shard-dg1
Known issues
------------
Here are the changes found in Patchwork_109612v2_full that come from known issues:
### CI changes ###
#### Possible fixes ####
* boot:
- shard-skl: ([PASS][1], [PASS][2], [PASS][3], [PASS][4], [PASS][5], [PASS][6], [PASS][7], [PASS][8], [PASS][9], [PASS][10], [PASS][11], [PASS][12], [PASS][13], [FAIL][14], [PASS][15], [PASS][16], [PASS][17], [PASS][18], [FAIL][19], [PASS][20], [PASS][21], [PASS][22], [PASS][23], [PASS][24], [PASS][25]) ([i915#5032]) -> ([PASS][26], [PASS][27], [PASS][28], [PASS][29], [PASS][30], [PASS][31], [PASS][32], [PASS][33], [PASS][34], [PASS][35], [PASS][36], [PASS][37], [PASS][38], [PASS][39], [PASS][40], [PASS][41], [PASS][42], [PASS][43], [PASS][44], [PASS][45], [PASS][46])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl10/boot.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl9/boot.html
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl9/boot.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl9/boot.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl10/boot.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl9/boot.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl7/boot.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl7/boot.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl7/boot.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl6/boot.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl6/boot.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl6/boot.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl5/boot.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl5/boot.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl10/boot.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl10/boot.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl1/boot.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl5/boot.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl5/boot.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl4/boot.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl4/boot.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl4/boot.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl4/boot.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl1/boot.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl1/boot.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl1/boot.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/boot.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/boot.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/boot.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl7/boot.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl7/boot.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl6/boot.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl6/boot.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl6/boot.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl5/boot.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl5/boot.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl4/boot.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl4/boot.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl4/boot.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl2/boot.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl2/boot.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl1/boot.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl1/boot.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl10/boot.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl10/boot.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl10/boot.html
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_balancer@parallel-out-fence:
- shard-iclb: [PASS][47] -> [SKIP][48] ([i915#4525])
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-iclb1/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb8/igt@[email protected]
* igt@gem_exec_fair@basic-none-solo@rcs0:
- shard-apl: [PASS][49] -> [FAIL][50] ([i915#2842])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl7/igt@gem_exec_fair@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl8/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none@vcs1:
- shard-iclb: NOTRUN -> [FAIL][51] ([i915#2842])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb1/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@vecs0:
- shard-iclb: [PASS][52] -> [FAIL][53] ([i915#2842])
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-iclb8/igt@gem_exec_fair@[email protected]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb6/igt@gem_exec_fair@[email protected]
* igt@gem_huc_copy@huc-copy:
- shard-tglb: [PASS][54] -> [SKIP][55] ([i915#2190])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-tglb5/igt@[email protected]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-tglb7/igt@[email protected]
* igt@gem_lmem_swapping@heavy-random:
- shard-skl: NOTRUN -> [SKIP][56] ([fdo#109271] / [i915#4613]) +1 similar issue
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@[email protected]
* igt@gem_userptr_blits@dmabuf-sync:
- shard-skl: NOTRUN -> [SKIP][57] ([fdo#109271] / [i915#3323])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@[email protected]
* igt@gen9_exec_parse@allowed-single:
- shard-apl: [PASS][58] -> [DMESG-WARN][59] ([i915#5566] / [i915#716])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl1/igt@[email protected]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@[email protected]
* igt@i915_pipe_stress@stress-xrgb8888-untiled:
- shard-apl: NOTRUN -> [FAIL][60] ([i915#7036])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@[email protected]
* igt@i915_selftest@live@gt_heartbeat:
- shard-apl: [PASS][61] -> [DMESG-FAIL][62] ([i915#5334])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl1/igt@i915_selftest@live@gt_heartbeat.html
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl6/igt@i915_selftest@live@gt_heartbeat.html
* igt@kms_async_flips@alternate-sync-async-flip@pipe-b-edp-1:
- shard-skl: [PASS][63] -> [FAIL][64] ([i915#2521]) +1 similar issue
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl10/igt@kms_async_flips@[email protected]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl10/igt@kms_async_flips@[email protected]
* igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_mc_ccs:
- shard-skl: NOTRUN -> [SKIP][65] ([fdo#109271] / [i915#3886])
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-a-random-ccs-data-y_tiled_gen12_rc_ccs_cc:
- shard-apl: NOTRUN -> [SKIP][66] ([fdo#109271] / [i915#3886]) +2 similar issues
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@kms_ccs@pipe-a-random-ccs-data-y_tiled_gen12_rc_ccs_cc.html
- shard-glk: NOTRUN -> [SKIP][67] ([fdo#109271] / [i915#3886])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk3/igt@kms_ccs@pipe-a-random-ccs-data-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-b-bad-rotation-90-4_tiled_dg2_rc_ccs_cc:
- shard-apl: NOTRUN -> [SKIP][68] ([fdo#109271]) +52 similar issues
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@kms_ccs@pipe-b-bad-rotation-90-4_tiled_dg2_rc_ccs_cc.html
* igt@kms_ccs@pipe-c-crc-sprite-planes-basic-4_tiled_dg2_rc_ccs:
- shard-glk: NOTRUN -> [SKIP][69] ([fdo#109271]) +27 similar issues
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk3/igt@kms_ccs@pipe-c-crc-sprite-planes-basic-4_tiled_dg2_rc_ccs.html
* igt@kms_chamelium@hdmi-edid-change-during-suspend:
- shard-skl: NOTRUN -> [SKIP][70] ([fdo#109271] / [fdo#111827]) +3 similar issues
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@[email protected]
* igt@kms_chamelium@hdmi-hpd-storm:
- shard-apl: NOTRUN -> [SKIP][71] ([fdo#109271] / [fdo#111827]) +3 similar issues
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@[email protected]
- shard-glk: NOTRUN -> [SKIP][72] ([fdo#109271] / [fdo#111827])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk3/igt@[email protected]
* igt@kms_color@ctm-0-25:
- shard-skl: NOTRUN -> [SKIP][73] ([fdo#109271] / [i915#3546])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@[email protected]
* igt@kms_fbcon_fbt@psr-suspend:
- shard-skl: NOTRUN -> [INCOMPLETE][74] ([i915#4939] / [i915#7192])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@[email protected]
* igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@bc-hdmi-a1-hdmi-a2:
- shard-glk: [PASS][75] -> [FAIL][76] ([i915#79])
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-glk9/igt@kms_flip@[email protected]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk7/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible@c-edp1:
- shard-skl: [PASS][77] -> [FAIL][78] ([i915#2122]) +1 similar issue
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl6/igt@kms_flip@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl2/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-expired-vblank@c-edp1:
- shard-skl: [PASS][79] -> [FAIL][80] ([i915#79]) +1 similar issue
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl1/igt@kms_flip@[email protected]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@kms_flip@[email protected]
* igt@kms_flip_scaled_crc@flip-32bpp-xtile-to-64bpp-xtile-downscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][81] ([i915#3555])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb2/igt@kms_flip_scaled_crc@flip-32bpp-xtile-to-64bpp-xtile-downscaling@pipe-a-default-mode.html
* igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tile-upscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][82] ([i915#2672]) +2 similar issues
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tile-upscaling@pipe-a-default-mode.html
* igt@kms_flip_scaled_crc@flip-64bpp-yftile-to-16bpp-yftile-upscaling@pipe-a-valid-mode:
- shard-iclb: NOTRUN -> [SKIP][83] ([i915#2587] / [i915#2672]) +1 similar issue
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb5/igt@kms_flip_scaled_crc@flip-64bpp-yftile-to-16bpp-yftile-upscaling@pipe-a-valid-mode.html
* igt@kms_frontbuffer_tracking@fbcpsr-suspend:
- shard-skl: NOTRUN -> [SKIP][84] ([fdo#109271]) +116 similar issues
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@[email protected]
* igt@kms_plane_alpha_blend@alpha-opaque-fb@pipe-a-dp-1:
- shard-apl: NOTRUN -> [FAIL][85] ([i915#4573]) +2 similar issues
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@kms_plane_alpha_blend@[email protected]
* igt@kms_psr2_su@page_flip-p010@pipe-b-edp-1:
- shard-iclb: NOTRUN -> [FAIL][86] ([i915#5939]) +2 similar issues
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb2/igt@kms_psr2_su@[email protected]
* igt@kms_psr2_su@page_flip-xrgb8888:
- shard-skl: NOTRUN -> [SKIP][87] ([fdo#109271] / [i915#658]) +2 similar issues
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@kms_psr2_su@page_flip-xrgb8888.html
* igt@kms_psr@psr2_primary_mmap_cpu:
- shard-iclb: [PASS][88] -> [SKIP][89] ([fdo#109441])
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb1/igt@kms_psr@psr2_primary_mmap_cpu.html
* igt@kms_vblank@pipe-b-ts-continuation-suspend:
- shard-apl: [PASS][90] -> [DMESG-WARN][91] ([i915#180]) +2 similar issues
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl8/igt@[email protected]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl3/igt@[email protected]
* igt@kms_writeback@writeback-invalid-parameters:
- shard-skl: NOTRUN -> [SKIP][92] ([fdo#109271] / [i915#2437])
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@[email protected]
* igt@perf@blocking:
- shard-skl: [PASS][93] -> [FAIL][94] ([i915#1542])
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl6/igt@[email protected]
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl6/igt@[email protected]
* igt@perf@polling-parameterized:
- shard-glk: [PASS][95] -> [FAIL][96] ([i915#5639])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-glk6/igt@[email protected]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk6/igt@[email protected]
* igt@sysfs_clients@create:
- shard-apl: NOTRUN -> [SKIP][97] ([fdo#109271] / [i915#2994])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@[email protected]
#### Possible fixes ####
* igt@gem_exec_balancer@parallel-balancer:
- shard-iclb: [SKIP][98] ([i915#4525]) -> [PASS][99]
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-iclb5/igt@[email protected]
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb2/igt@[email protected]
* igt@gem_exec_fair@basic-flow@rcs0:
- shard-tglb: [FAIL][100] ([i915#2842]) -> [PASS][101]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-tglb7/igt@gem_exec_fair@[email protected]
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-tglb1/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-glk: [FAIL][102] ([i915#2842]) -> [PASS][103]
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-glk3/igt@gem_exec_fair@[email protected]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk5/igt@gem_exec_fair@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-apl: [DMESG-WARN][104] ([i915#5566] / [i915#716]) -> [PASS][105]
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl2/igt@[email protected]
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-crc-atomic:
- shard-skl: [FAIL][106] ([i915#2346]) -> [PASS][107]
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl6/igt@[email protected]
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl6/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions:
- shard-glk: [FAIL][108] ([i915#2346]) -> [PASS][109]
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-glk9/igt@kms_cursor_legacy@[email protected]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk7/igt@kms_cursor_legacy@[email protected]
* igt@kms_flip@busy-flip@c-edp1:
- shard-skl: [FAIL][110] ([i915#7200]) -> [PASS][111] +1 similar issue
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl5/igt@kms_flip@[email protected]
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl7/igt@kms_flip@[email protected]
* igt@kms_hdr@bpc-switch-suspend@pipe-a-dp-1:
- shard-apl: [DMESG-WARN][112] ([i915#180]) -> [PASS][113] +1 similar issue
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl3/igt@kms_hdr@[email protected]
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@kms_hdr@[email protected]
* igt@perf@polling-parameterized:
- shard-skl: [FAIL][114] ([i915#5639]) -> [PASS][115]
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl10/igt@[email protected]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl10/igt@[email protected]
* igt@perf@stress-open-close:
- shard-glk: [INCOMPLETE][116] ([i915#5213]) -> [PASS][117]
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-glk1/igt@[email protected]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk3/igt@[email protected]
#### Warnings ####
* igt@dmabuf@all@dma_fence_chain:
- shard-skl: [INCOMPLETE][118] ([i915#6949] / [i915#7165]) -> [INCOMPLETE][119] ([i915#6949] / [i915#7165] / [i915#7192])
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl6/igt@dmabuf@all@dma_fence_chain.html
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl6/igt@dmabuf@all@dma_fence_chain.html
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-tglb: [FAIL][120] ([i915#2842]) -> [SKIP][121] ([i915#2848]) +2 similar issues
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-tglb3/igt@gem_exec_fair@[email protected]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-tglb2/igt@gem_exec_fair@[email protected]
* igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip:
- shard-apl: [SKIP][122] ([fdo#109271]) -> [SKIP][123] ([fdo#109271] / [i915#7206])
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl7/igt@[email protected]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl8/igt@[email protected]
- shard-glk: [SKIP][124] ([fdo#109271]) -> [SKIP][125] ([fdo#109271] / [i915#7206])
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-glk9/igt@[email protected]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk7/igt@[email protected]
* igt@kms_ccs@pipe-b-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc:
- shard-skl: [SKIP][126] ([fdo#109271] / [i915#3886]) -> [INCOMPLETE][127] ([i915#7192])
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl1/igt@kms_ccs@pipe-b-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc.html
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl5/igt@kms_ccs@pipe-b-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_dsc@dsc-with-bpc-formats:
- shard-glk: [SKIP][128] ([fdo#109271]) -> [SKIP][129] ([fdo#109271] / [i915#7205])
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-glk9/igt@[email protected]
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk7/igt@[email protected]
- shard-skl: [SKIP][130] ([fdo#109271]) -> [SKIP][131] ([fdo#109271] / [i915#7205])
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl5/igt@[email protected]
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl7/igt@[email protected]
- shard-apl: [SKIP][132] ([fdo#109271]) -> [SKIP][133] ([fdo#109271] / [i915#7205])
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl7/igt@[email protected]
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl8/igt@[email protected]
* igt@kms_flip_scaled_crc@flip-32bpp-yftileccs-to-64bpp-yftile-upscaling@pipe-a-default-mode:
- shard-skl: [SKIP][134] ([fdo#109271]) -> [SKIP][135] ([fdo#109271] / [i915#7207])
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl9/igt@kms_flip_scaled_crc@flip-32bpp-yftileccs-to-64bpp-yftile-upscaling@pipe-a-default-mode.html
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl1/igt@kms_flip_scaled_crc@flip-32bpp-yftileccs-to-64bpp-yftile-upscaling@pipe-a-default-mode.html
* igt@kms_psr2_sf@cursor-plane-move-continuous-exceed-fully-sf:
- shard-iclb: [SKIP][136] ([i915#658]) -> [SKIP][137] ([i915#2920])
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-iclb5/igt@[email protected]
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb2/igt@[email protected]
* igt@runner@aborted:
- shard-apl: ([FAIL][138], [FAIL][139], [FAIL][140], [FAIL][141], [FAIL][142]) ([fdo#109271] / [i915#3002] / [i915#4312]) -> ([FAIL][143], [FAIL][144], [FAIL][145], [FAIL][146], [FAIL][147], [FAIL][148]) ([fdo#109271] / [i915#180] / [i915#3002] / [i915#4312])
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl2/igt@[email protected]
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl6/igt@[email protected]
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl8/igt@[email protected]
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl3/igt@[email protected]
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl3/igt@[email protected]
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl3/igt@[email protected]
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl6/igt@[email protected]
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl3/igt@[email protected]
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@[email protected]
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@[email protected]
[148]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl1/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109283]: https://bugs.freedesktop.org/show_bug.cgi?id=109283
[fdo#109289]: https://bugs.freedesktop.org/show_bug.cgi?id=109289
[fdo#109291]: https://bugs.freedesktop.org/show_bug.cgi?id=109291
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#109303]: https://bugs.freedesktop.org/show_bug.cgi?id=109303
[fdo#109307]: https://bugs.freedesktop.org/show_bug.cgi?id=109307
[fdo#109308]: https://bugs.freedesktop.org/show_bug.cgi?id=109308
[fdo#109309]: https://bugs.freedesktop.org/show_bug.cgi?id=109309
[fdo#109312]: https://bugs.freedesktop.org/show_bug.cgi?id=109312
[fdo#109314]: https://bugs.freedesktop.org/show_bug.cgi?id=109314
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109506]: https://bugs.freedesktop.org/show_bug.cgi?id=109506
[fdo#110542]: https://bugs.freedesktop.org/show_bug.cgi?id=110542
[fdo#110723]: https://bugs.freedesktop.org/show_bug.cgi?id=110723
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#111614]: https://bugs.freedesktop.org/show_bug.cgi?id=111614
[fdo#111615]: https://bugs.freedesktop.org/show_bug.cgi?id=111615
[fdo#111656]: https://bugs.freedesktop.org/show_bug.cgi?id=111656
[fdo#111825]: https://bugs.freedesktop.org/show_bug.cgi?id=111825
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[fdo#112054]: https://bugs.freedesktop.org/show_bug.cgi?id=112054
[fdo#112283]: https://bugs.freedesktop.org/show_bug.cgi?id=112283
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1155]: https://gitlab.freedesktop.org/drm/intel/issues/1155
[i915#1257]: https://gitlab.freedesktop.org/drm/intel/issues/1257
[i915#132]: https://gitlab.freedesktop.org/drm/intel/issues/132
[i915#1397]: https://gitlab.freedesktop.org/drm/intel/issues/1397
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1825]: https://gitlab.freedesktop.org/drm/intel/issues/1825
[i915#1839]: https://gitlab.freedesktop.org/drm/intel/issues/1839
[i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
[i915#1849]: https://gitlab.freedesktop.org/drm/intel/issues/1849
[i915#1902]: https://gitlab.freedesktop.org/drm/intel/issues/1902
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2410]: https://gitlab.freedesktop.org/drm/intel/issues/2410
[i915#2433]: https://gitlab.freedesktop.org/drm/intel/issues/2433
[i915#2434]: https://gitlab.freedesktop.org/drm/intel/issues/2434
[i915#2435]: https://gitlab.freedesktop.org/drm/intel/issues/2435
[i915#2436]: https://gitlab.freedesktop.org/drm/intel/issues/2436
[i915#2437]: https://gitlab.freedesktop.org/drm/intel/issues/2437
[i915#2521]: https://gitlab.freedesktop.org/drm/intel/issues/2521
[i915#2527]: https://gitlab.freedesktop.org/drm/intel/issues/2527
[i915#2532]: https://gitlab.freedesktop.org/drm/intel/issues/2532
[i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582
[i915#2587]: https://gitlab.freedesktop.org/drm/intel/issues/2587
[i915#2658]: https://gitlab.freedesktop.org/drm/intel/issues/2658
[i915#2672]: https://gitlab.freedesktop.org/drm/intel/issues/2672
[i915#2705]: https://gitlab.freedesktop.org/drm/intel/issues/2705
[i915#280]: https://gitlab.freedesktop.org/drm/intel/issues/280
[i915#284]: https://gitlab.freedesktop.org/drm/intel/issues/284
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2848]: https://gitlab.freedesktop.org/drm/intel/issues/2848
[i915#2920]: https://gitlab.freedesktop.org/drm/intel/issues/2920
[i915#2994]: https://gitlab.freedesktop.org/drm/intel/issues/2994
[i915#3002]: https://gitlab.freedesktop.org/drm/intel/issues/3002
[i915#3012]: https://gitlab.freedesktop.org/drm/intel/issues/3012
[i915#3281]: https://gitlab.freedesktop.org/drm/intel/issues/3281
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3291]: https://gitlab.freedesktop.org/drm/intel/issues/3291
[i915#3297]: https://gitlab.freedesktop.org/drm/intel/issues/3297
[i915#3299]: https://gitlab.freedesktop.org/drm/intel/issues/3299
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#3318]: https://gitlab.freedesktop.org/drm/intel/issues/3318
[i915#3323]: https://gitlab.freedesktop.org/drm/intel/issues/3323
[i915#3359]: https://gitlab.freedesktop.org/drm/intel/issues/3359
[i915#3361]: https://gitlab.freedesktop.org/drm/intel/issues/3361
[i915#3458]: https://gitlab.freedesktop.org/drm/intel/issues/3458
[i915#3469]: https://gitlab.freedesktop.org/drm/intel/issues/3469
[i915#3528]: https://gitlab.freedesktop.org/drm/intel/issues/3528
[i915#3539]: https://gitlab.freedesktop.org/drm/intel/issues/3539
[i915#3546]: https://gitlab.freedesktop.org/drm/intel/issues/3546
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3558]: https://gitlab.freedesktop.org/drm/intel/issues/3558
[i915#3637]: https://gitlab.freedesktop.org/drm/intel/issues/3637
[i915#3638]: https://gitlab.freedesktop.org/drm/intel/issues/3638
[i915#3689]: https://gitlab.freedesktop.org/drm/intel/issues/3689
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#3734]: https://gitlab.freedesktop.org/drm/intel/issues/3734
[i915#3742]: https://gitlab.freedesktop.org/drm/intel/issues/3742
[i915#3840]: https://gitlab.freedesktop.org/drm/intel/issues/3840
[i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#3938]: https://gitlab.freedesktop.org/drm/intel/issues/3938
[i915#3952]: https://gitlab.freedesktop.org/drm/intel/issues/3952
[i915#3955]: https://gitlab.freedesktop.org/drm/intel/issues/3955
[i915#404]: https://gitlab.freedesktop.org/drm/intel/issues/404
[i915#4070]: https://gitlab.freedesktop.org/drm/intel/issues/4070
[i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077
[i915#4078]: https://gitlab.freedesktop.org/drm/intel/issues/4078
[i915#4079]: https://gitlab.freedesktop.org/drm/intel/issues/4079
[i915#4083]: https://gitlab.freedesktop.org/drm/intel/issues/4083
[i915#4098]: https://gitlab.freedesktop.org/drm/intel/issues/4098
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4212]: https://gitlab.freedesktop.org/drm/intel/issues/4212
[i915#4213]: https://gitlab.freedesktop.org/drm/intel/issues/4213
[i915#4258]: https://gitlab.freedesktop.org/drm/intel/issues/4258
[i915#426]: https://gitlab.freedesktop.org/drm/intel/issues/426
[i915#4270]: https://gitlab.freedesktop.org/drm/intel/issues/4270
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4387]: https://gitlab.freedesktop.org/drm/intel/issues/4387
[i915#4391]: https://gitlab.freedesktop.org/drm/intel/issues/4391
[i915#4525]: https://gitlab.freedesktop.org/drm/intel/issues/4525
[i915#4538]: https://gitlab.freedesktop.org/drm/intel/issues/4538
[i915#4565]: https://gitlab.freedesktop.org/drm/intel/issues/4565
[i915#4573]: https://gitlab.freedesktop.org/drm/intel/issues/4573
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4771]: https://gitlab.freedesktop.org/drm/intel/issues/4771
[i915#4812]: https://gitlab.freedesktop.org/drm/intel/issues/4812
[i915#4818]: https://gitlab.freedesktop.org/drm/intel/issues/4818
[i915#4833]: https://gitlab.freedesktop.org/drm/intel/issues/4833
[i915#4852]: https://gitlab.freedesktop.org/drm/intel/issues/4852
[i915#4854]: https://gitlab.freedesktop.org/drm/intel/issues/4854
[i915#4855]: https://gitlab.freedesktop.org/drm/intel/issues/4855
[i915#4859]: https://gitlab.freedesktop.org/drm/intel/issues/4859
[i915#4860]: https://gitlab.freedesktop.org/drm/intel/issues/4860
[i915#4873]: https://gitlab.freedesktop.org/drm/intel/issues/4873
[i915#4879]: https://gitlab.freedesktop.org/drm/intel/issues/4879
[i915#4880]: https://gitlab.freedesktop.org/drm/intel/issues/4880
[i915#4881]: https://gitlab.freedesktop.org/drm/intel/issues/4881
[i915#4884]: https://gitlab.freedesktop.org/drm/intel/issues/4884
[i915#4885]: https://gitlab.freedesktop.org/drm/intel/issues/4885
[i915#4939]: https://gitlab.freedesktop.org/drm/intel/issues/4939
[i915#4958]: https://gitlab.freedesktop.org/drm/intel/issues/4958
[i915#4991]: https://gitlab.freedesktop.org/drm/intel/issues/4991
[i915#5032]: https://gitlab.freedesktop.org/drm/intel/issues/5032
[i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176
[i915#5213]: https://gitlab.freedesktop.org/drm/intel/issues/5213
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#5286]: https://gitlab.freedesktop.org/drm/intel/issues/5286
[i915#5288]: https://gitlab.freedesktop.org/drm/intel/issues/5288
[i915#5289]: https://gitlab.freedesktop.org/drm/intel/issues/5289
[i915#5325]: https://gitlab.freedesktop.org/drm/intel/issues/5325
[i915#5327]: https://gitlab.freedesktop.org/drm/intel/issues/5327
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5334]: https://gitlab.freedesktop.org/drm/intel/issues/5334
[i915#5439]: https://gitlab.freedesktop.org/drm/intel/issues/5439
[i915#5563]: https://gitlab.freedesktop.org/drm/intel/issues/5563
[i915#5566]: https://gitlab.freedesktop.org/drm/intel/issues/5566
[i915#5639]: https://gitlab.freedesktop.org/drm/intel/issues/5639
[i915#5723]: https://gitlab.freedesktop.org/drm/intel/issues/5723
[i915#5784]: https://gitlab.freedesktop.org/drm/intel/issues/5784
[i915#5939]: https://gitlab.freedesktop.org/drm/intel/issues/5939
[i915#6095]: https://gitlab.freedesktop.org/drm/intel/issues/6095
[i915#6227]: https://gitlab.freedesktop.org/drm/intel/issues/6227
[i915#6230]: https://gitlab.freedesktop.org/drm/intel/issues/6230
[i915#6248]: https://gitlab.freedesktop.org/drm/intel/issues/6248
[i915#6268]: https://gitlab.freedesktop.org/drm/intel/issues/6268
[i915#6301]: https://gitlab.freedesktop.org/drm/intel/issues/6301
[i915#6334]: https://gitlab.freedesktop.org/drm/intel/issues/6334
[i915#6335]: https://gitlab.freedesktop.org/drm/intel/issues/6335
[i915#6344]: https://gitlab.freedesktop.org/drm/intel/issues/6344
[i915#6412]: https://gitlab.freedesktop.org/drm/intel/issues/6412
[i915#6433]: https://gitlab.freedesktop.org/drm/intel/issues/6433
[i915#6463]: https://gitlab.freedesktop.org/drm/intel/issues/6463
[i915#6493]: https://gitlab.freedesktop.org/drm/intel/issues/6493
[i915#6497]: https://gitlab.freedesktop.org/drm/intel/issues/6497
[i915#6524]: https://gitlab.freedesktop.org/drm/intel/issues/6524
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#6590]: https://gitlab.freedesktop.org/drm/intel/issues/6590
[i915#6621]: https://gitlab.freedesktop.org/drm/intel/issues/6621
[i915#6946]: https://gitlab.freedesktop.org/drm/intel/issues/6946
[i915#6949]: https://gitlab.freedesktop.org/drm/intel/issues/6949
[i915#6987]: https://gitlab.freedesktop.org/drm/intel/issues/6987
[i915#7036]: https://gitlab.freedesktop.org/drm/intel/issues/7036
[i915#7116]: https://gitlab.freedesktop.org/drm/intel/issues/7116
[i915#7118]: https://gitlab.freedesktop.org/drm/intel/issues/7118
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#7165]: https://gitlab.freedesktop.org/drm/intel/issues/7165
[i915#7178]: https://gitlab.freedesktop.org/drm/intel/issues/7178
[i915#7192]: https://gitlab.freedesktop.org/drm/intel/issues/7192
[i915#7200]: https://gitlab.freedesktop.org/drm/intel/issues/7200
[i915#7205]: https://gitlab.freedesktop.org/drm/intel/issues/7205
[i915#7206]: https://gitlab.freedesktop.org/drm/intel/issues/7206
[i915#7207]: https://gitlab.freedesktop.org/drm/intel/issues/7207
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
Build changes
-------------
* Linux: CI_DRM_12242 -> Patchwork_109612v2
CI-20190529: 20190529
CI_DRM_12242: 075a81b1efd29300194bdf7877e08b6dbe3079d9 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7012: ca6f5bdd537d26692c4b1ca011b8c4f227d95703 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_109612v2: 075a81b1efd29300194bdf7877e08b6dbe3079d9 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/index.html
Re: [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on' (rev2)
Pushed to drm-intel-next.
Thanks for Review.
Br,
Anshuman Gupta.
From: Patchwork <[email protected]>
Sent: Friday, October 14, 2022 7:01 PM
To: Gupta, Anshuman <[email protected]>
Cc: [email protected]
Subject: ✓ Fi.CI.IGT: success for drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on' (rev2)
Patch Details
Series:
drm/i915/dgfx: Temporary hammer to keep autosuspend control 'on' (rev2)
URL:
https://patchwork.freedesktop.org/series/109612/
State:
success
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/index.html
CI Bug Log - changes from CI_DRM_12242_full -> Patchwork_109612v2_full
Summary
SUCCESS
No regressions found.
Participating hosts (9 -> 11)
Additional (2): shard-rkl shard-dg1
Known issues
Here are the changes found in Patchwork_109612v2_full that come from known issues:
CI changes
Possible fixes
• boot:
o shard-skl: (https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl10/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl9/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl9/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl9/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl10/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl9/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl7/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl7/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl7/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl6/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl6/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl6/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl5/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl5/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl10/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl10/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl1/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl5/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl5/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl4/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl4/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl4/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl4/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl1/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl1/boot.html) (https://gitlab.freedesktop.org/drm/intel/issues/5032) -> (https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl1/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl7/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl7/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl6/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl6/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl6/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl5/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl5/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl4/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl4/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl4/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl2/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl2/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl1/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl1/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl10/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl10/boot.html, https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl10/boot.html)
IGT changes
Issues hit
• igt@gem_exec_balancer@parallel-out-fence:
o shard-iclb: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-iclb1/igt@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb8/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/4525)
• igt@gem_exec_fair@basic-none-solo@rcs0:
o shard-apl: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl7/igt@gem_exec_fair@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl8/igt@gem_exec_fair@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/2842)
• igt@gem_exec_fair@basic-none@vcs1:
o shard-iclb: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb1/igt@gem_exec_fair@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/2842)
• igt@gem_exec_fair@basic-pace@vecs0:
o shard-iclb: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-iclb8/igt@gem_exec_fair@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb6/igt@gem_exec_fair@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/2842)
• igt@gem_huc_copy@huc-copy:
o shard-tglb: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-tglb5/igt@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-tglb7/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/2190)
• igt@gem_lmem_swapping@heavy-random:
o shard-skl: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://gitlab.freedesktop.org/drm/intel/issues/4613) +1 similar issue
• igt@gem_userptr_blits@dmabuf-sync:
o shard-skl: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://gitlab.freedesktop.org/drm/intel/issues/3323)
• igt@gen9_exec_parse@allowed-single:
o shard-apl: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl1/igt@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/5566 / https://gitlab.freedesktop.org/drm/intel/issues/716)
• igt@i915_pipe_stress@stress-xrgb8888-untiled:
o shard-apl: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/7036)
• igt@i915_selftest@live@gt_heartbeat:
o shard-apl: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl1/igt@i915_selftest@live@gt_heartbeat.html -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl6/igt@i915_selftest@live@gt_heartbeat.html (https://gitlab.freedesktop.org/drm/intel/issues/5334)
• igt@kms_async_flips@alternate-sync-async-flip@pipe-b-edp-1:
o shard-skl: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl10/igt@kms_async_flips@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl10/igt@kms_async_flips@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/2521) +1 similar issue
• igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_mc_ccs:
o shard-skl: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@kms_ccs@pipe-a-missing-ccs-buffer-y_tiled_gen12_mc_ccs.html (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://gitlab.freedesktop.org/drm/intel/issues/3886)
• igt@kms_ccs@pipe-a-random-ccs-data-y_tiled_gen12_rc_ccs_cc:
o shard-apl: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@kms_ccs@pipe-a-random-ccs-data-y_tiled_gen12_rc_ccs_cc.html (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://gitlab.freedesktop.org/drm/intel/issues/3886) +2 similar issues
o shard-glk: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk3/igt@kms_ccs@pipe-a-random-ccs-data-y_tiled_gen12_rc_ccs_cc.html (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://gitlab.freedesktop.org/drm/intel/issues/3886)
• igt@kms_ccs@pipe-b-bad-rotation-90-4_tiled_dg2_rc_ccs_cc:
o shard-apl: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@kms_ccs@pipe-b-bad-rotation-90-4_tiled_dg2_rc_ccs_cc.html (https://bugs.freedesktop.org/show_bug.cgi?id=109271) +52 similar issues
• igt@kms_ccs@pipe-c-crc-sprite-planes-basic-4_tiled_dg2_rc_ccs:
o shard-glk: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk3/igt@kms_ccs@pipe-c-crc-sprite-planes-basic-4_tiled_dg2_rc_ccs.html (https://bugs.freedesktop.org/show_bug.cgi?id=109271) +27 similar issues
• igt@kms_chamelium@hdmi-edid-change-during-suspend:
o shard-skl: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://bugs.freedesktop.org/show_bug.cgi?id=111827) +3 similar issues
• igt@kms_chamelium@hdmi-hpd-storm:
o shard-apl: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://bugs.freedesktop.org/show_bug.cgi?id=111827) +3 similar issues
o shard-glk: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk3/igt@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://bugs.freedesktop.org/show_bug.cgi?id=111827)
• igt@kms_color@ctm-0-25:
o shard-skl: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://gitlab.freedesktop.org/drm/intel/issues/3546)
• igt@kms_fbcon_fbt@psr-suspend:
o shard-skl: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/4939 / https://gitlab.freedesktop.org/drm/intel/issues/7192)
• igt@kms_flip@2x-flip-vs-expired-vblank-interruptible@bc-hdmi-a1-hdmi-a2:
o shard-glk: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-glk9/igt@kms_flip@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk7/igt@kms_flip@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/79)
• igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible@c-edp1:
o shard-skl: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl6/igt@kms_flip@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl2/igt@kms_flip@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/2122) +1 similar issue
• igt@kms_flip@flip-vs-expired-vblank@c-edp1:
o shard-skl: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl1/igt@kms_flip@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@kms_flip@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/79) +1 similar issue
• igt@kms_flip_scaled_crc@flip-32bpp-xtile-to-64bpp-xtile-downscaling@pipe-a-default-mode:
o shard-iclb: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb2/igt@kms_flip_scaled_crc@flip-32bpp-xtile-to-64bpp-xtile-downscaling@pipe-a-default-mode.html (https://gitlab.freedesktop.org/drm/intel/issues/3555)
• igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tile-upscaling@pipe-a-default-mode:
o shard-iclb: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-4tile-to-32bpp-4tile-upscaling@pipe-a-default-mode.html (https://gitlab.freedesktop.org/drm/intel/issues/2672) +2 similar issues
• igt@kms_flip_scaled_crc@flip-64bpp-yftile-to-16bpp-yftile-upscaling@pipe-a-valid-mode:
o shard-iclb: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb5/igt@kms_flip_scaled_crc@flip-64bpp-yftile-to-16bpp-yftile-upscaling@pipe-a-valid-mode.html (https://gitlab.freedesktop.org/drm/intel/issues/2587 / https://gitlab.freedesktop.org/drm/intel/issues/2672) +1 similar issue
• igt@kms_frontbuffer_tracking@fbcpsr-suspend:
o shard-skl: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271) +116 similar issues
• igt@kms_plane_alpha_blend@alpha-opaque-fb@pipe-a-dp-1:
o shard-apl: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@kms_plane_alpha_blend@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/4573) +2 similar issues
• igt@kms_psr2_su@page_flip-p010@pipe-b-edp-1:
o shard-iclb: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb2/igt@kms_psr2_su@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/5939) +2 similar issues
• igt@kms_psr2_su@page_flip-xrgb8888:
o shard-skl: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@kms_psr2_su@page_flip-xrgb8888.html (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://gitlab.freedesktop.org/drm/intel/issues/658) +2 similar issues
• igt@kms_psr@psr2_primary_mmap_cpu:
o shard-iclb: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-iclb2/igt@kms_psr@psr2_primary_mmap_cpu.html -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb1/igt@kms_psr@psr2_primary_mmap_cpu.html (https://bugs.freedesktop.org/show_bug.cgi?id=109441)
• igt@kms_vblank@pipe-b-ts-continuation-suspend:
o shard-apl: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl8/igt@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl3/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/180) +2 similar issues
• igt@kms_writeback@writeback-invalid-parameters:
o shard-skl: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl9/igt@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://gitlab.freedesktop.org/drm/intel/issues/2437)
• igt@perf@blocking:
o shard-skl: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl6/igt@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl6/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/1542)
• igt@perf@polling-parameterized:
o shard-glk: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-glk6/igt@[email protected] -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk6/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/5639)
• igt@sysfs_clients@create:
o shard-apl: NOTRUN -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://gitlab.freedesktop.org/drm/intel/issues/2994)
Possible fixes
• igt@gem_exec_balancer@parallel-balancer:
o shard-iclb: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-iclb5/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/4525) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb2/igt@[email protected]
• igt@gem_exec_fair@basic-flow@rcs0:
o shard-tglb: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-tglb7/igt@gem_exec_fair@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/2842) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-tglb1/igt@gem_exec_fair@[email protected]
• igt@gem_exec_fair@basic-pace-share@rcs0:
o shard-glk: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-glk3/igt@gem_exec_fair@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/2842) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk5/igt@gem_exec_fair@[email protected]
• igt@gen9_exec_parse@allowed-all:
o shard-apl: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl2/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/5566 / https://gitlab.freedesktop.org/drm/intel/issues/716) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@[email protected]
• igt@kms_cursor_legacy@flip-vs-cursor-crc-atomic:
o shard-skl: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl6/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/2346) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl6/igt@[email protected]
• igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions:
o shard-glk: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-glk9/igt@kms_cursor_legacy@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/2346) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk7/igt@kms_cursor_legacy@[email protected]
• igt@kms_flip@busy-flip@c-edp1:
o shard-skl: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl5/igt@kms_flip@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/7200) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl7/igt@kms_flip@[email protected] +1 similar issue
• igt@kms_hdr@bpc-switch-suspend@pipe-a-dp-1:
o shard-apl: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl3/igt@kms_hdr@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/180) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@kms_hdr@[email protected] +1 similar issue
• igt@perf@polling-parameterized:
o shard-skl: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl10/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/5639) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl10/igt@[email protected]
• igt@perf@stress-open-close:
o shard-glk: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-glk1/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/5213) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk3/igt@[email protected]
Warnings
• igt@dmabuf@all@dma_fence_chain:
o shard-skl: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl6/igt@dmabuf@all@dma_fence_chain.html (https://gitlab.freedesktop.org/drm/intel/issues/6949 / https://gitlab.freedesktop.org/drm/intel/issues/7165) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl6/igt@dmabuf@all@dma_fence_chain.html (https://gitlab.freedesktop.org/drm/intel/issues/6949 / https://gitlab.freedesktop.org/drm/intel/issues/7165 / https://gitlab.freedesktop.org/drm/intel/issues/7192)
• igt@gem_exec_fair@basic-throttle@rcs0:
o shard-tglb: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-tglb3/igt@gem_exec_fair@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/2842) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-tglb2/igt@gem_exec_fair@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/2848) +2 similar issues
• igt@kms_big_fb@y-tiled-max-hw-stride-64bpp-rotate-0-hflip:
o shard-apl: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl7/igt@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl8/igt@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://gitlab.freedesktop.org/drm/intel/issues/7206)
o shard-glk: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-glk9/igt@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk7/igt@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://gitlab.freedesktop.org/drm/intel/issues/7206)
• igt@kms_ccs@pipe-b-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc:
o shard-skl: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl1/igt@kms_ccs@pipe-b-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc.html (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://gitlab.freedesktop.org/drm/intel/issues/3886) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl5/igt@kms_ccs@pipe-b-missing-ccs-buffer-y_tiled_gen12_rc_ccs_cc.html (https://gitlab.freedesktop.org/drm/intel/issues/7192)
• igt@kms_dsc@dsc-with-bpc-formats:
o shard-glk: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-glk9/igt@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-glk7/igt@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://gitlab.freedesktop.org/drm/intel/issues/7205)
o shard-skl: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl5/igt@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl7/igt@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://gitlab.freedesktop.org/drm/intel/issues/7205)
o shard-apl: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl7/igt@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl8/igt@[email protected] (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://gitlab.freedesktop.org/drm/intel/issues/7205)
• igt@kms_flip_scaled_crc@flip-32bpp-yftileccs-to-64bpp-yftile-upscaling@pipe-a-default-mode:
o shard-skl: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-skl9/igt@kms_flip_scaled_crc@flip-32bpp-yftileccs-to-64bpp-yftile-upscaling@pipe-a-default-mode.html (https://bugs.freedesktop.org/show_bug.cgi?id=109271) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-skl1/igt@kms_flip_scaled_crc@flip-32bpp-yftileccs-to-64bpp-yftile-upscaling@pipe-a-default-mode.html (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://gitlab.freedesktop.org/drm/intel/issues/7207)
• igt@kms_psr2_sf@cursor-plane-move-continuous-exceed-fully-sf:
o shard-iclb: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-iclb5/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/658) -> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-iclb2/igt@[email protected] (https://gitlab.freedesktop.org/drm/intel/issues/2920)
• igt@runner@aborted:
o shard-apl: (https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl2/igt@[email protected], https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl6/igt@[email protected], https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl8/igt@[email protected], https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl3/igt@[email protected], https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12242/shard-apl3/igt@[email protected]) (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://gitlab.freedesktop.org/drm/intel/issues/3002 / https://gitlab.freedesktop.org/drm/intel/issues/4312) -> (https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl3/igt@[email protected], https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl6/igt@[email protected], https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl3/igt@[email protected], https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@[email protected], https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl7/igt@[email protected], https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_109612v2/shard-apl1/igt@[email protected]) (https://bugs.freedesktop.org/show_bug.cgi?id=109271 / https://gitlab.freedesktop.org/drm/intel/issues/180 / https://gitlab.freedesktop.org/drm/intel/issues/3002 / https://gitlab.freedesktop.org/drm/intel/issues/4312)
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
Build changes
• Linux: CI_DRM_12242 -> Patchwork_109612v2
CI-20190529: 20190529CI_DRM_12242: 075a81b1efd29300194bdf7877e08b6dbe3079d9 @ git://anongit.freedesktop.org/gfx-ci/linuxIGT_7012: ca6f5bdd537d26692c4b1ca011b8c4f227d95703 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.gitPatchwork_109612v2: 075a81b1efd29300194bdf7877e08b6dbe3079d9 @ git://anongit.freedesktop.org/gfx-ci/linuxpiglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit