lib/i915: Fix gem_has_execlists to match description
PATCH 1/1 lib/i915: Fix gem_has_execlists to match description
Driver is using execlists if it is not using GuC submission. GEM_SUBMISSION_EXECLISTS flag indicates if execlist submission is available, not if it is being used by the driver.
--- lib/i915/gem_submission.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
lib/i915/gem_submission.c +1 -1
@@ -153,7 +153,7 @@ bool gem_has_semaphores(int fd)*/ bool gem_has_execlists (int fd) { -return gem_submission_method (fd) &GEM_SUBMISSION_EXECLISTS ; +return !gem_has_guc_submission (fd); }/**
Signature · 1 line
2.33.0
Quoted 14 lines · Ashutosh Dixit
Driver is using execlists if it is not using GuC submission.
GEM_SUBMISSION_EXECLISTSflag indicates if execlist submission is available, not if it is being used by the driver.Signed-off-by Ashutosh Dixit <[email protected]>--- lib/i915/gem_submission.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)lib/i915/gem_submission.c +0
-0
lib/i915/gem_submission.c bool gem_has_semaphores(int fd) · line 156
Quoted 5 lines
lib/i915/gem_submission.c +1
-1@@ -153,7 +153,7 @@ bool gem_has_semaphores(int fd)*/ bool gem_has_execlists (int fd) { -return gem_submission_method (fd) &GEM_SUBMISSION_EXECLISTS ; +return !gem_has_guc_submission (fd);
Don't we use ring submission on older platforms?
Isn't the better fix to just not set the EXECLIST flag when GuC submission is detected?
John.
Quoted 3 lines
lib/i915/gem_submission.c +0
-0}/**
Quoted 11 lines · John Harrison
Quoted 9 lines · Ashutosh Dixit
Driver is using execlists if it is not using GuC submission.
GEM_SUBMISSION_EXECLISTSflag indicates if execlist submission is available, not if it is being used by the driver.Signed-off-by Ashutosh Dixit <[email protected]>--- lib/i915/gem_submission.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Quoted 12 lines
lib/i915/gem_submission.c bool gem_has_semaphores(int fd) · line 156
Quoted 10 lines
lib/i915/gem_submission.c +1
-1@@ -153,7 +153,7 @@ bool gem_has_semaphores(int fd)*/ bool gem_has_execlists (int fd) { -return gem_submission_method (fd) &GEM_SUBMISSION_EXECLISTS ; +return !gem_has_guc_submission (fd);Don't we use ring submission on older platforms?
Hmm, I wasn't aware that there was yet another submission method :/
So execlist submission is only available for gen >= 8 as the code says, in case anyone knows?
Quoted 2 lines
Isn't the better fix to just not set the EXECLIST flag when GuC submission is detected?
Yes, let me post this patch too. Thanks!
Quoted 22 lines · Ashutosh
Quoted 10 lines · John Harrison
Quoted 9 lines · Ashutosh Dixit
Driver is using execlists if it is not using GuC submission.
GEM_SUBMISSION_EXECLISTSflag indicates if execlist submission is available, not if it is being used by the driver.Signed-off-by Ashutosh Dixit <[email protected]>--- lib/i915/gem_submission.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)Quoted 11 lines
lib/i915/gem_submission.c bool gem_has_semaphores(int fd) · line 156
Quoted 10 lines
lib/i915/gem_submission.c +1
-1@@ -153,7 +153,7 @@ bool gem_has_semaphores(int fd)*/ bool gem_has_execlists (int fd) { -return gem_submission_method (fd) &GEM_SUBMISSION_EXECLISTS ; +return !gem_has_guc_submission (fd);Don't we use ring submission on older platforms?
Quoted 4 lines
Hmm, I wasn't aware that there was yet another submission method :/
So execlist submission is only available for gen >= 8 as the code says, in case anyone knows?
Yes. Execlists was new feature of the hardware not all that long ago (ELSP and all that). Gen8 sounds plausible.
Of course, it all depends why the code is asking the question? Does it really need to know what the submission hardware is? Or is it actually asking about the scheduling algorithm (as is the case for gem_exec_fair). Or something else entirely? The scheduler question is going to change again when we move to using the DRM scheduler instead of our own private one in the execlist code. Currently though, I would assume we use the execlist scheduler for ring submission but certainly not for GuC submission (because the scheduler is in the hardware).
John.
Quoted 4 lines
Quoted 3 lines
Isn't the better fix to just not set the EXECLIST flag when GuC submission is detected?
Yes, let me post this patch too. Thanks!
Quoted 23 lines · John Harrison
Quoted 22 lines · Ashutosh
Quoted 21 lines · John Harrison
Quoted 14 lines · Ashutosh Dixit
Driver is using execlists if it is not using GuC submission.
GEM_SUBMISSION_EXECLISTSflag indicates if execlist submission is available, not if it is being used by the driver.Signed-off-by Ashutosh Dixit <[email protected]>---
lib/i915/gem_submission.c| 2 +-1 file changed, 1 insertion(+), 1 deletion(-)lib/i915/gem_submission.c +0
-0lib/i915/gem_submission.c bool gem_has_semaphores(int fd) · line 156
Quoted 5 lines
lib/i915/gem_submission.c +1
-1@@ -153,7 +153,7 @@ bool gem_has_semaphores(int fd)*/ bool gem_has_execlists(int fd) { - return gem_submission_method(fd) & GEM_SUBMISSION_EXECLISTS; + return !gem_has_guc_submission(fd);Don't we use ring submission on older platforms?
Quoted 5 lines
Quoted 4 lines
Hmm, I wasn't aware that there was yet another submission method :/
So execlist submission is only available for gen >= 8 as the code says, in case anyone knows?
Yes. Execlists was new feature of the hardware not all that long ago (ELSP and all that). Gen8 sounds plausible.
Yes Gen8+.
Quoted 1 line
Of course, it all depends why the code is asking the question? Does it really need to know what the submission hardware is? Or is it actually asking about the scheduling algorithm (as is the case for
gem_exec_fair). Or something else entirely? The scheduler question is going to change again when we move to using the DRM scheduler instead of our own private one in the execlist code. Currently though, I would assume we use the execlist scheduler for ring submission but certainly not for GuC submission (because the scheduler is in the hardware).
Nope, no scheduling with ringbuffer backend.
There is I915_PARAM_HAS_SCHEDULER and respective IGT helpers to query what kind of scheduling is supported on the device in question.
It will be on a test per test basis why it is asking the question and what would be the appropriate test.
Regards,
Tvrtko
Quoted 8 lines
John.
Quoted 4 lines
Quoted 3 lines
Isn't the better fix to just not set the EXECLIST flag when GuC submission is detected?
Yes, let me post this patch too. Thanks!
Quoted 21 lines · Tvrtko Ursulin
Quoted 9 lines
Quoted 7 lines
Quoted 2 lines
Don't we use ring submission on older platforms?
Hmm, I wasn't aware that there was yet another submission method :/
So execlist submission is only available for gen >= 8 as the code says, in
case anyone knows?Yes. Execlists was new feature of the hardware not all that long ago (ELSP and all that). Gen8 sounds plausible.
Yes Gen8+.
Quoted 8 lines
Of course, it all depends why the code is asking the question? Does it really need to know what the submission hardware is? Or is it actually asking about the scheduling algorithm (as is the case for
gem_exec_fair). Or something else entirely? The scheduler question is going to change again when we move to using the DRM scheduler instead of our own private one in the execlist code. Currently though, I would assume we use the execlist scheduler for ring submission but certainly not for GuC submission (because the scheduler is in the hardware).
Quoted 7 lines
Nope, no scheduling with ringbuffer backend.
There is
I915_PARAM_HAS_SCHEDULERand respective IGT helpers to query what kind of scheduling is supported on the device in question.It will be on a test per test basis why it is asking the question and what would be the appropriate test.
This patch is abandoned in favor of:
https://patchwork.freedesktop.org/series/95906/
Would it be possible to get a review on that? Thanks.
Quoted 32 lines · Tvrtko Ursulin
Quoted 23 lines · John Harrison
Quoted 22 lines · Ashutosh
Quoted 21 lines · John Harrison
Quoted 14 lines · Ashutosh Dixit
Driver is using execlists if it is not using GuC submission.
GEM_SUBMISSION_EXECLISTSflag indicates if execlist submission is available, not if it is being used by the driver.Signed-off-by Ashutosh Dixit <[email protected]>---
lib/i915/gem_submission.c| 2 +-1 file changed, 1 insertion(+), 1 deletion(-)lib/i915/gem_submission.c +0
-0lib/i915/gem_submission.c bool gem_has_semaphores(int fd) · line 156
Quoted 5 lines
lib/i915/gem_submission.c +1
-1@@ -153,7 +153,7 @@ bool gem_has_semaphores(int fd)*/ bool gem_has_execlists(int fd) { - return gem_submission_method(fd) & GEM_SUBMISSION_EXECLISTS; + return !gem_has_guc_submission(fd);Don't we use ring submission on older platforms?
Quoted 5 lines
Quoted 4 lines
Hmm, I wasn't aware that there was yet another submission method :/
So execlist submission is only available for gen >= 8 as the code says, in case anyone knows?
Yes. Execlists was new feature of the hardware not all that long ago (ELSP and all that). Gen8 sounds plausible.
Yes Gen8+.
Quoted 8 lines
Quoted 1 line
Of course, it all depends why the code is asking the question? Does it really need to know what the submission hardware is? Or is it actually asking about the scheduling algorithm (as is the case for
gem_exec_fair). Or something else entirely? The scheduler question is going to change again when we move to using the DRM scheduler instead of our own private one in the execlist code. Currently though, I would assume we use the execlist scheduler for ring submission but certainly not for GuC submission (because the scheduler is in the hardware).Nope, no scheduling with ringbuffer backend.
There is
I915_PARAM_HAS_SCHEDULERand respective IGT helpers to query what kind of scheduling is supported on the device in question.It will be on a test per test basis why it is asking the question and what would be the appropriate test.
Are you saying that we need to add an extra flag (or even enum field) to say what type of scheduler is supported? As in 'fair', 'round robin', 'DRM', etc.?
I'm not seeing any scheduling _CAP flag that would be relevant to differentiating between the GuC and the execlist scheduler implementations.
John.
Quoted 12 lines
Regards,
Tvrtko
Quoted 8 lines
John.
Quoted 4 lines
Quoted 3 lines
Isn't the better fix to just not set the EXECLIST flag when GuC submission is detected?
Yes, let me post this patch too. Thanks!
Quoted 35 lines · John Harrison
Quoted 34 lines · Tvrtko Ursulin
Quoted 23 lines · John Harrison
Quoted 22 lines · Ashutosh
Quoted 21 lines · John Harrison
Quoted 14 lines · Ashutosh Dixit
Driver is using execlists if it is not using GuC submission.
GEM_SUBMISSION_EXECLISTSflag indicates if execlist submission is available, not if it is being used by the driver.Signed-off-by Ashutosh Dixit <[email protected]>---
lib/i915/gem_submission.c| 2 +-1 file changed, 1 insertion(+), 1 deletion(-)lib/i915/gem_submission.c +0
-0lib/i915/gem_submission.c bool gem_has_semaphores(int fd) · line 156
Quoted 5 lines
lib/i915/gem_submission.c +1
-1@@ -153,7 +153,7 @@ bool gem_has_semaphores(int fd)*/ bool gem_has_execlists(int fd) { - return gem_submission_method(fd) & GEM_SUBMISSION_EXECLISTS; + return !gem_has_guc_submission(fd);Don't we use ring submission on older platforms?
Quoted 5 lines
Quoted 4 lines
Hmm, I wasn't aware that there was yet another submission method :/
So execlist submission is only available for gen >= 8 as the code says, in case anyone knows?
Yes. Execlists was new feature of the hardware not all that long ago (ELSP and all that). Gen8 sounds plausible.
Yes Gen8+.
Quoted 1 line
Of course, it all depends why the code is asking the question? Does it really need to know what the submission hardware is? Or is it actually asking about the scheduling algorithm (as is the case for
gem_exec_fair). Or something else entirely? The scheduler question is going to change again when we move to using the DRM scheduler instead of our own private one in the execlist code. Currently though, I would assume we use the execlist scheduler for ring submission but certainly not for GuC submission (because the scheduler is in the hardware).
Quoted 7 lines
Quoted 6 lines
Nope, no scheduling with ringbuffer backend.
There is
I915_PARAM_HAS_SCHEDULERand respective IGT helpers to query what kind of scheduling is supported on the device in question.It will be on a test per test basis why it is asking the question and what would be the appropriate test.
Are you saying that we need to add an extra flag (or even enum field) to say what type of scheduler is supported? As in 'fair', 'round robin', 'DRM', etc.?
No strong opinion. I was just saying what exists today, and noticing gem_exec_fair does not only fail with the GuC.
If a new feature test is needed, which is not possible via all that is currently available, then the question is how/where to expose the data.
But in principle is it not okay even to have a failing test since ci known failure list takes care of that? Because I know there is a customer requirement for fair scheduling already so it sounds better to highlight in the CI matrix we are not there yet.
Regards,
Tvrtko
Quoted 18 lines
I'm not seeing any scheduling
_CAPflag that would be relevant to differentiating between the GuC and the execlist scheduler implementations.John.
Quoted 12 lines
Regards,
Tvrtko
Quoted 8 lines
John.
Quoted 4 lines
Quoted 3 lines
Isn't the better fix to just not set the EXECLIST flag when GuC submission is detected?
Yes, let me post this patch too. Thanks!
Quoted 38 lines · Tvrtko Ursulin
Quoted 37 lines · John Harrison
Quoted 36 lines · Tvrtko Ursulin
Quoted 23 lines · John Harrison
Quoted 22 lines · Ashutosh
Quoted 21 lines · John Harrison
Quoted 14 lines · Ashutosh Dixit
Driver is using execlists if it is not using GuC submission.
GEM_SUBMISSION_EXECLISTSflag indicates if execlist submission is available, not if it is being used by the driver.Signed-off-by Ashutosh Dixit <[email protected]>---
lib/i915/gem_submission.c| 2 +-1 file changed, 1 insertion(+), 1 deletion(-)lib/i915/gem_submission.c +0
-0lib/i915/gem_submission.c bool gem_has_semaphores(int fd) · line 156
Quoted 5 lines
lib/i915/gem_submission.c +1
-1@@ -153,7 +153,7 @@ bool gem_has_semaphores(int fd)*/ bool gem_has_execlists(int fd) { - return gem_submission_method(fd) & GEM_SUBMISSION_EXECLISTS; + return !gem_has_guc_submission(fd);Don't we use ring submission on older platforms?
Quoted 5 lines
Quoted 4 lines
Hmm, I wasn't aware that there was yet another submission method :/
So execlist submission is only available for gen >= 8 as the code says, in case anyone knows?
Yes. Execlists was new feature of the hardware not all that long ago (ELSP and all that). Gen8 sounds plausible.
Yes Gen8+.
Quoted 1 line
Of course, it all depends why the code is asking the question? Does it really need to know what the submission hardware is? Or is it actually asking about the scheduling algorithm (as is the case for
gem_exec_fair). Or something else entirely? The scheduler question is going to change again when we move to using the DRM scheduler instead of our own private one in the execlist code. Currently though, I would assume we use the execlist scheduler for ring submission but certainly not for GuC submission (because the scheduler is in the hardware).Nope, no scheduling with ringbuffer backend.
Quoted 7 lines
Quoted 5 lines
Quoted 4 lines
There is
I915_PARAM_HAS_SCHEDULERand respective IGT helpers to query what kind of scheduling is supported on the device in question.It will be on a test per test basis why it is asking the question and what would be the appropriate test.
Are you saying that we need to add an extra flag (or even enum field) to say what type of scheduler is supported? As in 'fair', 'round robin', 'DRM', etc.?
No strong opinion. I was just saying what exists today,
Okay. I was also thinking that extending/adding a UAPI for this is not going to fly anyway because we have no UMD use case for it. It would be purely for the IGT. I think just skipping on GuC is the best way forward for the moment. As/when we have a customer requirement for a different scheduling algorithm, the test can be re-visited and updated to match.
Quoted 1 line
and noticing
gem_exec_fairdoes not only fail with the GuC.
Not my problem, guv ;)
My understanding is that it is supposed to pass in execlist mode. As to whether any failures are test issues or KMD issues I don't know. But that would need to be investigated by someone who knows the test and/or the execlist scheduler. I am neither of those people.
Quoted 4 lines
If a new feature test is needed, which is not possible via all that is currently available, then the question is how/where to expose the data.
But in principle is it not okay even to have a failing test since ci known failure list takes care of that? Because I know there is a customer requirement for fair scheduling already so it sounds better to highlight in the CI matrix we are not there yet.
There *was* a customer requirement. I don't believe that exists any more. At least, not the specific customer on the specific product that was the reason for adding this test.
For execlist failures, as above. My view is to leave them as sporadic failures and whoever is assigned to fix them can fix them. For GuC submission, it is a known product difference. No need to track that as an IGT failure. It is tracked at the program management level as part of the feature list for each platform / requirement list for each customer.
John.
Quoted 23 lines
Regards,
Tvrtko
Quoted 18 lines
I'm not seeing any scheduling
_CAPflag that would be relevant to differentiating between the GuC and the execlist scheduler implementations.John.
Quoted 12 lines
Regards,
Tvrtko
Quoted 8 lines
John.
Quoted 4 lines
Quoted 3 lines
Isn't the better fix to just not set the EXECLIST flag when GuC submission is detected?
Yes, let me post this patch too. Thanks!
Quoted 15 lines · Ashutosh Dixit
Driver is using execlists if it is not using GuC submission.
GEM_SUBMISSION_EXECLISTSflag indicates if execlist submission is available, not if it is being used by the driver.Signed-off-by Ashutosh Dixit <[email protected]>--- lib/i915/gem_submission.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)lib/i915/gem_submission.c +0
-0
lib/i915/gem_submission.c bool gem_has_semaphores(int fd) · line 156
Quoted 5 lines
lib/i915/gem_submission.c +1
-1@@ -153,7 +153,7 @@ bool gem_has_semaphores(int fd)*/ bool gem_has_execlists (int fd) { -return gem_submission_method (fd) &GEM_SUBMISSION_EXECLISTS ; +return !gem_has_guc_submission (fd);
Could the reviewers also check if anything needs to be done for these two call sites for gem_has_execlists(). Thanks!
*** tests/i915/gem_ctx_shared.c:
disjoint_timelines[162] igt_require(gem_has_execlists(i915));
*** tests/i915/gem_watchdog.c:
virtual[225] igt_require(gem_has_execlists(i915));
Patchwork
CI[igt-dev] ✓ Fi.CI.BAT: success for lib/i915: Fix gem_has_execlists to match description
In reply to Ashutosh Dixit== Series Details ==
== Series Details ==
Series: lib/i915: Fix gem_has_execlists to match description
URL : https://patchwork.freedesktop.org/series/95903/
State : success
== Summary ==
CI Bug Log - changes from IGT_6251 -> IGTPW_6327
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/index.html
Known issues
------------
Here are the changes found in IGTPW_6327 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@amdgpu/amd_basic@semaphore:
- fi-bdw-5557u: NOTRUN -> [SKIP][1] ([fdo#109271]) +23 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/fi-bdw-5557u/igt@amdgpu/[email protected]
* igt@gem_exec_suspend@basic-s3:
- fi-tgl-1115g4: [PASS][2] -> [FAIL][3] ([i915#1888])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/fi-tgl-1115g4/igt@[email protected]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/fi-tgl-1115g4/igt@[email protected]
#### Possible fixes ####
* igt@debugfs_test@read_all_entries:
- fi-kbl-soraka: [DMESG-WARN][4] ([i915#1982] / [i915#262]) -> [PASS][5]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/fi-kbl-soraka/igt@debugfs_test@read_all_entries.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/fi-kbl-soraka/igt@debugfs_test@read_all_entries.html
* igt@kms_flip@basic-flip-vs-modeset@c-dp1:
- fi-cfl-8109u: [FAIL][6] ([i915#4165]) -> [PASS][7]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/fi-cfl-8109u/igt@kms_flip@[email protected]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/fi-cfl-8109u/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@basic:
- fi-cml-u2: [DMESG-WARN][8] ([i915#4269]) -> [PASS][9]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/fi-cml-u2/igt@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/fi-cml-u2/igt@[email protected]
- fi-cfl-8109u: [FAIL][10] ([i915#2546]) -> [PASS][11]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/fi-cfl-8109u/igt@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/fi-cfl-8109u/igt@[email protected]
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2546]: https://gitlab.freedesktop.org/drm/intel/issues/2546
[i915#262]: https://gitlab.freedesktop.org/drm/intel/issues/262
[i915#4165]: https://gitlab.freedesktop.org/drm/intel/issues/4165
[i915#4269]: https://gitlab.freedesktop.org/drm/intel/issues/4269
Participating hosts (39 -> 37)
------------------------------
Missing (2): fi-bsw-cyan fi-hsw-4200u
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_6251 -> IGTPW_6327
CI-20190529: 20190529
CI_DRM_10744: dc405215cfabb6f13490cbdceb1f6e831e8a8596 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_6327: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/index.html
IGT_6251: 01b6be842d74fb86f3226acb4ddcb85231f4b161 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/index.html
Patchwork
CI[igt-dev] ✗ Fi.CI.IGT: failure for lib/i915: Fix gem_has_execlists to match description
In reply to Ashutosh Dixit== Series Details ==
== Series Details ==
Series: lib/i915: Fix gem_has_execlists to match description
URL : https://patchwork.freedesktop.org/series/95903/
State : failure
== Summary ==
CI Bug Log - changes from IGT_6251_full -> IGTPW_6327_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_6327_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in IGTPW_6327_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_6327_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_bw@linear-tiling-3-displays-2560x1440p:
- shard-snb: NOTRUN -> [FAIL][1] +3 similar issues
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-snb7/igt@[email protected]
Known issues
------------
Here are the changes found in IGTPW_6327_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@feature_discovery@chamelium:
- shard-iclb: NOTRUN -> [SKIP][2] ([fdo#111827])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb2/igt@[email protected]
* igt@gem_ctx_persistence@legacy-engines-mixed:
- shard-snb: NOTRUN -> [SKIP][3] ([fdo#109271] / [i915#1099]) +5 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-snb5/igt@[email protected]
* igt@gem_eio@unwedge-stress:
- shard-tglb: NOTRUN -> [TIMEOUT][4] ([i915#2369] / [i915#3063] / [i915#3648])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb2/igt@[email protected]
- shard-iclb: NOTRUN -> [TIMEOUT][5] ([i915#2369] / [i915#2481] / [i915#3070])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb4/igt@[email protected]
- shard-snb: NOTRUN -> [FAIL][6] ([i915#3354])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-snb5/igt@[email protected]
* igt@gem_exec_fair@basic-flow@rcs0:
- shard-tglb: [PASS][7] -> [FAIL][8] ([i915#2842]) +1 similar issue
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-tglb5/igt@gem_exec_fair@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb1/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none@vcs0:
- shard-apl: NOTRUN -> [FAIL][9] ([i915#2842])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-apl6/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@vecs0:
- shard-kbl: [PASS][10] -> [FAIL][11] ([i915#2842]) +2 similar issues
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-kbl3/igt@gem_exec_fair@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-kbl7/igt@gem_exec_fair@[email protected]
* igt@gem_exec_gttfill@all:
- shard-glk: [PASS][12] -> [DMESG-WARN][13] ([i915#118])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-glk5/igt@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-glk2/igt@[email protected]
* igt@gem_exec_params@no-blt:
- shard-tglb: NOTRUN -> [SKIP][14] ([fdo#109283])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb7/igt@[email protected]
* igt@gem_ppgtt@flink-and-close-vma-leak:
- shard-glk: [PASS][15] -> [FAIL][16] ([i915#644])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-glk8/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-glk8/igt@[email protected]
* igt@gem_pwrite@basic-exhaustion:
- shard-apl: NOTRUN -> [WARN][17] ([i915#2658])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-apl6/igt@[email protected]
* igt@gem_pxp@reject-modify-context-protection-off-3:
- shard-iclb: NOTRUN -> [SKIP][18] ([i915#4270]) +2 similar issues
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb3/igt@[email protected]
* igt@gem_pxp@reject-modify-context-protection-on:
- shard-tglb: NOTRUN -> [SKIP][19] ([i915#4270]) +1 similar issue
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb1/igt@[email protected]
* igt@gem_render_copy@y-tiled-mc-ccs-to-vebox-y-tiled:
- shard-iclb: NOTRUN -> [SKIP][20] ([i915#768]) +1 similar issue
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb1/igt@[email protected]
* igt@gem_userptr_blits@input-checking:
- shard-apl: NOTRUN -> [DMESG-WARN][21] ([i915#3002])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-apl6/igt@[email protected]
* igt@gem_userptr_blits@unsync-unmap-cycles:
- shard-tglb: NOTRUN -> [SKIP][22] ([i915#3297])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb7/igt@[email protected]
* igt@gem_userptr_blits@vma-merge:
- shard-apl: NOTRUN -> [FAIL][23] ([i915#3318])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-apl7/igt@[email protected]
* igt@gen7_exec_parse@batch-without-end:
- shard-iclb: NOTRUN -> [SKIP][24] ([fdo#109289]) +2 similar issues
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb6/igt@[email protected]
* igt@gen9_exec_parse@bb-oversize:
- shard-tglb: NOTRUN -> [SKIP][25] ([i915#2856]) +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb3/igt@[email protected]
* igt@i915_pm_rpm@dpms-non-lpsp:
- shard-tglb: NOTRUN -> [SKIP][26] ([fdo#111644] / [i915#1397] / [i915#2411])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb7/igt@[email protected]
* igt@i915_pm_rpm@gem-execbuf-stress-pc8:
- shard-iclb: NOTRUN -> [SKIP][27] ([fdo#109293] / [fdo#109506])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb6/igt@[email protected]
* igt@i915_pm_rpm@modeset-non-lpsp:
- shard-iclb: NOTRUN -> [SKIP][28] ([fdo#110892]) +1 similar issue
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb8/igt@[email protected]
* igt@i915_selftest@live@hangcheck:
- shard-snb: [PASS][29] -> [INCOMPLETE][30] ([i915#3921])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-snb5/igt@i915_selftest@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-snb2/igt@i915_selftest@[email protected]
* igt@kms_atomic_transition@plane-all-modeset-transition:
- shard-tglb: NOTRUN -> [SKIP][31] ([i915#1769])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb5/igt@[email protected]
* igt@kms_big_fb@linear-16bpp-rotate-90:
- shard-iclb: NOTRUN -> [SKIP][32] ([fdo#110725] / [fdo#111614])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb8/igt@[email protected]
* igt@kms_big_fb@x-tiled-32bpp-rotate-270:
- shard-tglb: NOTRUN -> [SKIP][33] ([fdo#111614])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb1/igt@[email protected]
* igt@kms_big_fb@x-tiled-max-hw-stride-64bpp-rotate-180-hflip:
- shard-kbl: NOTRUN -> [SKIP][34] ([fdo#109271] / [i915#3777]) +2 similar issues
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-kbl2/igt@[email protected]
* igt@kms_big_fb@y-tiled-max-hw-stride-32bpp-rotate-0-hflip:
- shard-apl: NOTRUN -> [SKIP][35] ([fdo#109271] / [i915#3777]) +1 similar issue
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-apl7/igt@[email protected]
* igt@kms_big_fb@yf-tiled-8bpp-rotate-270:
- shard-tglb: NOTRUN -> [SKIP][36] ([fdo#111615]) +4 similar issues
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb8/igt@[email protected]
* igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-180-hflip:
- shard-iclb: NOTRUN -> [SKIP][37] ([fdo#110723])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb7/igt@[email protected]
* igt@kms_bw@linear-tiling-2-displays-1920x1080p:
- shard-apl: NOTRUN -> [DMESG-FAIL][38] ([i915#4298]) +2 similar issues
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-apl3/igt@[email protected]
* igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][39] ([i915#3689]) +3 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb6/igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_ccs.html
* igt@kms_ccs@pipe-a-crc-primary-rotation-180-y_tiled_gen12_rc_ccs_cc:
- shard-kbl: NOTRUN -> [SKIP][40] ([fdo#109271] / [i915#3886]) +10 similar issues
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-kbl6/igt@kms_ccs@pipe-a-crc-primary-rotation-180-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-b-bad-aux-stride-y_tiled_gen12_rc_ccs_cc:
- shard-glk: NOTRUN -> [SKIP][41] ([fdo#109271] / [i915#3886]) +3 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-glk8/igt@kms_ccs@pipe-b-bad-aux-stride-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-b-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs_cc:
- shard-apl: NOTRUN -> [SKIP][42] ([fdo#109271] / [i915#3886]) +12 similar issues
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-apl7/igt@kms_ccs@pipe-b-crc-sprite-planes-basic-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-c-crc-primary-basic-y_tiled_gen12_mc_ccs:
- shard-iclb: NOTRUN -> [SKIP][43] ([fdo#109278] / [i915#3886]) +6 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb2/igt@kms_ccs@pipe-c-crc-primary-basic-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-c-missing-ccs-buffer-y_tiled_gen12_mc_ccs:
- shard-tglb: NOTRUN -> [SKIP][44] ([i915#3689] / [i915#3886]) +2 similar issues
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb6/igt@kms_ccs@pipe-c-missing-ccs-buffer-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-d-bad-pixel-format-y_tiled_ccs:
- shard-snb: NOTRUN -> [SKIP][45] ([fdo#109271]) +438 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-snb7/igt@kms_ccs@pipe-d-bad-pixel-format-y_tiled_ccs.html
* igt@kms_ccs@pipe-d-crc-primary-rotation-180-y_tiled_gen12_mc_ccs:
- shard-glk: NOTRUN -> [SKIP][46] ([fdo#109271]) +67 similar issues
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-glk8/igt@kms_ccs@pipe-d-crc-primary-rotation-180-y_tiled_gen12_mc_ccs.html
* igt@kms_chamelium@dp-hpd-storm-disable:
- shard-glk: NOTRUN -> [SKIP][47] ([fdo#109271] / [fdo#111827]) +8 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-glk7/igt@[email protected]
* igt@kms_chamelium@hdmi-edid-read:
- shard-tglb: NOTRUN -> [SKIP][48] ([fdo#109284] / [fdo#111827]) +8 similar issues
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb6/igt@[email protected]
* igt@kms_chamelium@vga-edid-read:
- shard-apl: NOTRUN -> [SKIP][49] ([fdo#109271] / [fdo#111827]) +24 similar issues
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-apl6/igt@[email protected]
* igt@kms_chamelium@vga-hpd-for-each-pipe:
- shard-kbl: NOTRUN -> [SKIP][50] ([fdo#109271] / [fdo#111827]) +12 similar issues
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-kbl6/igt@[email protected]
* igt@kms_chamelium@vga-hpd-with-enabled-mode:
- shard-iclb: NOTRUN -> [SKIP][51] ([fdo#109284] / [fdo#111827]) +6 similar issues
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb2/igt@[email protected]
* igt@kms_color_chamelium@pipe-a-ctm-0-25:
- shard-snb: NOTRUN -> [SKIP][52] ([fdo#109271] / [fdo#111827]) +24 similar issues
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-snb2/igt@[email protected]
* igt@kms_color_chamelium@pipe-d-ctm-0-75:
- shard-iclb: NOTRUN -> [SKIP][53] ([fdo#109278] / [fdo#109284] / [fdo#111827]) +1 similar issue
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb3/igt@[email protected]
* igt@kms_content_protection@dp-mst-lic-type-0:
- shard-iclb: NOTRUN -> [SKIP][54] ([i915#3116])
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb8/igt@[email protected]
* igt@kms_content_protection@lic:
- shard-apl: NOTRUN -> [TIMEOUT][55] ([i915#1319]) +1 similar issue
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-apl1/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-512x512-sliding:
- shard-iclb: NOTRUN -> [SKIP][56] ([fdo#109278] / [fdo#109279]) +1 similar issue
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb6/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-32x32-sliding:
- shard-tglb: NOTRUN -> [SKIP][57] ([i915#3319])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb6/igt@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-alpha-opaque:
- shard-glk: [PASS][58] -> [FAIL][59] ([i915#3444])
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-glk7/igt@[email protected]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-glk2/igt@[email protected]
- shard-apl: [PASS][60] -> [FAIL][61] ([i915#3444])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-apl7/igt@[email protected]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-apl1/igt@[email protected]
- shard-kbl: [PASS][62] -> [FAIL][63] ([i915#3444])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-kbl6/igt@[email protected]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-kbl6/igt@[email protected]
* igt@kms_cursor_crc@pipe-d-cursor-32x32-rapid-movement:
- shard-iclb: NOTRUN -> [SKIP][64] ([fdo#109278]) +19 similar issues
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb3/igt@[email protected]
* igt@kms_cursor_crc@pipe-d-cursor-512x170-rapid-movement:
- shard-tglb: NOTRUN -> [SKIP][65] ([i915#3359]) +1 similar issue
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb1/igt@[email protected]
* igt@kms_cursor_crc@pipe-d-cursor-512x512-onscreen:
- shard-tglb: NOTRUN -> [SKIP][66] ([fdo#109279] / [i915#3359]) +1 similar issue
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb5/igt@[email protected]
* igt@kms_dsc@xrgb8888-dsc-compression:
- shard-tglb: NOTRUN -> [SKIP][67] ([i915#3828])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb2/igt@[email protected]
* igt@kms_flip@2x-blocking-absolute-wf_vblank-interruptible:
- shard-tglb: NOTRUN -> [SKIP][68] ([fdo#111825]) +13 similar issues
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb6/igt@kms_flip@2x-blocking-absolute-wf_vblank-interruptible.html
* igt@kms_flip@2x-flip-vs-absolute-wf_vblank-interruptible:
- shard-iclb: NOTRUN -> [SKIP][69] ([fdo#109274]) +2 similar issues
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb4/igt@kms_flip@2x-flip-vs-absolute-wf_vblank-interruptible.html
* igt@kms_flip@flip-vs-expired-vblank@a-edp1:
- shard-tglb: [PASS][70] -> [FAIL][71] ([i915#79])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-tglb1/igt@kms_flip@[email protected]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb8/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-expired-vblank@b-hdmi-a2:
- shard-glk: [PASS][72] -> [FAIL][73] ([i915#79])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-glk7/igt@kms_flip@[email protected]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-glk8/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-suspend-interruptible@a-dp1:
- shard-kbl: [PASS][74] -> [DMESG-WARN][75] ([i915#180]) +10 similar issues
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-kbl7/igt@kms_flip@[email protected]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-kbl4/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-mmap-cpu:
- shard-kbl: NOTRUN -> [SKIP][76] ([fdo#109271]) +138 similar issues
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-kbl7/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-mmap-cpu.html
* igt@kms_frontbuffer_tracking@psr-2p-primscrn-pri-indfb-draw-render:
- shard-iclb: NOTRUN -> [SKIP][77] ([fdo#109280]) +10 similar issues
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb7/igt@kms_frontbuffer_tracking@psr-2p-primscrn-pri-indfb-draw-render.html
* igt@kms_hdmi_inject@inject-audio:
- shard-tglb: [PASS][78] -> [SKIP][79] ([i915#433])
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-tglb8/igt@[email protected]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb3/igt@[email protected]
* igt@kms_hdr@static-toggle-dpms:
- shard-iclb: NOTRUN -> [SKIP][80] ([i915#1187])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb2/igt@[email protected]
* igt@kms_invalid_mode@clock-too-high:
- shard-tglb: NOTRUN -> [SKIP][81] ([i915#4278])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb3/igt@[email protected]
- shard-iclb: NOTRUN -> [SKIP][82] ([i915#4278])
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb8/igt@[email protected]
* igt@kms_multipipe_modeset@basic-max-pipe-crc-check:
- shard-tglb: NOTRUN -> [SKIP][83] ([i915#1839])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb3/igt@[email protected]
- shard-iclb: NOTRUN -> [SKIP][84] ([i915#1839])
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb1/igt@[email protected]
* igt@kms_pipe_b_c_ivb@pipe-b-double-modeset-then-modeset-pipe-c:
- shard-tglb: NOTRUN -> [SKIP][85] ([fdo#109289])
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb2/igt@[email protected]
* igt@kms_pipe_crc_basic@disable-crc-after-crtc-pipe-d:
- shard-kbl: NOTRUN -> [SKIP][86] ([fdo#109271] / [i915#533])
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-kbl2/igt@[email protected]
* igt@kms_pipe_crc_basic@suspend-read-crc-pipe-d:
- shard-apl: NOTRUN -> [SKIP][87] ([fdo#109271] / [i915#533]) +1 similar issue
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-apl7/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-alpha-opaque-fb:
- shard-apl: NOTRUN -> [FAIL][88] ([fdo#108145] / [i915#265])
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-apl8/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-alpha-transparent-fb:
- shard-glk: NOTRUN -> [FAIL][89] ([i915#265])
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-glk4/igt@[email protected]
- shard-kbl: NOTRUN -> [FAIL][90] ([i915#265])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-kbl2/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-b-alpha-basic:
- shard-kbl: NOTRUN -> [FAIL][91] ([fdo#108145] / [i915#265])
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-kbl7/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-b-alpha-opaque-fb:
- shard-glk: NOTRUN -> [FAIL][92] ([fdo#108145] / [i915#265])
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-glk5/igt@[email protected]
* igt@kms_plane_lowres@pipe-b-tiling-y:
- shard-tglb: NOTRUN -> [SKIP][93] ([i915#3536]) +1 similar issue
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb2/igt@[email protected]
* igt@kms_plane_lowres@pipe-c-tiling-yf:
- shard-iclb: NOTRUN -> [SKIP][94] ([i915#3536]) +1 similar issue
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb5/igt@[email protected]
- shard-tglb: NOTRUN -> [SKIP][95] ([fdo#112054]) +1 similar issue
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb2/igt@[email protected]
* igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping:
- shard-kbl: NOTRUN -> [SKIP][96] ([fdo#109271] / [i915#2733])
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-kbl4/igt@kms_plane_scaling@scaler-with-clipping-clamping@pipe-c-scaler-with-clipping-clamping.html
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area-4:
- shard-glk: NOTRUN -> [SKIP][97] ([fdo#109271] / [i915#658])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-glk9/igt@[email protected]
* igt@kms_psr2_sf@overlay-primary-update-sf-dmg-area-4:
- shard-apl: NOTRUN -> [SKIP][98] ([fdo#109271] / [i915#658]) +5 similar issues
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-apl3/igt@[email protected]
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-2:
- shard-iclb: NOTRUN -> [SKIP][99] ([i915#658]) +1 similar issue
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb7/igt@[email protected]
- shard-kbl: NOTRUN -> [SKIP][100] ([fdo#109271] / [i915#658]) +3 similar issues
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-kbl7/igt@[email protected]
* igt@kms_psr@psr2_cursor_blt:
- shard-iclb: [PASS][101] -> [SKIP][102] ([fdo#109441]) +3 similar issues
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-iclb2/igt@kms_psr@psr2_cursor_blt.html
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb3/igt@kms_psr@psr2_cursor_blt.html
* igt@kms_sysfs_edid_timing:
- shard-kbl: NOTRUN -> [FAIL][103] ([IGT#2])
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-kbl4/igt@kms_sysfs_edid_timing.html
* igt@kms_tv_load_detect@load-detect:
- shard-iclb: NOTRUN -> [SKIP][104] ([fdo#109309])
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb8/igt@[email protected]
* igt@kms_vblank@pipe-d-ts-continuation-idle:
- shard-apl: NOTRUN -> [SKIP][105] ([fdo#109271]) +264 similar issues
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-apl7/igt@[email protected]
* igt@kms_writeback@writeback-check-output:
- shard-apl: NOTRUN -> [SKIP][106] ([fdo#109271] / [i915#2437])
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-apl1/igt@[email protected]
* igt@kms_writeback@writeback-fb-id:
- shard-glk: NOTRUN -> [SKIP][107] ([fdo#109271] / [i915#2437])
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-glk8/igt@[email protected]
* igt@nouveau_crc@pipe-a-ctx-flip-skip-current-frame:
- shard-iclb: NOTRUN -> [SKIP][108] ([i915#2530])
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb5/igt@[email protected]
* igt@perf_pmu@rc6-suspend:
- shard-apl: [PASS][109] -> [DMESG-WARN][110] ([i915#180])
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-apl1/igt@[email protected]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-apl6/igt@[email protected]
* igt@prime_nv_api@i915_nv_double_import:
- shard-tglb: NOTRUN -> [SKIP][111] ([fdo#109291]) +1 similar issue
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb1/igt@prime_nv_api@i915_nv_double_import.html
* igt@prime_nv_api@nv_i915_reimport_twice_check_flink_name:
- shard-iclb: NOTRUN -> [SKIP][112] ([fdo#109291]) +2 similar issues
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb2/igt@prime_nv_api@nv_i915_reimport_twice_check_flink_name.html
* igt@prime_vgem@fence-write-hang:
- shard-iclb: NOTRUN -> [SKIP][113] ([fdo#109295])
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb3/igt@[email protected]
* igt@sysfs_clients@fair-3:
- shard-kbl: NOTRUN -> [SKIP][114] ([fdo#109271] / [i915#2994]) +1 similar issue
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-kbl3/igt@[email protected]
* igt@sysfs_clients@fair-7:
- shard-apl: NOTRUN -> [SKIP][115] ([fdo#109271] / [i915#2994]) +4 similar issues
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-apl6/igt@[email protected]
* igt@sysfs_clients@sema-25:
- shard-iclb: NOTRUN -> [SKIP][116] ([i915#2994])
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-iclb3/igt@[email protected]
- shard-glk: NOTRUN -> [SKIP][117] ([fdo#109271] / [i915#2994])
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-glk3/igt@[email protected]
#### Possible fixes ####
* igt@gem_exec_fair@basic-deadline:
- shard-kbl: [FAIL][118] ([i915#2846]) -> [PASS][119]
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-kbl4/igt@[email protected]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-kbl6/igt@[email protected]
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-glk: [FAIL][120] ([i915#2842]) -> [PASS][121]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-glk8/igt@gem_exec_fair@[email protected]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-glk6/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none@vcs1:
- shard-kbl: [FAIL][122] ([i915#2842]) -> [PASS][123]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-kbl6/igt@gem_exec_fair@[email protected]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-kbl2/igt@gem_exec_fair@[email protected]
* igt@gem_exec_whisper@basic-queues-all:
- shard-glk: [DMESG-WARN][124] ([i915#118]) -> [PASS][125]
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-glk4/igt@[email protected]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-glk4/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-64x21-offscreen:
- shard-glk: [FAIL][126] ([i915#3444]) -> [PASS][127]
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-glk1/igt@[email protected]
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-glk4/igt@[email protected]
* igt@kms_flip@flip-vs-suspend@c-dp1:
- shard-kbl: [DMESG-WARN][128] ([i915#180]) -> [PASS][129] +3 similar issues
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-kbl4/igt@kms_flip@[email protected]
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-kbl2/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-onoff:
- shard-tglb: [INCOMPLETE][130] ([i915#750]) -> [PASS][131]
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/IGT_6251/shard-tglb6/igt@[email protected]
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/shard-tglb5/igt@kms_fr
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_6327/index.html