drm/i915: Apply waitboosting before fence wait
Subsystems (2)
v2 cover drm/i915: Apply waitboosting before fence wait
Waitboost is a heuristic that detects latency sensitive workloads waiting for the results from previous execution. The wait can be seen as GPU under-utilisation by RPS, Render Power State management, which might lower the GPU frequency to save power. Limiting the frequency means more waiting for results, which is undesirable for submissions with tight time constraints. To circumvent this, with waitboost we iteratively check the list of fences during gem_wait to see if any of them is stalled waiting for GPU. If such is found, and the request hasn't yet started its execution, we temporarily bump up the GPU frequency, so we get the required results as soon as possible.
Commit 047a1b877ed4 ("dma-buf & drm/amdgpu: remove dma_resv workaround") changes the fences order and how they are iterated. Under this new scheme, we would wait on each fence that starts executing, rendering them not suitable for waitboost.
To avoid situation like this, inspect the entire list of fences dma-resv earlier, before gem_wait, instead of sequentially waiting for each of them, applying the boost when needed.
v2:
- Fixed a style issue in i915_gem_object_boost
Chris Wilson (3):
drm/i915/gem: Look for waitboosting across the whole object prior to
individual waits
drm/i915: Bump GT idling delay to 2 jiffies
drm/i915/gt: Only kick the signal worker if there's been an update
drivers/gpu/drm/i915/gem/i915_gem_wait.c | 34 +++++++++++++++++++++ drivers/gpu/drm/i915/gt/intel_breadcrumbs.c | 3 +- drivers/gpu/drm/i915/i915_active.c | 2 +- 3 files changed, 37 insertions(+), 2 deletions(-)
--
2.25.1
PATCH v2 1/3 drm/i915/gem: Look for waitboosting across the whole object prior to individual waits
From: Chris Wilson <[email protected]>
We employ a "waitboost" heuristic to detect when userspace is stalled waiting for results from earlier execution. Under latency sensitive work mixed between the gpu/cpu, the GPU is typically under-utilised and so RPS sees that low utilisation as a reason to downclock the frequency, causing longer stalls and lower throughput. The user left waiting for the results is not impressed.
On applying commit 047a1b877ed4 ("dma-buf & drm/amdgpu: remove dma_resv workaround") it was observed that deinterlacing h264 on Haswell performance dropped by 2-5x. The reason being that the natural workload was not intense enough to trigger RPS (using HW evaluation intervals) to upclock, and so it was depending on waitboosting for the throughput.
Commit 047a1b877ed4 ("dma-buf & drm/amdgpu: remove dma_resv workaround") changes the composition of dma-resv from keeping a single write fence + multiple read fences, to a single array of multiple write and read fences (a maximum of one pair of write/read fences per context). The iteration order was also changed implicitly from all-read fences then the single write fence, to a mix of write fences followed by read fences. It is that ordering change that belied the fragility of waitboosting.
Currently, a waitboost is inspected at the point of waiting on an outstanding fence. If the GPU is backlogged such that we haven't yet stated the request we need to wait on, we force the GPU to upclock until the completion of that request. By changing the order in which we waited upon requests, we ended up waiting on those requests in sequence and as such we saw that each request was already started and so not a suitable candidate for waitboosting.
Instead of asking whether to boost each fence in turn, we can look at whether boosting is required for the dma-resv ensemble prior to waiting on any fence, making the heuristic more robust to the order in which fences are stored in the dma-resv.
--- drivers/gpu/drm/i915/gem/i915_gem_wait.c | 34 ++++++++++++++++++++++++ 1 file changed, 34 insertions(+)
drivers/gpu/drm/i915/gem/i915_gem_wait.c +34 -0
@@ -9,6 +9,7 @@#include <linux/jiffies.h> #include "gt/intel_engine.h" +#include "gt/intel_rps.h" #include "i915_gem_ioctls.h" #include "i915_gem_object.h"
@@ -31,6 +32,37 @@ i915_gem_object_wait_fence(struct dma_fence *fence, timeout); } +static void +i915_gem_object_boost (struct dma_resv *resv,unsigned int flags) +{ +struct dma_resv_iter cursor; +struct dma_fence *fence; + +/* +* Prescan all fences for potential boosting before we begin waiting. +* +* When we wait, we wait on outstanding fences serially. If the +* dma-resv contains a sequence such as 1:1, 1:2 instead of a reduced +* form 1:2, then as we look at each wait in turn we see that each +* request is currently executing and not worthy of boosting. But if +* we only happen to look at the final fence in the sequence (because +* of request coalescing or splitting between read/write arrays by +* the iterator), then we would boost. As such our decision to boost +* or not is delicately balanced on the order we wait on fences. +* +* So instead of looking for boosts sequentially, look for all boosts +* upfront and then wait on the outstanding fences. +*/ + +dma_resv_iter_begin (&cursor, resv, +dma_resv_usage_rw (flags &I915_WAIT_ALL )); +dma_resv_for_each_fence_unlocked (&cursor, fence) +if (dma_fence_is_i915 (fence) && + !i915_request_started (to_request (fence))) +intel_rps_boost (to_request (fence)); +dma_resv_iter_end (&cursor); +} + static long i915_gem_object_wait_reservation(struct dma_resv *resv, unsigned int flags,
@@ -40,6 +72,8 @@ i915_gem_object_wait_reservation(struct dma_resv *resv,struct dma_fence *fence;long ret = timeout ?:1 ; +i915_gem_object_boost (resv, flags); +dma_resv_iter_begin (&cursor, resv,dma_resv_usage_rw (flags &I915_WAIT_ALL ));dma_resv_for_each_fence_unlocked (&cursor, fence) {
Signature · 1 line
2.25.1
Re: [Intel-gfx] [PATCH v2 1/3] drm/i915/gem: Look for waitboosting across the whole object prior to individual waits
Quoted 37 lines · Karolina Drobnik
From: Chris Wilson <[email protected]>
We employ a "waitboost" heuristic to detect when userspace is stalled waiting for results from earlier execution. Under latency sensitive work mixed between the gpu/cpu, the GPU is typically under-utilised and so RPS sees that low utilisation as a reason to downclock the frequency, causing longer stalls and lower throughput. The user left waiting for the results is not impressed.
On applying commit
047a1b877ed4("dma-buf & drm/amdgpu: removedma_resvworkaround") it was observed that deinterlacing h264 on Haswell performance dropped by 2-5x. The reason being that the natural workload was not intense enough to trigger RPS (using HW evaluation intervals) to upclock, and so it was depending on waitboosting for the throughput.Commit
047a1b877ed4("dma-buf & drm/amdgpu: removedma_resvworkaround") changes the composition of dma-resv from keeping a single write fence + multiple read fences, to a single array of multiple write and read fences (a maximum of one pair of write/read fences per context). The iteration order was also changed implicitly from all-read fences then the single write fence, to a mix of write fences followed by read fences. It is that ordering change that belied the fragility of waitboosting.Currently, a waitboost is inspected at the point of waiting on an outstanding fence. If the GPU is backlogged such that we haven't yet stated the request we need to wait on, we force the GPU to upclock until the completion of that request. By changing the order in which we waited upon requests, we ended up waiting on those requests in sequence and as such we saw that each request was already started and so not a suitable candidate for waitboosting.
Instead of asking whether to boost each fence in turn, we can look at whether boosting is required for the dma-resv ensemble prior to waiting on any fence, making the heuristic more robust to the order in which fences are stored in the dma-resv.
Quoted 8 lines
Reported-by Thomas Voegtle <[email protected]>Fixes 047a1b877ed4 ("dma-buf & drm/amdgpu: remove dma_resv workaround")Signed-off-by Chris Wilson <[email protected]>Cc Tvrtko Ursulin <[email protected]>Signed-off-by Karolina Drobnik <[email protected]>Tested-by Thomas Voegtle <[email protected]>Reviewed-by Andi Shyti <[email protected]>
Quoted 66 lines
--- drivers/gpu/drm/i915/gem/i915_gem_wait.c | 34 ++++++++++++++++++++++++ 1 file changed, 34 insertions(+)drivers/gpu/drm/i915/gem/i915_gem_wait.c +34
-0@@ -9,6 +9,7 @@#include <linux/jiffies.h> #include "gt/intel_engine.h" +#include "gt/intel_rps.h" #include "i915_gem_ioctls.h" #include "i915_gem_object.h" @@ -31,6 +32,37 @@ i915_gem_object_wait_fence(struct dma_fence *fence, timeout); } +static void +i915_gem_object_boost (struct dma_resv *resv,unsigned int flags) +{ +struct dma_resv_iter cursor; +struct dma_fence *fence; + +/* +* Prescan all fences for potential boosting before we begin waiting. +* +* When we wait, we wait on outstanding fences serially. If the +* dma-resv contains a sequence such as 1:1, 1:2 instead of a reduced +* form 1:2, then as we look at each wait in turn we see that each +* request is currently executing and not worthy of boosting. But if +* we only happen to look at the final fence in the sequence (because +* of request coalescing or splitting between read/write arrays by +* the iterator), then we would boost. As such our decision to boost +* or not is delicately balanced on the order we wait on fences. +* +* So instead of looking for boosts sequentially, look for all boosts +* upfront and then wait on the outstanding fences. +*/ + +dma_resv_iter_begin (&cursor, resv, +dma_resv_usage_rw (flags &I915_WAIT_ALL )); +dma_resv_for_each_fence_unlocked (&cursor, fence) +if (dma_fence_is_i915 (fence) && + !i915_request_started (to_request (fence))) +intel_rps_boost (to_request (fence)); +dma_resv_iter_end (&cursor); +} + static long i915_gem_object_wait_reservation(struct dma_resv *resv, unsigned int flags,@@ -40,6 +72,8 @@ i915_gem_object_wait_reservation(struct dma_resv *resv,struct dma_fence *fence;long ret = timeout ?:1 ; +i915_gem_object_boost (resv, flags); +dma_resv_iter_begin (&cursor, resv,dma_resv_usage_rw (flags &I915_WAIT_ALL ));dma_resv_for_each_fence_unlocked (&cursor, fence) {Signature · 1 line
2.25.1
PATCH v2 2/3 drm/i915: Bump GT idling delay to 2 jiffies
In reply to Karolina DrobnikFrom: Chris Wilson <[email protected]>
In monitoring a transcode pipeline that is latency sensitive (it waits between submitting frames, and each frame requires work on rcs/vcs/vecs engines), it is found that it took longer than a single jiffy for it to sustain its workload. Allowing an extra jiffy headroom for the userspace prevents us from prematurely parking and having to exit powersaving immediately.
--- drivers/gpu/drm/i915/i915_active.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/i915/i915_active.c +1 -1
@@ -974,7 +974,7 @@ void i915_active_acquire_barrier(struct i915_active *ref)GEM_BUG_ON (!intel_engine_pm_is_awake (engine));llist_add (barrier_to_ll (node), &engine->barrier_tasks); -intel_engine_pm_put_delay (engine,1 ); +intel_engine_pm_put_delay (engine,2 ); } }
Signature · 1 line
2.25.1
PATCH v2 3/3 drm/i915/gt: Only kick the signal worker if there's been an update
In reply to Karolina DrobnikFrom: Chris Wilson <[email protected]>
One impact of commit 047a1b877ed4 ("dma-buf & drm/amdgpu: remove dma_resv workaround") is that it stores many, many more fences. Whereas adding an exclusive fence used to remove the shared fence list, that list is now preserved and the write fences included into the list. Not just a single write fence, but now a write/read fence per context. That causes us to have to track more fences than before (albeit half of those are redundant), and we trigger more interrupts for multi-engine workloads.
As part of reducing the impact from handling more signaling, we observe we only need to kick the signal worker after adding a fence iff we have good cause to believe that there is work to be done in processing the fence i.e. we either need to enable the interrupt or the request is already complete but we don't know if we saw the interrupt and so need to check signaling.
References: 047a1b877ed4 ("dma-buf & drm/amdgpu: remove dma_resv workaround")
--- drivers/gpu/drm/i915/gt/intel_breadcrumbs.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/gt/intel_breadcrumbs.c +2 -1
@@ -399,7 +399,8 @@ static void insert_breadcrumb(struct i915_request *rq)* the request as it may have completed and raised the interrupt as * we were attaching it into the lists. */ -irq_work_queue (&b->irq_work); +if (!b->irq_armed ||__i915_request_is_complete (rq)) +irq_work_queue (&b->irq_work); }bool i915_request_enable_breadcrumb (struct i915_request *rq)
Signature · 1 line
2.25.1
Rodrigo Vivi
maintainerRe: [Intel-gfx] [PATCH v2 3/3] drm/i915/gt: Only kick the signal worker if there's been an update
Quoted 11 lines · Karolina Drobnik
From: Chris Wilson <[email protected]>
One impact of commit
047a1b877ed4("dma-buf & drm/amdgpu: removedma_resvworkaround") is that it stores many, many more fences. Whereas adding an exclusive fence used to remove the shared fence list, that list is now preserved and the write fences included into the list. Not just a single write fence, but now a write/read fence per context. That causes us to have to track more fences than before (albeit half of those are redundant), and we trigger more interrupts for multi-engine workloads.
Quoted 2 lines
As part of reducing the impact from handling more signaling, we observe we only need to kick the signal worker after adding a fence iff we have
s/iff/if
Quoted 17 lines
good cause to believe that there is work to be done in processing the fence i.e. we either need to enable the interrupt or the request is already complete but we don't know if we saw the interrupt and so need to check signaling.
References:
047a1b877ed4("dma-buf & drm/amdgpu: removedma_resvworkaround")Signed-off-by Chris Wilson <[email protected]>Signed-off-by Karolina Drobnik <[email protected]>--- drivers/gpu/drm/i915/gt/intel_breadcrumbs.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)drivers/gpu/drm/i915/gt/intel_breadcrumbs.c +0
-0
drivers/gpu/drm/i915/gt/intel_breadcrumbs.c static void insert_breadcrumb(struct i915_request *rq) · line 402
Quoted 5 lines
drivers/gpu/drm/i915/gt/intel_breadcrumbs.c +1
-1@@ -399,7 +399,8 @@ static void insert_breadcrumb(struct i915_request *rq)* the request as it may have completed and raised the interrupt as * we were attaching it into the lists. */ -irq_work_queue (&b->irq_work); +if (!b->irq_armed ||__i915_request_is_complete (rq))
would we need the READ_ONCE(irq_armed) ?
would we need to use the irq_lock?
Quoted 7 lines
drivers/gpu/drm/i915/gt/intel_breadcrumbs.c +1
-0+irq_work_queue (&b->irq_work); }bool i915_request_enable_breadcrumb (struct i915_request *rq)Signature · 1 line
2.25.1
Rodrigo Vivi
maintainerRe: [Intel-gfx] [PATCH v2 3/3] drm/i915/gt: Only kick the signal worker if there's been an update
Quoted 29 lines · Rodrigo Vivi
Quoted 11 lines · Karolina Drobnik
From: Chris Wilson <[email protected]>
One impact of commit
047a1b877ed4("dma-buf & drm/amdgpu: removedma_resvworkaround") is that it stores many, many more fences. Whereas adding an exclusive fence used to remove the shared fence list, that list is now preserved and the write fences included into the list. Not just a single write fence, but now a write/read fence per context. That causes us to have to track more fences than before (albeit half of those are redundant), and we trigger more interrupts for multi-engine workloads.Quoted 2 lines
As part of reducing the impact from handling more signaling, we observe we only need to kick the signal worker after adding a fence iff we have
s/iff/if
Quoted 12 lines
good cause to believe that there is work to be done in processing the fence i.e. we either need to enable the interrupt or the request is already complete but we don't know if we saw the interrupt and so need to check signaling.
References:
047a1b877ed4("dma-buf & drm/amdgpu: removedma_resvworkaround")Signed-off-by Chris Wilson <[email protected]>Signed-off-by Karolina Drobnik <[email protected]>--- drivers/gpu/drm/i915/gt/intel_breadcrumbs.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
Quoted 13 lines
drivers/gpu/drm/i915/gt/intel_breadcrumbs.c static void insert_breadcrumb(struct i915_request *rq) · line 402
Quoted 10 lines
drivers/gpu/drm/i915/gt/intel_breadcrumbs.c +1
-1@@ -399,7 +399,8 @@ static void insert_breadcrumb(struct i915_request *rq)* the request as it may have completed and raised the interrupt as * we were attaching it into the lists. */ -irq_work_queue (&b->irq_work); +if (!b->irq_armed ||__i915_request_is_complete (rq))would we need the
READ_ONCE(irq_armed)?
would we need to use theirq_lock?
gentle ping on these questions here so maybe we can get this ready for 5.20 still...
Thanks,
Rodrigo.
Quoted 8 lines
Quoted 8 lines
drivers/gpu/drm/i915/gt/intel_breadcrumbs.c +1
-0+irq_work_queue (&b->irq_work); }bool i915_request_enable_breadcrumb (struct i915_request *rq)Signature · 1 line
2.25.1
Re: [Intel-gfx] [PATCH v2 3/3] drm/i915/gt: Only kick the signal worker if there's been an update
In reply to Rodrigo ViviHi Rodrigo,
Many thanks for taking another look at the patches.
Quoted 12 lines · Rodrigo Vivi
Quoted 11 lines · Karolina Drobnik
From: Chris Wilson <[email protected]>
One impact of commit
047a1b877ed4("dma-buf & drm/amdgpu: removedma_resvworkaround") is that it stores many, many more fences. Whereas adding an exclusive fence used to remove the shared fence list, that list is now preserved and the write fences included into the list. Not just a single write fence, but now a write/read fence per context. That causes us to have to track more fences than before (albeit half of those are redundant), and we trigger more interrupts for multi-engine workloads.
Quoted 4 lines
Quoted 2 lines
As part of reducing the impact from handling more signaling, we observe we only need to kick the signal worker after adding a fence iff we have
s/iff/if
This is fine, it means "if, and only if"
Quoted 12 lines
Quoted 12 lines
good cause to believe that there is work to be done in processing the fence i.e. we either need to enable the interrupt or the request is already complete but we don't know if we saw the interrupt and so need to check signaling.
References:
047a1b877ed4("dma-buf & drm/amdgpu: removedma_resvworkaround")Signed-off-by Chris Wilson <[email protected]>Signed-off-by Karolina Drobnik <[email protected]>--- drivers/gpu/drm/i915/gt/intel_breadcrumbs.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
Quoted 13 lines
drivers/gpu/drm/i915/gt/intel_breadcrumbs.c static void insert_breadcrumb(struct i915_request *rq) · line 402
Quoted 10 lines
drivers/gpu/drm/i915/gt/intel_breadcrumbs.c +1
-1@@ -399,7 +399,8 @@ static void insert_breadcrumb(struct i915_request *rq)* the request as it may have completed and raised the interrupt as * we were attaching it into the lists. */ -irq_work_queue (&b->irq_work); +if (!b->irq_armed ||__i915_request_is_complete (rq))would we need the
READ_ONCE(irq_armed)?
would we need to use theirq_lock?
I'll rephrase Chris' answer here:
No, it doesn't need either, the workqueuing is unrelated to the irq_lock. The worker enables the interrupt if there are any breadcrumbs at the end of its task. When queuing the work, we have to consider the race conditions:
- If the worker is running and b->irq_armed at this point, we know the irq will remain armed
- If the worker is running and !b->irq_armed at this point, we will kick the worker again -- it doesn't make any difference then if the worker is in the process of trying to arm the irq
- If the worker is not running, b->irq_armed is constant, no race
Ergo, the only race condition is where the worker is trying to arm the irq, and we end up running the worker a second time.
The only danger to consider is _not_ running the worker when we need to. Once we put the breadcrumb on the signal, it has to be removed at some point. Normally this is only performed by the worker, so we have to confident that the worker will be run. We know that if the irq is armed (after we have attached this breadcrumb) there must be another run of the worker.
The other condition then, if the irq is armed, but the breadcrumb is already completed, we may not see an interrupt from the gpu as the breadcrumb may have completed as we attached it, keeping the worker alive, but not noticing the completed breadcrumb in that case, we have to simulate the interrupt ourselves and give the worker a kick.
The irq_lock is immaterial in both cases.
Quoted 7 lines
Quoted 7 lines
drivers/gpu/drm/i915/gt/intel_breadcrumbs.c +1
-0+irq_work_queue (&b->irq_work); }bool i915_request_enable_breadcrumb (struct i915_request *rq)Signature · 1 line
2.25.1
Rodrigo Vivi
maintainerRe: [Intel-gfx] [PATCH v2 3/3] drm/i915/gt: Only kick the signal worker if there's been an update
Quoted 73 lines · Karolina Drobnik
Hi Rodrigo,
Many thanks for taking another look at the patches.
Quoted 12 lines · Rodrigo Vivi
Quoted 11 lines · Karolina Drobnik
From: Chris Wilson <[email protected]>
One impact of commit
047a1b877ed4("dma-buf & drm/amdgpu: removedma_resvworkaround") is that it stores many, many more fences. Whereas adding an exclusive fence used to remove the shared fence list, that list is now preserved and the write fences included into the list. Not just a single write fence, but now a write/read fence per context. That causes us to have to track more fences than before (albeit half of those are redundant), and we trigger more interrupts for multi-engine workloads.Quoted 4 lines
Quoted 2 lines
As part of reducing the impact from handling more signaling, we observe we only need to kick the signal worker after adding a fence iff we have
s/iff/if
This is fine, it means "if, and only if"
Quoted 12 lines
Quoted 12 lines
good cause to believe that there is work to be done in processing the fence i.e. we either need to enable the interrupt or the request is already complete but we don't know if we saw the interrupt and so need to check signaling.
References:
047a1b877ed4("dma-buf & drm/amdgpu: removedma_resvworkaround")Signed-off-by Chris Wilson <[email protected]>Signed-off-by Karolina Drobnik <[email protected]>--- drivers/gpu/drm/i915/gt/intel_breadcrumbs.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)Quoted 13 lines
drivers/gpu/drm/i915/gt/intel_breadcrumbs.c static void insert_breadcrumb(struct i915_request *rq) · line 402
Quoted 10 lines
drivers/gpu/drm/i915/gt/intel_breadcrumbs.c +1
-1@@ -399,7 +399,8 @@ static void insert_breadcrumb(struct i915_request *rq)* the request as it may have completed and raised the interrupt as * we were attaching it into the lists. */ -irq_work_queue (&b->irq_work); +if (!b->irq_armed ||__i915_request_is_complete (rq))would we need the
READ_ONCE(irq_armed)?
would we need to use theirq_lock?I'll rephrase Chris' answer here:
No, it doesn't need either, the workqueuing is unrelated to the
irq_lock. The worker enables the interrupt if there are any breadcrumbs at the end of its task. When queuing the work, we have to consider the race conditions:- If the worker is running and
b->irq_armedat this point, we know the irq will remain armed
- If the worker is running and !b->irq_armed at this point, we will kick the worker again -- it doesn't make any difference then if the worker is in the process of trying to arm the irq
- If the worker is not running,b->irq_armedis constant, no raceErgo, the only race condition is where the worker is trying to arm the irq, and we end up running the worker a second time.
The only danger to consider is _not_ running the worker when we need to. Once we put the breadcrumb on the signal, it has to be removed at some point. Normally this is only performed by the worker, so we have to confident that the worker will be run. We know that if the irq is armed (after we have attached this breadcrumb) there must be another run of the worker.
Quoted 8 lines
The other condition then, if the irq is armed, but the breadcrumb is already completed, we may not see an interrupt from the gpu as the breadcrumb may have completed as we attached it, keeping the worker alive, but not noticing the completed breadcrumb in that case, we have to simulate the interrupt ourselves and give the worker a kick.
The
irq_lockis immaterial in both cases.
I just pushed the patch. More relying on multiple reviews and on the tests that unblock our users than on this explanation here.
If the locks exist to protect some access we need to use it. It should be simple like that. Magic cases where locks don't apply just helps this castle of cards to fall apart later.
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
drivers/gpu/drm/i915/gt/intel_breadcrumbs.c +1
-0+irq_work_queue (&b->irq_work); }bool i915_request_enable_breadcrumb (struct i915_request *rq)Signature · 1 line
2.25.1
Re: [Intel-gfx] [PATCH v2 3/3] drm/i915/gt: Only kick the signal worker if there's been an update
In reply to Karolina DrobnikHi Karolina,
Quoted 16 lines
One impact of commit
047a1b877ed4("dma-buf & drm/amdgpu: removedma_resvworkaround") is that it stores many, many more fences. Whereas adding an exclusive fence used to remove the shared fence list, that list is now preserved and the write fences included into the list. Not just a single write fence, but now a write/read fence per context. That causes us to have to track more fences than before (albeit half of those are redundant), and we trigger more interrupts for multi-engine workloads.As part of reducing the impact from handling more signaling, we observe we only need to kick the signal worker after adding a fence iff we have good cause to believe that there is work to be done in processing the fence i.e. we either need to enable the interrupt or the request is already complete but we don't know if we saw the interrupt and so need to check signaling.
Quoted 3 lines
References:
047a1b877ed4("dma-buf & drm/amdgpu: removedma_resvworkaround")Signed-off-by Chris Wilson <[email protected]>Signed-off-by Karolina Drobnik <[email protected]>
sorry, I missed this patch.
Thanks,
Andi
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Apply waitboosting before fence wait (rev2)
In reply to Karolina Drobnik== Series Details ==
== Series Details ==
Series: drm/i915: Apply waitboosting before fence wait (rev2)
URL : https://patchwork.freedesktop.org/series/105925/
State : warning
== Summary ==
Error: dim checkpatch failede35c61e9e46c drm/i915/gem: Look for waitboosting across the whole object prior to individual waits 85a4558b5d11 drm/i915: Bump GT idling delay to 2 jiffies0ec610488c77 drm/i915/gt: Only kick the signal worker if there's been an update
-:23: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line) #23:
References: 047a1b877ed4 ("dma-buf & drm/amdgpu: remove dma_resv workaround")
-:23: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 047a1b877ed4 ("dma-buf & drm/amdgpu: remove dma_resv workaround")' #23:
References: 047a1b877ed4 ("dma-buf & drm/amdgpu: remove dma_resv workaround")
total: 1 errors, 1 warnings, 0 checks, 9 lines checked
Re: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Apply waitboosting before fence wait (rev2)
Quoted 8 lines · Patchwork
== Series Details ==
Series: drm/i915: Apply waitboosting before fence wait (rev2)
URL : https://patchwork.freedesktop.org/series/105925/
State : warning== Summary ==
Quoted 7 lines
Error: dim checkpatch failed
e35c61e9e46cdrm/i915/gem: Look for waitboosting across the whole object prior to individual waits85a4558b5d11drm/i915: Bump GT idling delay to 2 jiffies0ec610488c77drm/i915/gt: Only kick the signal worker if there's been an update
-:23: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line) #23:
References:047a1b877ed4("dma-buf & drm/amdgpu: removedma_resvworkaround")
Tags shouldn't be wrapped
Quoted 3 lines
-:23: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit
047a1b877ed4("dma-buf & drm/amdgpu: removedma_resvworkaround")' #23:
References:047a1b877ed4("dma-buf & drm/amdgpu: removedma_resvworkaround")
"References:" line doesn't need "commit" keyword, it's a false positive
Quoted 3 lines
total: 1 errors, 1 warnings, 0 checks, 9 lines checked
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Apply waitboosting before fence wait (rev2)
In reply to Karolina Drobnik== Series Details ==
== Series Details ==
Series: drm/i915: Apply waitboosting before fence wait (rev2)
URL : https://patchwork.freedesktop.org/series/105925/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11862 -> Patchwork_105925v2
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/index.html
Participating hosts (45 -> 41)
------------------------------
Missing (4): fi-ctg-p8600 fi-cml-u2 fi-hsw-4200u bat-jsl-3
Known issues
------------
Here are the changes found in Patchwork_105925v2 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@module-reload:
- fi-cfl-8109u: [PASS][1] -> [DMESG-FAIL][2] ([i915#62])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/fi-cfl-8109u/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/fi-cfl-8109u/igt@[email protected]
* igt@i915_selftest@live@gem:
- fi-pnv-d510: NOTRUN -> [DMESG-FAIL][3] ([i915#4528])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/fi-pnv-d510/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@hangcheck:
- fi-hsw-4770: [PASS][4] -> [INCOMPLETE][5] ([i915#4785])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/fi-hsw-4770/igt@i915_selftest@[email protected]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/fi-hsw-4770/igt@i915_selftest@[email protected]
- fi-hsw-g3258: [PASS][6] -> [INCOMPLETE][7] ([i915#4785])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/fi-hsw-g3258/igt@i915_selftest@[email protected]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/fi-hsw-g3258/igt@i915_selftest@[email protected]
* igt@kms_busy@basic@modeset:
- bat-adlp-4: [PASS][8] -> [DMESG-WARN][9] ([i915#3576])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/bat-adlp-4/igt@kms_busy@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/bat-adlp-4/igt@kms_busy@[email protected]
* igt@kms_chamelium@common-hpd-after-suspend:
- fi-snb-2600: NOTRUN -> [SKIP][10] ([fdo#109271] / [fdo#111827])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/fi-snb-2600/igt@[email protected]
* igt@kms_frontbuffer_tracking@basic:
- fi-cfl-8109u: [PASS][11] -> [DMESG-WARN][12] ([i915#62]) +12 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/fi-cfl-8109u/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/fi-cfl-8109u/igt@[email protected]
* igt@runner@aborted:
- fi-hsw-4770: NOTRUN -> [FAIL][13] ([fdo#109271] / [i915#4312] / [i915#5594] / [i915#6246])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/fi-hsw-4770/igt@[email protected]
- fi-hsw-g3258: NOTRUN -> [FAIL][14] ([fdo#109271] / [i915#4312] / [i915#6246])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/fi-hsw-g3258/igt@[email protected]
#### Possible fixes ####
* igt@i915_module_load@reload:
- {bat-adln-1}: [DMESG-WARN][15] ([i915#6297]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/bat-adln-1/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/bat-adln-1/igt@[email protected]
* igt@i915_selftest@live@hangcheck:
- fi-snb-2600: [INCOMPLETE][17] ([i915#3921]) -> [PASS][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/fi-snb-2600/igt@i915_selftest@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/fi-snb-2600/igt@i915_selftest@[email protected]
- bat-dg1-6: [DMESG-FAIL][19] ([i915#4494] / [i915#4957]) -> [PASS][20]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/bat-dg1-6/igt@i915_selftest@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/bat-dg1-6/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@requests:
- fi-pnv-d510: [DMESG-FAIL][21] ([i915#4528]) -> [PASS][22]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/fi-pnv-d510/igt@i915_selftest@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/fi-pnv-d510/igt@i915_selftest@[email protected]
* igt@kms_flip@basic-flip-vs-modeset@b-edp1:
- {bat-adlp-6}: [DMESG-WARN][23] ([i915#3576]) -> [PASS][24] +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/bat-adlp-6/igt@kms_flip@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/bat-adlp-6/igt@kms_flip@[email protected]
* igt@vgem_basic@setversion:
- fi-kbl-soraka: [INCOMPLETE][25] -> [PASS][26]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/fi-kbl-soraka/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/fi-kbl-soraka/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#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#3576]: https://gitlab.freedesktop.org/drm/intel/issues/3576
[i915#3921]: https://gitlab.freedesktop.org/drm/intel/issues/3921
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4494]: https://gitlab.freedesktop.org/drm/intel/issues/4494
[i915#4528]: https://gitlab.freedesktop.org/drm/intel/issues/4528
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4785]: https://gitlab.freedesktop.org/drm/intel/issues/4785
[i915#4957]: https://gitlab.freedesktop.org/drm/intel/issues/4957
[i915#5594]: https://gitlab.freedesktop.org/drm/intel/issues/5594
[i915#6106]: https://gitlab.freedesktop.org/drm/intel/issues/6106
[i915#62]: https://gitlab.freedesktop.org/drm/intel/issues/62
[i915#6246]: https://gitlab.freedesktop.org/drm/intel/issues/6246
[i915#6297]: https://gitlab.freedesktop.org/drm/intel/issues/6297
Build changes
-------------
* Linux: CI_DRM_11862 -> Patchwork_105925v2
CI-20190529: 20190529
CI_DRM_11862: ffee806d103b9604db7eb9cd689c098aca1ffa96 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6563: 7d43b49bf10788d4870668f93a800888fc8ab339 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_105925v2: ffee806d103b9604db7eb9cd689c098aca1ffa96 @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
964006e4fdad drm/i915/gt: Only kick the signal worker if there's been an update 98f39b7621f1 drm/i915: Bump GT idling delay to 2 jiffies409cb1ea1087 drm/i915/gem: Look for waitboosting across the whole object prior to individual waits
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/index.html
Patchwork
CI[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Apply waitboosting before fence wait (rev2)
In reply to Karolina Drobnik== Series Details ==
== Series Details ==
Series: drm/i915: Apply waitboosting before fence wait (rev2)
URL : https://patchwork.freedesktop.org/series/105925/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11862_full -> Patchwork_105925v2_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_105925v2_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_105925v2_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Participating hosts (10 -> 13)
------------------------------
Additional (3): shard-rkl shard-dg1 shard-tglu
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_105925v2_full:
### IGT changes ###
#### Possible regressions ####
* igt@i915_pm_rc6_residency@rc6-idle@vcs0:
- shard-apl: [PASS][1] -> [WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-apl2/igt@i915_pm_rc6_residency@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-apl2/igt@i915_pm_rc6_residency@[email protected]
* igt@kms_vblank@pipe-d-wait-forked-busy-hang:
- shard-tglb: [PASS][3] -> [INCOMPLETE][4] +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-tglb8/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb8/igt@[email protected]
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* igt@kms_cursor_crc@cursor-offscreen:
- {shard-rkl}: NOTRUN -> [SKIP][5] +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-rkl-5/igt@[email protected]
* {igt@kms_invalid_mode@clock-too-high@edp-1-pipe-d}:
- shard-tglb: NOTRUN -> [SKIP][6] +3 similar issues
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@kms_invalid_mode@[email protected]
New tests
---------
New tests have been introduced between CI_DRM_11862_full and Patchwork_105925v2_full:
### New IGT tests (1) ###
* igt@kms_legacy_colorkey@basic:
- Statuses : 1 skip(s)
- Exec time: [0.0] s
Known issues
------------
Here are the changes found in Patchwork_105925v2_full that come from known issues:
### CI changes ###
#### Issues hit ####
* boot:
- shard-glk: ([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], [PASS][21], [PASS][22], [PASS][23], [PASS][24], [PASS][25], [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], [FAIL][47], [PASS][48], [PASS][49], [PASS][50], [PASS][51], [PASS][52], [PASS][53], [PASS][54], [PASS][55]) ([i915#4392])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk5/boot.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk5/boot.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk1/boot.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk1/boot.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk1/boot.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk2/boot.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk2/boot.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk2/boot.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk2/boot.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk3/boot.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk3/boot.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk5/boot.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk9/boot.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk9/boot.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk9/boot.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk9/boot.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk8/boot.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk8/boot.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk8/boot.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk7/boot.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk7/boot.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk7/boot.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk6/boot.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk6/boot.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk6/boot.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk9/boot.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk9/boot.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk8/boot.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk7/boot.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk7/boot.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk8/boot.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk8/boot.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk9/boot.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk1/boot.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk1/boot.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk1/boot.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk2/boot.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk2/boot.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk3/boot.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk3/boot.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk3/boot.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk3/boot.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk5/boot.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk5/boot.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk5/boot.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk6/boot.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk6/boot.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk7/boot.html
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk7/boot.html
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_persistence@engines-hostile-preempt:
- shard-snb: NOTRUN -> [SKIP][56] ([fdo#109271] / [i915#1099]) +1 similar issue
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-snb7/igt@[email protected]
* igt@gem_ctx_persistence@hostile:
- shard-tglb: NOTRUN -> [FAIL][57] ([i915#2410])
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@[email protected]
* igt@gem_exec_balancer@parallel-balancer:
- shard-snb: NOTRUN -> [SKIP][58] ([fdo#109271]) +26 similar issues
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-snb7/igt@[email protected]
* igt@gem_exec_balancer@parallel-contexts:
- shard-iclb: [PASS][59] -> [SKIP][60] ([i915#4525])
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb4/igt@[email protected]
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb5/igt@[email protected]
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-glk: NOTRUN -> [FAIL][61] ([i915#2842])
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk9/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none-vip@rcs0:
- shard-kbl: NOTRUN -> [FAIL][62] ([i915#2842])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl6/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@bcs0:
- shard-iclb: [PASS][63] -> [FAIL][64] ([i915#2842])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb1/igt@gem_exec_fair@[email protected]
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb4/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@rcs0:
- shard-kbl: [PASS][65] -> [FAIL][66] ([i915#2842]) +2 similar issues
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-kbl7/igt@gem_exec_fair@[email protected]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl4/igt@gem_exec_fair@[email protected]
- shard-glk: [PASS][67] -> [FAIL][68] ([i915#2842])
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk9/igt@gem_exec_fair@[email protected]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk9/igt@gem_exec_fair@[email protected]
* igt@gem_lmem_swapping@heavy-verify-random:
- shard-skl: NOTRUN -> [SKIP][69] ([fdo#109271] / [i915#4613]) +1 similar issue
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl5/igt@[email protected]
* igt@gem_lmem_swapping@smem-oom:
- shard-kbl: NOTRUN -> [SKIP][70] ([fdo#109271] / [i915#4613])
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl6/igt@[email protected]
* igt@gem_pxp@create-regular-context-1:
- shard-tglb: NOTRUN -> [SKIP][71] ([i915#4270])
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@[email protected]
* igt@gem_softpin@evict-snoop-interruptible:
- shard-tglb: NOTRUN -> [SKIP][72] ([fdo#109312])
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@[email protected]
* igt@gem_userptr_blits@vma-merge:
- shard-skl: NOTRUN -> [FAIL][73] ([i915#3318])
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl5/igt@[email protected]
* igt@gen9_exec_parse@allowed-single:
- shard-glk: [PASS][74] -> [DMESG-WARN][75] ([i915#5566] / [i915#716])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk6/igt@[email protected]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk5/igt@[email protected]
* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-glk: NOTRUN -> [SKIP][76] ([fdo#109271] / [i915#658])
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk9/igt@[email protected]
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [PASS][77] -> [FAIL][78] ([i915#454])
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb4/igt@[email protected]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb7/igt@[email protected]
* igt@i915_pm_rc6_residency@rc6-idle@rcs0:
- shard-tglb: NOTRUN -> [WARN][79] ([i915#2681]) +3 similar issues
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@i915_pm_rc6_residency@[email protected]
* igt@i915_selftest@live@gt_pm:
- shard-skl: NOTRUN -> [DMESG-FAIL][80] ([i915#1886])
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl4/igt@i915_selftest@live@gt_pm.html
* igt@i915_suspend@debugfs-reader:
- shard-kbl: NOTRUN -> [DMESG-WARN][81] ([i915#180])
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl6/igt@[email protected]
* igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-hflip:
- shard-skl: NOTRUN -> [SKIP][82] ([fdo#109271] / [i915#1888])
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl5/igt@[email protected]
* igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-async-flip:
- shard-skl: NOTRUN -> [FAIL][83] ([i915#3743])
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl7/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-async-flip.html
* igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0-hflip-async-flip:
- shard-kbl: NOTRUN -> [SKIP][84] ([fdo#109271]) +31 similar issues
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl6/igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0-hflip-async-flip.html
* igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_mc_ccs:
- shard-skl: NOTRUN -> [SKIP][85] ([fdo#109271] / [i915#3886]) +6 similar issues
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl5/igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_mc_ccs:
- shard-tglb: NOTRUN -> [SKIP][86] ([i915#3689] / [i915#3886])
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc:
- shard-kbl: NOTRUN -> [SKIP][87] ([fdo#109271] / [i915#3886])
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl6/igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-b-bad-pixel-format-y_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][88] ([i915#3689]) +1 similar issue
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@kms_ccs@pipe-b-bad-pixel-format-y_tiled_ccs.html
* igt@kms_ccs@pipe-c-bad-pixel-format-4_tiled_dg2_rc_ccs:
- shard-tglb: NOTRUN -> [SKIP][89] ([i915#6095]) +2 similar issues
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@kms_ccs@pipe-c-bad-pixel-format-4_tiled_dg2_rc_ccs.html
* igt@kms_ccs@pipe-c-crc-sprite-planes-basic-yf_tiled_ccs:
- shard-tglb: NOTRUN -> [SKIP][90] ([fdo#111615] / [i915#3689])
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@kms_ccs@pipe-c-crc-sprite-planes-basic-yf_tiled_ccs.html
* igt@kms_chamelium@dp-hpd-after-suspend:
- shard-snb: NOTRUN -> [SKIP][91] ([fdo#109271] / [fdo#111827]) +1 similar issue
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-snb7/igt@[email protected]
* igt@kms_chamelium@dp-hpd-fast:
- shard-glk: NOTRUN -> [SKIP][92] ([fdo#109271] / [fdo#111827]) +2 similar issues
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk9/igt@[email protected]
* igt@kms_chamelium@hdmi-audio:
- shard-kbl: NOTRUN -> [SKIP][93] ([fdo#109271] / [fdo#111827]) +1 similar issue
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl6/igt@[email protected]
* igt@kms_color_chamelium@pipe-b-ctm-0-25:
- shard-skl: NOTRUN -> [SKIP][94] ([fdo#109271] / [fdo#111827]) +5 similar issues
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl5/igt@[email protected]
* igt@kms_content_protection@lic:
- shard-tglb: NOTRUN -> [SKIP][95] ([i915#1063])
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@[email protected]
* igt@kms_cursor_legacy@2x-flip-vs-cursor-legacy:
- shard-tglb: NOTRUN -> [SKIP][96] ([fdo#109274] / [fdo#111825])
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-atomic:
- shard-skl: [PASS][97] -> [FAIL][98] ([i915#2346])
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl4/igt@[email protected]
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl3/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions-varying-size:
- shard-glk: [PASS][99] -> [FAIL][100] ([i915#2346]) +1 similar issue
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk1/igt@kms_cursor_legacy@[email protected]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk2/igt@kms_cursor_legacy@[email protected]
- shard-skl: NOTRUN -> [FAIL][101] ([i915#2346]) +1 similar issue
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl7/igt@kms_cursor_legacy@[email protected]
* igt@kms_flip@2x-flip-vs-expired-vblank@ac-hdmi-a1-hdmi-a2:
- shard-glk: [PASS][102] -> [FAIL][103] ([i915#79])
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk8/igt@kms_flip@[email protected]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk5/igt@kms_flip@[email protected]
* igt@kms_flip@2x-modeset-vs-vblank-race:
- shard-tglb: NOTRUN -> [SKIP][104] ([fdo#109274] / [fdo#111825] / [i915#3637])
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@[email protected]
* igt@kms_flip@flip-vs-expired-vblank@a-edp1:
- shard-skl: [PASS][105] -> [FAIL][106] ([i915#79]) +1 similar issue
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl4/igt@kms_flip@[email protected]
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl3/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-expired-vblank@b-edp1:
- shard-skl: [PASS][107] -> [FAIL][108] ([i915#2122])
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl4/igt@kms_flip@[email protected]
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl3/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-suspend-interruptible@c-dp1:
- shard-kbl: [PASS][109] -> [DMESG-WARN][110] ([i915#180]) +4 similar issues
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-kbl7/igt@kms_flip@[email protected]
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl1/igt@kms_flip@[email protected]
* igt@kms_flip_scaled_crc@flip-32bpp-yftileccs-to-64bpp-yftile-upscaling@pipe-a-valid-mode:
- shard-iclb: NOTRUN -> [SKIP][111] ([i915#2672]) +2 similar issues
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb1/igt@kms_flip_scaled_crc@flip-32bpp-yftileccs-to-64bpp-yftile-upscaling@pipe-a-valid-mode.html
* igt@kms_frontbuffer_tracking@fbc-tiling-4:
- shard-tglb: NOTRUN -> [SKIP][112] ([i915#5439])
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-shrfb-draw-mmap-cpu:
- shard-skl: NOTRUN -> [SKIP][113] ([fdo#109271]) +99 similar issues
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl7/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-shrfb-draw-mmap-cpu.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-draw-blt:
- shard-tglb: NOTRUN -> [SKIP][114] ([fdo#109280] / [fdo#111825]) +3 similar issues
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-draw-blt.html
* {igt@kms_legacy_colorkey@basic} (NEW):
- {shard-rkl}: NOTRUN -> [SKIP][115] ([fdo#109315])
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-rkl-5/igt@[email protected]
* igt@kms_pipe_b_c_ivb@enable-pipe-c-while-b-has-3-lanes:
- shard-tglb: NOTRUN -> [SKIP][116] ([fdo#109289]) +1 similar issue
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@[email protected]
* igt@kms_plane@plane-panning-bottom-right-suspend@pipe-b-planes:
- shard-apl: [PASS][117] -> [DMESG-WARN][118] ([i915#180]) +3 similar issues
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-apl7/igt@kms_plane@[email protected]
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-apl2/igt@kms_plane@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-alpha-basic:
- shard-kbl: NOTRUN -> [FAIL][119] ([fdo#108145] / [i915#265])
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl6/igt@[email protected]
* igt@kms_plane_lowres@tiling-y@pipe-b-hdmi-a-1:
- shard-glk: [PASS][120] -> [FAIL][121] ([i915#1888])
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk7/igt@kms_plane_lowres@[email protected]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk7/igt@kms_plane_lowres@[email protected]
* igt@kms_psr2_sf@cursor-plane-move-continuous-sf:
- shard-skl: NOTRUN -> [SKIP][122] ([fdo#109271] / [i915#658])
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl5/igt@[email protected]
* igt@kms_psr@psr2_no_drrs:
- shard-iclb: [PASS][123] -> [SKIP][124] ([fdo#109441])
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb2/igt@kms_psr@psr2_no_drrs.html
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb7/igt@kms_psr@psr2_no_drrs.html
* igt@kms_vblank@pipe-d-wait-busy-hang:
- shard-glk: NOTRUN -> [SKIP][125] ([fdo#109271]) +16 similar issues
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk9/igt@[email protected]
* igt@kms_writeback@writeback-fb-id:
- shard-kbl: NOTRUN -> [SKIP][126] ([fdo#109271] / [i915#2437])
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl6/igt@[email protected]
* igt@prime_nv_api@i915_nv_import_twice:
- shard-tglb: NOTRUN -> [SKIP][127] ([fdo#109291])
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@prime_nv_api@i915_nv_import_twice.html
* igt@sw_sync@sync_merge_same:
- shard-skl: NOTRUN -> [FAIL][128] ([i915#6140])
[128]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl5/igt@sw_sync@sync_merge_same.html
* igt@sysfs_clients@fair-1:
- shard-skl: NOTRUN -> [SKIP][129] ([fdo#109271] / [i915#2994])
[129]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl7/igt@[email protected]
#### Possible fixes ####
* igt@gem_busy@close-race:
- shard-snb: [TIMEOUT][130] ([i915#5748]) -> [PASS][131]
[130]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-snb6/igt@[email protected]
[131]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-snb7/igt@[email protected]
* igt@gem_exec_balancer@parallel-bb-first:
- shard-iclb: [SKIP][132] ([i915#4525]) -> [PASS][133] +1 similar issue
[132]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb8/igt@[email protected]
[133]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb1/igt@[email protected]
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-iclb: [FAIL][134] ([i915#2842]) -> [PASS][135]
[134]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb1/igt@gem_exec_fair@[email protected]
[135]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb4/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@vcs0:
- shard-kbl: [FAIL][136] ([i915#2842]) -> [PASS][137]
[136]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-kbl7/igt@gem_exec_fair@[email protected]
[137]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl4/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-throttle@rcs0:
- shard-iclb: [FAIL][138] ([i915#2849]) -> [PASS][139]
[138]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb6/igt@gem_exec_fair@[email protected]
[139]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb8/igt@gem_exec_fair@[email protected]
* igt@gem_exec_whisper@basic-contexts-forked-all:
- shard-glk: [DMESG-WARN][140] ([i915#118]) -> [PASS][141]
[140]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk6/igt@[email protected]
[141]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk5/igt@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-skl: [DMESG-WARN][142] ([i915#5566] / [i915#716]) -> [PASS][143]
[142]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl9/igt@[email protected]
[143]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl4/igt@[email protected]
* igt@i915_module_load@reload-with-fault-injection:
- shard-tglb: [TIMEOUT][144] ([i915#3953]) -> [PASS][145]
[144]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-tglb8/igt@[email protected]
[145]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb1/igt@[email protected]
* igt@i915_selftest@live@hangcheck:
- shard-snb: [INCOMPLETE][146] ([i915#3921]) -> [PASS][147]
[146]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-snb6/igt@i915_selftest@[email protected]
[147]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-snb2/igt@i915_selftest@[email protected]
- shard-tglb: [DMESG-WARN][148] ([i915#5591]) -> [PASS][149]
[148]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-tglb3/igt@i915_selftest@[email protected]
[149]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb3/igt@i915_selftest@[email protected]
* igt@kms_async_flips@alternate-sync-async-flip@pipe-c-edp-1:
- shard-skl: [FAIL][150] ([i915#2521]) -> [PASS][151]
[150]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl4/igt@kms_async_flips@[email protected]
[151]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl4/igt@kms_async_flips@[email protected]
* igt@kms_cursor_legacy@short-flip-before-cursor@atomic-transitions-varying-size:
- shard-skl: [FAIL][152] -> [PASS][153]
[152]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl3/igt@kms_cursor_legacy@[email protected]
[153]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl5/igt@kms_cursor_legacy@[email protected]
* igt@kms_flip@flip-vs-suspend-interruptible@a-dp1:
- shard-kbl: [DMESG-WARN][154] ([i915#180]) -> [PASS][155] +4 similar issues
[154]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-kbl7/igt@kms_flip@[email protected]
[155]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl1/igt@kms_flip@[email protected]
* igt@kms_flip@plain-flip-ts-check-interruptible@b-edp1:
- shard-skl: [FAIL][156] ([i915#2122]) -> [PASS][157]
[156]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl5/igt@kms_flip@[email protected]
[157]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl7/igt@kms_flip@[email protected]
* igt@kms_flip@plain-flip-ts-check-interruptible@c-dp1:
- shard-kbl: [FAIL][158] ([i915#2122]) -> [PASS][159]
[158]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-kbl6/igt@kms_flip@[email protected]
[159]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl1/igt@kms_flip@[email protected]
* igt@kms_hdr@bpc-switch@pipe-a-dp-1:
- shard-kbl: [FAIL][160] ([i915#1188]) -> [PASS][161]
[160]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-kbl6/igt@kms_hdr@[email protected]
[161]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl4/igt@kms_hdr@[email protected]
* igt@kms_plane@plane-position-covered@pipe-b-planes:
- shard-tglb: [INCOMPLETE][162] -> [PASS][163]
[162]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-tglb8/igt@kms_plane@[email protected]
[163]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@kms_plane@[email protected]
* igt@kms_plane_lowres@tiling-y@pipe-c-hdmi-a-2:
- shard-glk: [FAIL][164] ([i915#1888]) -> [PASS][165]
[164]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk7/igt@kms_plane_lowres@[email protected]
[165]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk7/igt@kms_plane_lowres@[email protected]
* igt@kms_psr@psr2_primary_render:
- shard-iclb: [SKIP][166] ([fdo#109441]) -> [PASS][167]
[166]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb5/igt@kms_psr@psr2_primary_render.html
[167]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb2/igt@kms_psr@psr2_primary_render.html
* igt@perf@polling-parameterized:
- shard-skl: [FAIL][168] ([i915#1888] / [i915#5639]) -> [PASS][169]
[168]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl7/igt@[email protected]
[169]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl7/igt@[email protected]
#### Warnings ####
* igt@gem_exec_fair@basic-none-rrul@rcs0:
- shard-iclb: [FAIL][170] ([i915#2842]) -> [FAIL][171] ([i915#2852])
[170]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb6/igt@gem_exec_fair@[email protected]
[171]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb8/igt@gem_exec_fair@[email protected]
* igt@i915_pm_rc6_residency@rc6-idle@vcs0:
- shard-iclb: [FAIL][172] ([i915#2684]) -> [WARN][173] ([i915#2684])
[172]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb3/igt@i915_pm_rc6_residency@[email protected]
[173]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb1/igt@i915_pm_rc6_residency@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-2p-pri-indfb-multidraw:
- shard-skl: [SKIP][174] ([fdo#109271]) -> [SKIP][175] ([fdo#109271] / [i915#1888])
[174]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl9/igt@[email protected]
[175]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl3/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-onoff:
- shard-skl: [SKIP][176] ([fdo#109271] / [i915#1888]) -> [SKIP][177] ([fdo#109271])
[176]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl10/igt@[email protected]
[177]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl9/igt@[email protected]
* igt@kms_psr2_sf@cursor-plane-move-continuous-sf:
- shard-iclb: [SKIP][178] ([i915#2920]) -> [SKIP][179] ([i915#658])
[178]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb2/igt@[email protected]
[179]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb7/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[IGT#2]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/2
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280
[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#109300]: https://bugs.freedesktop.org/show_bug.cgi?id=109300
[fdo#109302]: https://bugs.freedesktop.org/show_bug.cgi?id=109302
[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#109313]: https://bugs.freedesktop.org/show_bug.cgi?id=109313
[fdo#109314]: https://bugs.freedesktop.org/show_bug.cgi?id=109314
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109506]: https://bugs.freedesktop.org/show_bug.cgi?id=109506
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189
[fdo#110254]: https://bugs.freedesktop.org/show_bug.cgi?id=110254
[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#111314]: https://bugs.freedesktop.org/show_bug.cgi?id=111314
[fdo#111614]: https://bugs.freedesktop.org/show_bug.cgi?id=111614
[fdo#111615]: https://bugs.freedesktop.org/show_bug.cgi?id=111615
[fdo#111644]: https://bugs.freedesktop.org/show_bug.cgi?id=111644
[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#1063]: https://gitlab.freedesktop.org/drm/intel/issues/1063
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1099]: https://gitlab.freedesktop.org/drm/intel/issues/1099
[i915#1155]: https://gitlab.freedesktop.org/drm/intel/issues/1155
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[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#1755]: https://gitlab.freedesktop.org/drm/intel/issues/1755
[i915#1769]: https://gitlab.freedesktop.org/drm/intel/issues/1769
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1825]: https://gitlab.freedesktop.org/drm/intel/issues/1825
[i915#1836]: https://gitlab.freedesktop.org/drm/intel/issues/1836
[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#1886]: https://gitlab.freedesktop.org/drm/intel/issues/1886
[i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
[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#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#2530]: https://gitlab.freedesktop.org/drm/intel/issues/2530
[i915#2575]: https://gitlab.freedesktop.org/drm/intel/issues/2575
[i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#2658]: https://gitlab.freedesktop.org/drm/intel/issues/2658
[i915#2672]: https://gitlab.freedesktop.org/drm/intel/issues/2672
[i915#2681]: https://gitlab.freedesktop.org/drm/intel/issues/2681
[i915#2684]: https://gitlab.freedesktop.org/drm/intel/issues/2684
[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#2849]: https://gitlab.freedesktop.org/drm/intel/issues/2849
[i915#2852]: https://gitlab.freedesktop.org/drm/intel/issues/2852
[i915#2856]: https://gitlab.freedesktop.org/drm/intel/issues/2856
[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#3063]: https://gitlab.freedesktop.org/drm/intel/issues/3063
[i915#3116]: https://gitlab.freedesktop.org/drm/intel/issues/3116
[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#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#3376]: https://gitlab.freedesktop.org/drm/intel/issues/3376
[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#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#3743]: https://gitlab.freedesktop.org/drm/intel/issues/3743
[i915#3804]: https://gitlab.freedesktop.org/drm/intel/issues/3804
[i915#3825]: https://gitlab.freedesktop.org/drm/intel/issues/3825
[i915#3826]: https://gitlab.freedesktop.org/drm/intel/issues/3826
[i915#3828]: https://gitlab.freedesktop.org/drm/intel/issues/3828
[i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#3921]: https://gitlab.freedesktop.org/drm/intel/issues/3921
[i915#3936]: https://gitlab.freedesktop.org/drm/intel/issues/3936
[i915#3938]: https://gitlab.freedesktop.org/drm/intel/issues/3938
[i915#3952]: https://gitlab.freedesktop.org/drm/intel/issues/3952
[i915#3953]: https://gitlab.freedesktop.org/drm/intel/issues/3953
[i915#3955]: https://gitlab.freedesktop.org/drm/intel/issues/3955
[i915#3966]: https://gitlab.freedesktop.org/drm/intel/issues/3966
[i915#3989]: https://gitlab.freedesktop.org/drm/intel/issues/3989
[i915#4016]: https://gitlab.freedesktop.org/drm/intel/issues/4016
[i915#4032]: https://gitlab.freedesktop.org/drm/intel/issues/4032
[i915#4036]: https://gitlab.freedesktop.org/drm/intel/issues/4036
[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#4137]: https://gitlab.freedesktop.org/drm/intel/issues/4137
[i915#4212]: https://gitlab.freedesktop.org/drm/intel/issues/4212
[i915#4213]: https://gitlab.freedesktop.org/drm/intel/issues/4213
[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#433]: https://gitlab.freedesktop.org/drm/intel/issues/433
[i915#4369]: https://gitlab.freedesktop.org/drm/intel/issues/4369
[i915#4387]: https://gitlab.freedesktop.org/drm/intel/issues/4387
[i915#4392]: https://gitlab.freedesktop.org/drm/intel/issues/4392
[i915#4462]: https://gitlab.freedesktop.org/drm/intel/issues/4462
[i915#4494]: https://gitlab.freedesktop.org/drm/intel/issues/4494
[i915#4525]: https://gitlab.freedesktop.org/drm/intel/issues/4525
[i915#4538]: https://gitlab.freedesktop.org/drm/intel/issues/4538
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#4565]: https://gitlab.freedesktop.org/drm/intel/issues/4565
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4771]: https://gitlab.freedesktop.org/drm/intel/issues/4771
[i915#4778]: https://gitlab.freedesktop.org/drm/intel/issues/4778
[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#4853]: https://gitlab.freedesktop.org/drm/intel/issues/4853
[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#4874]: https://gitlab.freedesktop.org/drm/intel/issues/4874
[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#4883]: https://gitlab.freedesktop.org/drm/intel/issues/4883
[i915#4884]: https://gitlab.freedesktop.org/drm/intel/issues/4884
[i915#4893]: https://gitlab.freedesktop.org/drm/intel/issues/4893
[i915#4904]: https://gitlab.freedesktop.org/drm/intel/issues/4904
[i915#4936]: https://gitlab.freedesktop.org/drm/intel/issues/4936
[i915#4941]: https://gitlab.freedesktop.org/drm/intel/issues/4941
[i915#4957]: https://gitlab.freedesktop.org/drm/intel/issues/4957
[i915#4958]: https://gitlab.freedesktop.org/drm/intel/issues/4958
[i915#4991]: https://gitlab.freedesktop.org/drm/intel/issues/4991
[i915#5174]: https://gitlab.freedesktop.org/drm/intel/issues/5174
[i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176
[i915#5182]: https://gitlab.freedesktop.org/drm/intel/issues/5182
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#5257]: https://gitlab.freedesktop.org/drm/intel/issues/5257
[i915#5264]: https://gitlab.freedesktop.org/drm/intel/issues/5264
[i915#5286]: https://gitlab.freedesktop.org/drm/intel/issues/5286
[i915#5287]: https://gitlab.freedesktop.org/drm/intel/issues/5287
[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#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#5591]: https://gitlab.freedesktop.org/drm/intel/issues/5591
[i915#5639]: https://gitlab.freedesktop.org/drm/intel/issues/5639
[i915#5723]: https://gitlab.freedesktop.org/drm/intel/issues/5723
[i915#5748]: https://gitlab.freedesktop.org/drm/intel/issues/5748
[i915#5784]: https://gitlab.freedesktop.org/drm/intel/issues/5784
[i915#5903]: https://gitlab.freedesktop.org/drm/intel/issues/5903
[i915#6011]: https://gitlab.freedesktop.org/drm/intel/issues/6011
[i915#6095]: https://gitlab.freedesktop.org/drm/intel/issues/6095
[i915#6117]: https://gitlab.freedesktop.org/drm/intel/issues/6117
[i915#6140]: https://gitlab.freedesktop.org/drm/intel/issues/6140
[i915#6141]: https://gitlab.freedesktop.org/drm/intel/issues/6141
[i915#6227]: https://gitlab.freedesktop.org/drm/intel/issues/6227
[i915#6230]: https://gitlab.freedesktop.org/drm/intel/issues/6230
[i915#6245]: https://gitlab.freedesktop.org/drm/intel/issues/6245
[i915#6248]: https://gitlab.freedesktop.org/drm/intel/issues/6248
[i915#6301]: https://gitlab.freedesktop.org/drm/intel/issues/6301
[i915#6331]: https://gitlab.freedesktop.org/drm/intel/issues/6331
[i915#6334]: https://gitlab.freedesktop.org/drm/intel/issues/6334
[i915#6335]: https://gitlab.freedesktop.org/drm/intel/issues/6335
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[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_11862 -> Patchwork_105925v2
CI-20190529: 20190529
CI_DRM_11862: ffee806d103b9604db7eb9cd689c098aca1ffa96 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6563: 7d43b49bf10788d4870668f93a800888fc8ab339 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_105925v2: ffee806d103b9604db7eb9cd689c098aca1ffa96 @ 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_105925v2/index.html
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: Apply waitboosting before fence wait (rev2)
Quoted 47 lines · Patchwork
*Patch Details*
*Series:* drm/i915: Apply waitboosting before fence wait (rev2)
*URL:* https://patchwork.freedesktop.org/series/105925/ <https://patchwork.freedesktop.org/series/105925/>
*State:* failure
*Details:* https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/index.html <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/index.html>CI Bug Log - changes from
CI_DRM_11862_full->Patchwork_105925v2_fullSummary
*FAILURE*
Serious unknown changes coming with
Patchwork_105925v2_fullabsolutely need to be verified manually.If you think the reported changes have nothing to do with the changes introduced in
Patchwork_105925v2_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.Participating hosts (10 -> 13)Additional (3): shard-rkl shard-dg1 shard-tglu
Possible new issues
Here are the unknown changes that may have been introduced in
Patchwork_105925v2_full:IGT changes
Possible regressions
*
igt@i915_pm_rc6_residency@rc6-idle@vcs0: o shard-apl: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-apl2/igt@i915_pm_rc6_residency@[email protected]> -> WARN <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-apl2/igt@i915_pm_rc6_residency@[email protected]>*
Quoted 8 lines
igt@kms_vblank@pipe-d-wait-forked-busy-hang:
o shard-tglb: PASS
<https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-tglb8/igt@[email protected]>
-> INCOMPLETE
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb8/igt@[email protected]>
+1 similar issueThese issues are unrelated to the patchset changes
Quoted 946 lines
Suppressed
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
*
igt@kms_cursor_crc@cursor-offscreen:
o {shard-rkl}: NOTRUN -> SKIP
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-rkl-5/igt@[email protected]>
+1 similar issue
*{igt@kms_invalid_mode@clock-too-high@edp-1-pipe-d}:
o shard-tglb: NOTRUN -> SKIP
<https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@kms_invalid_mode@[email protected]>
+3 similar issuesNew tests
New tests have been introduced between
CI_DRM_11862_fullandPatchwork_105925v2_full:New IGT tests (1)
* igt@kms_legacy_colorkey@basic:
o Statuses : 1 skip(s)
o Exec time: [0.0] sKnown issues
Here are the changes found in
Patchwork_105925v2_fullthat come from known issues:CI changes
Issues hit
* boot:
o shard-glk: (PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk5/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk5/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk1/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk1/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk1/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk2/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk2/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk2/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk2/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk3/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk3/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk5/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk9/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk9/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk9/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk9/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk8/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk8/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk8/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk7/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk7/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk7/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk6/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk6/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk6/boot.html>) -> (PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk9/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk9/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk8/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk7/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk7/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk8/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk8/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk9/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk1/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk1/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk1/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk2/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk2/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk3/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk3/boot.html>, FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk3/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk3/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk5/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk5/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk5/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk6/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk6/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk7/boot.html>, PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk7/boot.html>) (i915#4392 <https://gitlab.freedesktop.org/drm/intel/issues/4392>) IGT changes Issues hit*
igt@gem_ctx_persistence@engines-hostile-preempt: o shard-snb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-snb7/igt@[email protected]> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#1099 <https://gitlab.freedesktop.org/drm/intel/issues/1099>) +1 similar issue*
igt@gem_ctx_persistence@hostile: o shard-tglb: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@[email protected]> (i915#2410 <https://gitlab.freedesktop.org/drm/intel/issues/2410>)*
igt@gem_exec_balancer@parallel-balancer: o shard-snb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-snb7/igt@[email protected]> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +26 similar issues*
igt@gem_exec_balancer@parallel-contexts: o shard-iclb: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb4/igt@[email protected]> -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb5/igt@[email protected]> (i915#4525 <https://gitlab.freedesktop.org/drm/intel/issues/4525>)*
igt@gem_exec_fair@basic-none-share@rcs0: o shard-glk: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk9/igt@gem_exec_fair@[email protected]> (i915#2842 <https://gitlab.freedesktop.org/drm/intel/issues/2842>)*
igt@gem_exec_fair@basic-none-vip@rcs0: o shard-kbl: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl6/igt@gem_exec_fair@[email protected]> (i915#2842 <https://gitlab.freedesktop.org/drm/intel/issues/2842>)*
igt@gem_exec_fair@basic-pace@bcs0: o shard-iclb: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb1/igt@gem_exec_fair@[email protected]> -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb4/igt@gem_exec_fair@[email protected]> (i915#2842 <https://gitlab.freedesktop.org/drm/intel/issues/2842>)*
igt@gem_exec_fair@basic-pace@rcs0: o shard-kbl: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-kbl7/igt@gem_exec_fair@[email protected]> -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl4/igt@gem_exec_fair@[email protected]> (i915#2842 <https://gitlab.freedesktop.org/drm/intel/issues/2842>) +2 similar issues o shard-glk: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk9/igt@gem_exec_fair@[email protected]> -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk9/igt@gem_exec_fair@[email protected]> (i915#2842 <https://gitlab.freedesktop.org/drm/intel/issues/2842>)*
igt@gem_lmem_swapping@heavy-verify-random: o shard-skl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl5/igt@[email protected]> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#4613 <https://gitlab.freedesktop.org/drm/intel/issues/4613>) +1 similar issue*
igt@gem_lmem_swapping@smem-oom: o shard-kbl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl6/igt@[email protected]> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#4613 <https://gitlab.freedesktop.org/drm/intel/issues/4613>)*
igt@gem_pxp@create-regular-context-1: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@[email protected]> (i915#4270 <https://gitlab.freedesktop.org/drm/intel/issues/4270>)*
igt@gem_softpin@evict-snoop-interruptible: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@[email protected]> (fdo#109312 <https://bugs.freedesktop.org/show_bug.cgi?id=109312>)*
igt@gem_userptr_blits@vma-merge: o shard-skl: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl5/igt@[email protected]> (i915#3318 <https://gitlab.freedesktop.org/drm/intel/issues/3318>)*
igt@gen9_exec_parse@allowed-single: o shard-glk: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk6/igt@[email protected]> -> DMESG-WARN <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk5/igt@[email protected]> (i915#5566 <https://gitlab.freedesktop.org/drm/intel/issues/5566> / i915#716 <https://gitlab.freedesktop.org/drm/intel/issues/716>)*
igt@i915_pm_dc@dc3co-vpb-simulation: o shard-glk: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk9/igt@[email protected]> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#658 <https://gitlab.freedesktop.org/drm/intel/issues/658>)*
igt@i915_pm_dc@dc6-psr: o shard-iclb: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb4/igt@[email protected]> -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb7/igt@[email protected]> (i915#454 <https://gitlab.freedesktop.org/drm/intel/issues/454>)*
igt@i915_pm_rc6_residency@rc6-idle@rcs0: o shard-tglb: NOTRUN -> WARN <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@i915_pm_rc6_residency@[email protected]> (i915#2681 <https://gitlab.freedesktop.org/drm/intel/issues/2681>) +3 similar issues*
igt@i915_selftest@live@gt_pm: o shard-skl: NOTRUN -> DMESG-FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl4/igt@i915_selftest@live@gt_pm.html> (i915#1886 <https://gitlab.freedesktop.org/drm/intel/issues/1886>)*
igt@i915_suspend@debugfs-reader: o shard-kbl: NOTRUN -> DMESG-WARN <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl6/igt@[email protected]> (i915#180 <https://gitlab.freedesktop.org/drm/intel/issues/180>)*
igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-0-hflip: o shard-skl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl5/igt@[email protected]> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#1888 <https://gitlab.freedesktop.org/drm/intel/issues/1888>)*
igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-async-flip: o shard-skl: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl7/igt@kms_big_fb@yf-tiled-max-hw-stride-32bpp-rotate-180-async-flip.html> (i915#3743 <https://gitlab.freedesktop.org/drm/intel/issues/3743>)*
igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0-hflip-async-flip: o shard-kbl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl6/igt@kms_big_fb@yf-tiled-max-hw-stride-64bpp-rotate-0-hflip-async-flip.html> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +31 similar issues*
igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_mc_ccs: o shard-skl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl5/igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_mc_ccs.html> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#3886 <https://gitlab.freedesktop.org/drm/intel/issues/3886>) +6 similar issues*
igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_mc_ccs: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_mc_ccs.html> (i915#3689 <https://gitlab.freedesktop.org/drm/intel/issues/3689> / i915#3886 <https://gitlab.freedesktop.org/drm/intel/issues/3886>)*
igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc: o shard-kbl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl6/igt@kms_ccs@pipe-a-ccs-on-another-bo-y_tiled_gen12_rc_ccs_cc.html> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#3886 <https://gitlab.freedesktop.org/drm/intel/issues/3886>)*
igt@kms_ccs@pipe-b-bad-pixel-format-y_tiled_ccs: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@kms_ccs@pipe-b-bad-pixel-format-y_tiled_ccs.html> (i915#3689 <https://gitlab.freedesktop.org/drm/intel/issues/3689>) +1 similar issue*
igt@kms_ccs@pipe-c-bad-pixel-format-4_tiled_dg2_rc_ccs: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@kms_ccs@pipe-c-bad-pixel-format-4_tiled_dg2_rc_ccs.html> (i915#6095 <https://gitlab.freedesktop.org/drm/intel/issues/6095>) +2 similar issues*
igt@kms_ccs@pipe-c-crc-sprite-planes-basic-yf_tiled_ccs: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@kms_ccs@pipe-c-crc-sprite-planes-basic-yf_tiled_ccs.html> (fdo#111615 <https://bugs.freedesktop.org/show_bug.cgi?id=111615> / i915#3689 <https://gitlab.freedesktop.org/drm/intel/issues/3689>)*
igt@kms_chamelium@dp-hpd-after-suspend: o shard-snb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-snb7/igt@[email protected]> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271> / fdo#111827 <https://bugs.freedesktop.org/show_bug.cgi?id=111827>) +1 similar issue*
igt@kms_chamelium@dp-hpd-fast: o shard-glk: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk9/igt@[email protected]> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271> / fdo#111827 <https://bugs.freedesktop.org/show_bug.cgi?id=111827>) +2 similar issues*
igt@kms_chamelium@hdmi-audio: o shard-kbl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl6/igt@[email protected]> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271> / fdo#111827 <https://bugs.freedesktop.org/show_bug.cgi?id=111827>) +1 similar issue*
igt@kms_color_chamelium@pipe-b-ctm-0-25: o shard-skl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl5/igt@[email protected]> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271> / fdo#111827 <https://bugs.freedesktop.org/show_bug.cgi?id=111827>) +5 similar issues*
igt@kms_content_protection@lic: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@[email protected]> (i915#1063 <https://gitlab.freedesktop.org/drm/intel/issues/1063>)*
igt@kms_cursor_legacy@2x-flip-vs-cursor-legacy: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@[email protected]> (fdo#109274 <https://bugs.freedesktop.org/show_bug.cgi?id=109274> / fdo#111825 <https://bugs.freedesktop.org/show_bug.cgi?id=111825>)*
igt@kms_cursor_legacy@flip-vs-cursor-busy-crc-atomic: o shard-skl: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl4/igt@[email protected]> -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl3/igt@[email protected]> (i915#2346 <https://gitlab.freedesktop.org/drm/intel/issues/2346>)*
igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions-varying-size: o shard-glk: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk1/igt@kms_cursor_legacy@[email protected]> -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk2/igt@kms_cursor_legacy@[email protected]> (i915#2346 <https://gitlab.freedesktop.org/drm/intel/issues/2346>) +1 similar issue o shard-skl: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl7/igt@kms_cursor_legacy@[email protected]> (i915#2346 <https://gitlab.freedesktop.org/drm/intel/issues/2346>) +1 similar issue*
igt@kms_flip@2x-flip-vs-expired-vblank@ac-hdmi-a1-hdmi-a2: o shard-glk: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk8/igt@kms_flip@[email protected]> -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk5/igt@kms_flip@[email protected]> (i915#79 <https://gitlab.freedesktop.org/drm/intel/issues/79>)*
igt@kms_flip@2x-modeset-vs-vblank-race: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@[email protected]> (fdo#109274 <https://bugs.freedesktop.org/show_bug.cgi?id=109274> / fdo#111825 <https://bugs.freedesktop.org/show_bug.cgi?id=111825> / i915#3637 <https://gitlab.freedesktop.org/drm/intel/issues/3637>)*
igt@kms_flip@flip-vs-expired-vblank@a-edp1: o shard-skl: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl4/igt@kms_flip@[email protected]> -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl3/igt@kms_flip@[email protected]> (i915#79 <https://gitlab.freedesktop.org/drm/intel/issues/79>) +1 similar issue*
igt@kms_flip@flip-vs-expired-vblank@b-edp1: o shard-skl: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl4/igt@kms_flip@[email protected]> -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl3/igt@kms_flip@[email protected]> (i915#2122 <https://gitlab.freedesktop.org/drm/intel/issues/2122>)*
igt@kms_flip@flip-vs-suspend-interruptible@c-dp1: o shard-kbl: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-kbl7/igt@kms_flip@[email protected]> -> DMESG-WARN <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl1/igt@kms_flip@[email protected]> (i915#180 <https://gitlab.freedesktop.org/drm/intel/issues/180>) +4 similar issues*
igt@kms_flip_scaled_crc@flip-32bpp-yftileccs-to-64bpp-yftile-upscaling@pipe-a-valid-mode: o shard-iclb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb1/igt@kms_flip_scaled_crc@flip-32bpp-yftileccs-to-64bpp-yftile-upscaling@pipe-a-valid-mode.html> (i915#2672 <https://gitlab.freedesktop.org/drm/intel/issues/2672>) +2 similar issues*
igt@kms_frontbuffer_tracking@fbc-tiling-4: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@[email protected]> (i915#5439 <https://gitlab.freedesktop.org/drm/intel/issues/5439>)*
igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-shrfb-draw-mmap-cpu: o shard-skl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl7/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-pri-shrfb-draw-mmap-cpu.html> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +99 similar issues*
igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-draw-blt: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-draw-blt.html> (fdo#109280 <https://bugs.freedesktop.org/show_bug.cgi?id=109280> / fdo#111825 <https://bugs.freedesktop.org/show_bug.cgi?id=111825>) +3 similar issues*
{igt@kms_legacy_colorkey@basic} (NEW): o {shard-rkl}: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-rkl-5/igt@[email protected]> (fdo#109315 <https://bugs.freedesktop.org/show_bug.cgi?id=109315>)*
igt@kms_pipe_b_c_ivb@enable-pipe-c-while-b-has-3-lanes: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@[email protected]> (fdo#109289 <https://bugs.freedesktop.org/show_bug.cgi?id=109289>) +1 similar issue*
igt@kms_plane@plane-panning-bottom-right-suspend@pipe-b-planes: o shard-apl: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-apl7/igt@kms_plane@[email protected]> -> DMESG-WARN <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-apl2/igt@kms_plane@[email protected]> (i915#180 <https://gitlab.freedesktop.org/drm/intel/issues/180>) +3 similar issues*
igt@kms_plane_alpha_blend@pipe-c-alpha-basic: o shard-kbl: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl6/igt@[email protected]> (fdo#108145 <https://bugs.freedesktop.org/show_bug.cgi?id=108145> / i915#265 <https://gitlab.freedesktop.org/drm/intel/issues/265>)*
igt@kms_plane_lowres@tiling-y@pipe-b-hdmi-a-1: o shard-glk: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk7/igt@kms_plane_lowres@[email protected]> -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk7/igt@kms_plane_lowres@[email protected]> (i915#1888 <https://gitlab.freedesktop.org/drm/intel/issues/1888>)*
igt@kms_psr2_sf@cursor-plane-move-continuous-sf: o shard-skl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl5/igt@[email protected]> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#658 <https://gitlab.freedesktop.org/drm/intel/issues/658>)*
igt@kms_psr@psr2_no_drrs: o shard-iclb: PASS <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb2/igt@kms_psr@psr2_no_drrs.html> -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb7/igt@kms_psr@psr2_no_drrs.html> (fdo#109441 <https://bugs.freedesktop.org/show_bug.cgi?id=109441>)*
igt@kms_vblank@pipe-d-wait-busy-hang: o shard-glk: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk9/igt@[email protected]> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271>) +16 similar issues*
igt@kms_writeback@writeback-fb-id: o shard-kbl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl6/igt@[email protected]> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#2437 <https://gitlab.freedesktop.org/drm/intel/issues/2437>)*
igt@prime_nv_api@i915_nv_import_twice: o shard-tglb: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@prime_nv_api@i915_nv_import_twice.html> (fdo#109291 <https://bugs.freedesktop.org/show_bug.cgi?id=109291>)*
igt@sw_sync@sync_merge_same: o shard-skl: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl5/igt@sw_sync@sync_merge_same.html> (i915#6140 <https://gitlab.freedesktop.org/drm/intel/issues/6140>)*
igt@sysfs_clients@fair-1: o shard-skl: NOTRUN -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl7/igt@[email protected]> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#2994 <https://gitlab.freedesktop.org/drm/intel/issues/2994>) Possible fixes*
igt@gem_busy@close-race: o shard-snb: TIMEOUT <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-snb6/igt@[email protected]> (i915#5748 <https://gitlab.freedesktop.org/drm/intel/issues/5748>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-snb7/igt@[email protected]>*
igt@gem_exec_balancer@parallel-bb-first: o shard-iclb: SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb8/igt@[email protected]> (i915#4525 <https://gitlab.freedesktop.org/drm/intel/issues/4525>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb1/igt@[email protected]> +1 similar issue*
igt@gem_exec_fair@basic-none-share@rcs0: o shard-iclb: FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb1/igt@gem_exec_fair@[email protected]> (i915#2842 <https://gitlab.freedesktop.org/drm/intel/issues/2842>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb4/igt@gem_exec_fair@[email protected]>*
igt@gem_exec_fair@basic-pace@vcs0: o shard-kbl: FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-kbl7/igt@gem_exec_fair@[email protected]> (i915#2842 <https://gitlab.freedesktop.org/drm/intel/issues/2842>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl4/igt@gem_exec_fair@[email protected]>*
igt@gem_exec_fair@basic-throttle@rcs0: o shard-iclb: FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb6/igt@gem_exec_fair@[email protected]> (i915#2849 <https://gitlab.freedesktop.org/drm/intel/issues/2849>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb8/igt@gem_exec_fair@[email protected]>*
igt@gem_exec_whisper@basic-contexts-forked-all: o shard-glk: DMESG-WARN <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk6/igt@[email protected]> (i915#118 <https://gitlab.freedesktop.org/drm/intel/issues/118>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk5/igt@[email protected]>*
igt@gen9_exec_parse@allowed-all: o shard-skl: DMESG-WARN <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl9/igt@[email protected]> (i915#5566 <https://gitlab.freedesktop.org/drm/intel/issues/5566> / i915#716 <https://gitlab.freedesktop.org/drm/intel/issues/716>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl4/igt@[email protected]>*
igt@i915_module_load@reload-with-fault-injection: o shard-tglb: TIMEOUT <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-tglb8/igt@[email protected]> (i915#3953 <https://gitlab.freedesktop.org/drm/intel/issues/3953>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb1/igt@[email protected]>*
igt@i915_selftest@live@hangcheck: o shard-snb: INCOMPLETE <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-snb6/igt@i915_selftest@[email protected]> (i915#3921 <https://gitlab.freedesktop.org/drm/intel/issues/3921>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-snb2/igt@i915_selftest@[email protected]> o shard-tglb: DMESG-WARN <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-tglb3/igt@i915_selftest@[email protected]> (i915#5591 <https://gitlab.freedesktop.org/drm/intel/issues/5591>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb3/igt@i915_selftest@[email protected]>*
igt@kms_async_flips@alternate-sync-async-flip@pipe-c-edp-1: o shard-skl: FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl4/igt@kms_async_flips@[email protected]> (i915#2521 <https://gitlab.freedesktop.org/drm/intel/issues/2521>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl4/igt@kms_async_flips@[email protected]>*
igt@kms_cursor_legacy@short-flip-before-cursor@atomic-transitions-varying-size: o shard-skl: FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl3/igt@kms_cursor_legacy@[email protected]> -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl5/igt@kms_cursor_legacy@[email protected]>*
igt@kms_flip@flip-vs-suspend-interruptible@a-dp1: o shard-kbl: DMESG-WARN <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-kbl7/igt@kms_flip@[email protected]> (i915#180 <https://gitlab.freedesktop.org/drm/intel/issues/180>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl1/igt@kms_flip@[email protected]> +4 similar issues*
igt@kms_flip@plain-flip-ts-check-interruptible@b-edp1: o shard-skl: FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl5/igt@kms_flip@[email protected]> (i915#2122 <https://gitlab.freedesktop.org/drm/intel/issues/2122>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl7/igt@kms_flip@[email protected]>*
igt@kms_flip@plain-flip-ts-check-interruptible@c-dp1: o shard-kbl: FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-kbl6/igt@kms_flip@[email protected]> (i915#2122 <https://gitlab.freedesktop.org/drm/intel/issues/2122>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl1/igt@kms_flip@[email protected]>*
igt@kms_hdr@bpc-switch@pipe-a-dp-1: o shard-kbl: FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-kbl6/igt@kms_hdr@[email protected]> (i915#1188 <https://gitlab.freedesktop.org/drm/intel/issues/1188>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-kbl4/igt@kms_hdr@[email protected]>*
igt@kms_plane@plane-position-covered@pipe-b-planes: o shard-tglb: INCOMPLETE <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-tglb8/igt@kms_plane@[email protected]> -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-tglb2/igt@kms_plane@[email protected]>*
igt@kms_plane_lowres@tiling-y@pipe-c-hdmi-a-2: o shard-glk: FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-glk7/igt@kms_plane_lowres@[email protected]> (i915#1888 <https://gitlab.freedesktop.org/drm/intel/issues/1888>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-glk7/igt@kms_plane_lowres@[email protected]>*
igt@kms_psr@psr2_primary_render: o shard-iclb: SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb5/igt@kms_psr@psr2_primary_render.html> (fdo#109441 <https://bugs.freedesktop.org/show_bug.cgi?id=109441>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb2/igt@kms_psr@psr2_primary_render.html>*
igt@perf@polling-parameterized: o shard-skl: FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl7/igt@[email protected]> (i915#1888 <https://gitlab.freedesktop.org/drm/intel/issues/1888> / i915#5639 <https://gitlab.freedesktop.org/drm/intel/issues/5639>) -> PASS <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl7/igt@[email protected]> Warnings*
igt@gem_exec_fair@basic-none-rrul@rcs0: o shard-iclb: FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb6/igt@gem_exec_fair@[email protected]> (i915#2842 <https://gitlab.freedesktop.org/drm/intel/issues/2842>) -> FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb8/igt@gem_exec_fair@[email protected]> (i915#2852 <https://gitlab.freedesktop.org/drm/intel/issues/2852>)*
igt@i915_pm_rc6_residency@rc6-idle@vcs0: o shard-iclb: FAIL <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb3/igt@i915_pm_rc6_residency@[email protected]> (i915#2684 <https://gitlab.freedesktop.org/drm/intel/issues/2684>) -> WARN <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb1/igt@i915_pm_rc6_residency@[email protected]> (i915#2684 <https://gitlab.freedesktop.org/drm/intel/issues/2684>)*
igt@kms_frontbuffer_tracking@fbcpsr-2p-pri-indfb-multidraw: o shard-skl: SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl9/igt@[email protected]> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271>) -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl3/igt@[email protected]> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#1888 <https://gitlab.freedesktop.org/drm/intel/issues/1888>)*
igt@kms_frontbuffer_tracking@fbcpsr-2p-scndscrn-cur-indfb-onoff: o shard-skl: SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-skl10/igt@[email protected]> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271> / i915#1888 <https://gitlab.freedesktop.org/drm/intel/issues/1888>) -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-skl9/igt@[email protected]> (fdo#109271 <https://bugs.freedesktop.org/show_bug.cgi?id=109271>)*
igt@kms_psr2_sf@cursor-plane-move-continuous-sf: o shard-iclb: SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11862/shard-iclb2/igt@[email protected]> (i915#2920 <https://gitlab.freedesktop.org/drm/intel/issues/2920>) -> SKIP <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105925v2/shard-iclb7/igt@[email protected]> (i915#658 <https://gitlab.freedesktop.org/drm/intel/issues/658>){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_11862->Patchwork_105925v2CI-20190529: 20190529
CI_DRM_11862:ffee806d103b9604db7eb9cd689c098aca1ffa96@git://anongit.freedesktop.org/gfx-ci/linuxIGT_6563:7d43b49bf10788d4870668f93a800888fc8ab339@ https://gitlab.freedesktop.org/drm/igt-gpu-tools.gitPatchwork_105925v2:ffee806d103b9604db7eb9cd689c098aca1ffa96@git://anongit.freedesktop.org/gfx-ci/linuxpiglit_4509:fdc5a4ca11124ab8413c7988896eec4c97336694@git://anongit.freedesktop.org/piglit