drm/i915/guc: Check for ct enabled while waiting for response
Subsystems (2)
PATCH 1/1 drm/i915/guc: Check for ct enabled while waiting for response
We are seeing error message of "No response for request". Some cases happened while waiting for response and reset/suspend action was triggered. In this case, no response is not an error, active requests will be cancelled.
This patch will handle this condition and change the error message into debug message.
--- drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 24 ++++++++++++++++------- 1 file changed, 17 insertions(+), 7 deletions(-)
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c +17 -7
@@ -455,6 +455,7 @@ static int ct_write(struct intel_guc_ct *ct,/** * wait_for_ct_request_update - Wait for CT request state update. +* @ct: pointer to CT * @req: pointer to pending request * @status: placeholder for status *
@@ -467,9 +468,10 @@ static int ct_write(struct intel_guc_ct *ct,* * 0 response received (status is valid) * * -ETIMEDOUT no response within hardcoded timeout */ -static int wait_for_ct_request_update (struct ct_request *req,u32 *status) +static int wait_for_ct_request_update (struct intel_guc_ct *ct,struct ct_request *req,u32 *status) {int err; +bool ct_enabled;/* * Fast commands should complete in less than 10us, so sample quickly
@@ -481,12 +483,15 @@ static int wait_for_ct_request_update(struct ct_request *req, u32 *status)#define GUC_CTB_RESPONSE_TIMEOUT_SHORT_MS 10#define GUC_CTB_RESPONSE_TIMEOUT_LONG_MS 1000#define done \ - (FIELD_GET(GUC_HXG_MSG_0_ORIGIN, READ_ONCE(req->status)) == \ + (!(ct_enabled = intel_guc_ct_enabled(ct)) || \ + FIELD_GET(GUC_HXG_MSG_0_ORIGIN, READ_ONCE(req->status)) == \ GUC_HXG_ORIGIN_GUC) err =wait_for_us (done,GUC_CTB_RESPONSE_TIMEOUT_SHORT_MS );if (err) err =wait_for (done,GUC_CTB_RESPONSE_TIMEOUT_LONG_MS );#undef done +if (!ct_enabled) + err = -ECANCELED ; *status = req->status;return err;
@@ -703,11 +708,15 @@ static int ct_send(struct intel_guc_ct *ct,intel_guc_notify (ct_to_guc (ct)); - err =wait_for_ct_request_update (&request, status); + err =wait_for_ct_request_update (ct, &request, status);g2h_release_space (ct,GUC_CTB_HXG_MSG_MAX_LEN );if (unlikely (err)) { -CT_ERROR (ct,"No response for request %#x (fence %u)\n" , - action[0 ], request.fence); +if (err == -ECANCELED ) +CT_DEBUG (ct,"Request %#x (fence %u) cancelled as CTB is disabled\n" , + action[0 ], request.fence); +else +CT_ERROR (ct,"No response for request %#x (fence %u)\n" , + action[0 ], request.fence); goto unlink; }
@@ -771,8 +780,9 @@ int intel_guc_ct_send(struct intel_guc_ct *ct, const u32 *action, u32 len, ret =ct_send (ct, action, len, response_buf, response_buf_size, &status);if (unlikely (ret <0 )) { -CT_ERROR (ct,"Sending action %#x failed (%pe) status=%#X\n" , - action[0 ],ERR_PTR (ret), status); +if (ret != -ECANCELED ) +CT_ERROR (ct,"Sending action %#x failed (%pe) status=%#X\n" , + action[0 ],ERR_PTR (ret), status); }else if (unlikely (ret)) {CT_DEBUG (ct,"send action %#x returned %d (%#x)\n" , action[0 ], ret, ret);
Signature · 1 line
2.36.0
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/guc: Check for ct enabled while waiting for response
== Series Details ==
== Series Details ==
Series: drm/i915/guc: Check for ct enabled while waiting for response
URL : https://patchwork.freedesktop.org/series/105258/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11773 -> Patchwork_105258v1
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/index.html
Participating hosts (35 -> 34)
------------------------------
Missing (1): fi-bdw-samus
Known issues
------------
Here are the changes found in Patchwork_105258v1 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live@gem:
- fi-blb-e6850: NOTRUN -> [DMESG-FAIL][1] ([i915#4528])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/fi-blb-e6850/igt@i915_selftest@[email protected]
- fi-pnv-d510: NOTRUN -> [DMESG-FAIL][2] ([i915#4528])
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/fi-pnv-d510/igt@i915_selftest@[email protected]
* igt@kms_flip@basic-flip-vs-wf_vblank@a-edp1:
- fi-tgl-u2: [PASS][3] -> [DMESG-WARN][4] ([i915#402]) +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/fi-tgl-u2/igt@kms_flip@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/fi-tgl-u2/igt@kms_flip@[email protected]
#### Possible fixes ####
* igt@i915_selftest@live@gt_lrc:
- fi-bsw-n3050: [DMESG-FAIL][5] ([i915#2373]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/fi-bsw-n3050/igt@i915_selftest@live@gt_lrc.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/fi-bsw-n3050/igt@i915_selftest@live@gt_lrc.html
* igt@i915_selftest@live@requests:
- fi-blb-e6850: [DMESG-FAIL][7] ([i915#4528]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/fi-blb-e6850/igt@i915_selftest@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/fi-blb-e6850/igt@i915_selftest@[email protected]
- fi-pnv-d510: [DMESG-FAIL][9] ([i915#4528]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/fi-pnv-d510/igt@i915_selftest@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/fi-pnv-d510/igt@i915_selftest@[email protected]
* igt@kms_flip@basic-flip-vs-modeset@a-edp1:
- fi-tgl-u2: [DMESG-WARN][11] ([i915#402]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/fi-tgl-u2/igt@kms_flip@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/fi-tgl-u2/igt@kms_flip@[email protected]
[i915#2373]: https://gitlab.freedesktop.org/drm/intel/issues/2373
[i915#402]: https://gitlab.freedesktop.org/drm/intel/issues/402
[i915#4528]: https://gitlab.freedesktop.org/drm/intel/issues/4528
Build changes
-------------
* Linux: CI_DRM_11773 -> Patchwork_105258v1
CI-20190529: 20190529
CI_DRM_11773: 8025a295b7aa707f64c7984b7781c6f25e22a901 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6533: 6b5107d91827962808441db6b98e478aa9e67bdb @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_105258v1: 8025a295b7aa707f64c7984b7781c6f25e22a901 @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
746f27f6bf8f drm/i915/guc: Check for ct enabled while waiting for response
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/index.html
Quoted 8 lines · Zhanjun Dong
We are seeing error message of "No response for request". Some cases happened while waiting for response and reset/suspend action was triggered. In this case, no response is not an error, active requests will be cancelled.
This patch will handle this condition and change the error message into debug message.
The convention we follow in drm is to record the version of the patch and what changed in that version.
Generally I am ok with this version of the patch but still have a couple of questions.
Quoted 12 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c +1
-1-static int wait_for_ct_request_update (struct ct_request *req,u32 *status) +static int wait_for_ct_request_update (struct intel_guc_ct *ct,struct ct_request *req,u32 *status) {int err;drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c +1
-0+bool ct_enabled;/* * Fast commands should complete in less than 10us, so sample quicklydrivers/gpu/drm/i915/gt/uc/intel_guc_ct.c +0
-0@@ -481,12 +483,15 @@ static int wait_for_ct_request_update(struct ct_request *req, u32 *status)#define GUC_CTB_RESPONSE_TIMEOUT_SHORT_MS 10#define GUC_CTB_RESPONSE_TIMEOUT_LONG_MS 1000#define done \
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c static int wait_for_ct_request_update(struct ct_request *req, u32 *status) · line 494
Quoted 10 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c +4
-1- (FIELD_GET (GUC_HXG_MSG_0_ORIGIN ,READ_ONCE (req->status)) == \ + (!(ct_enabled =intel_guc_ct_enabled (ct)) || \ +FIELD_GET (GUC_HXG_MSG_0_ORIGIN ,READ_ONCE (req->status)) == \GUC_HXG_ORIGIN_GUC ) err = wait_for_us(done, GUC_CTB_RESPONSE_TIMEOUT_SHORT_MS);if (err) err =wait_for (done,GUC_CTB_RESPONSE_TIMEOUT_LONG_MS );#undef done +if (!ct_enabled) + err = -ECANCELED ;
So we have the choice of either setting the request status here as I was suggesting earlier, e.g. as follows:
#define GUC_HXG_TYPE_REQUEST_CANCELED 4u // unused value if (!ct_enabled) req->status = GUC_HXG_TYPE_REQUEST_CANCELED;
We would return 0 in this case and would check for the req->status value above where needed.
Or we can return -ECANCELED. I don't know if -ECANCELED is the right value to return but whatever we return will have to be unique (ununsed elsewhere) since we are relying on the return value. -ECANCELED is unique so that part is ok.
Do other reviewers have a preference whether we should set req->status or return a unique return value?
Quoted 22 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c +7
-3*status = req->status;return err;@@ -703,11 +708,15 @@ static int ct_send(struct intel_guc_ct *ct,intel_guc_notify (ct_to_guc (ct)); - err =wait_for_ct_request_update (&request, status); + err =wait_for_ct_request_update (ct, &request, status);g2h_release_space (ct,GUC_CTB_HXG_MSG_MAX_LEN );if (unlikely (err)) { -CT_ERROR (ct,"No response for request %#x (fence %u)\n" , - action[0 ], request.fence); +if (err == -ECANCELED ) +CT_DEBUG (ct,"Request %#x (fence %u) cancelled as CTB is disabled\n" , + action[0 ], request.fence); +else +CT_ERROR (ct,"No response for request %#x (fence %u)\n" , + action[0 ], request.fence); goto unlink; }
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c int intel_guc_ct_send(struct intel_guc_ct *ct, const u32 *action, u32 len, · line 785
Quoted 8 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c +3
-2@@ -771,8 +780,9 @@ int intel_guc_ct_send(struct intel_guc_ct *ct, const u32 *action, u32 len, ret =ct_send (ct, action, len, response_buf, response_buf_size, &status);if (unlikely (ret <0 )) { -CT_ERROR (ct,"Sending action %#x failed (%pe) status=%#X\n" , - action[0 ],ERR_PTR (ret), status); +if (ret != -ECANCELED ) +CT_ERROR (ct,"Sending action %#x failed (%pe) status=%#X\n" , + action[0 ],ERR_PTR (ret), status);
I am wondering why we even have this print and should we just delete it or convert it to CT_DEBUG(). The reason is that only error prints closest to where the actual error occurs are useful since they pin-point the error clearly. This to be seems to be a "second" print from a higher level function which does not seem particularly useful.
Quoted 6 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c +0
-1}else if (unlikely (ret)) {CT_DEBUG (ct,"send action %#x returned %d (%#x)\n" , action[0 ], ret, ret); --2.36.0
Quoted 42 lines · Zhanjun Dong
We are seeing error message of "No response for request". Some cases happened while waiting for response and reset/suspend action was triggered. In this case, no response is not an error, active requests will be cancelled.
This patch will handle this condition and change the error message into debug message.
Signed-off-by Zhanjun Dong <[email protected]>--- drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 24 ++++++++++++++++------- 1 file changed, 17 insertions(+), 7 deletions(-)drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c +3
-1@@ -455,6 +455,7 @@ static int ct_write(struct intel_guc_ct *ct,/** * wait_for_ct_request_update - Wait for CT request state update. +* @ct: pointer to CT * @req: pointer to pending request * @status: placeholder for status * @@ -467,9 +468,10 @@ static int ct_write(struct intel_guc_ct *ct,* * 0 response received (status is valid) * * -ETIMEDOUT no response within hardcoded timeout */ -static int wait_for_ct_request_update (struct ct_request *req,u32 *status) +static int wait_for_ct_request_update (struct intel_guc_ct *ct,struct ct_request *req,u32 *status) {int err; +bool ct_enabled;/* * Fast commands should complete in less than 10us, so sample quickly @@ -481,12 +483,15 @@ static int wait_for_ct_request_update(struct ct_request *req, u32 *status)#define GUC_CTB_RESPONSE_TIMEOUT_SHORT_MS 10#define GUC_CTB_RESPONSE_TIMEOUT_LONG_MS 1000#define done \
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c static int wait_for_ct_request_update(struct ct_request *req, u32 *status) · line 494
Quoted 10 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c +4
-1- (FIELD_GET (GUC_HXG_MSG_0_ORIGIN ,READ_ONCE (req->status)) == \ + (!(ct_enabled =intel_guc_ct_enabled (ct)) || \ +FIELD_GET (GUC_HXG_MSG_0_ORIGIN ,READ_ONCE (req->status)) == \GUC_HXG_ORIGIN_GUC ) err = wait_for_us(done, GUC_CTB_RESPONSE_TIMEOUT_SHORT_MS);if (err) err =wait_for (done,GUC_CTB_RESPONSE_TIMEOUT_LONG_MS );#undef done +if (!ct_enabled) + err = -ECANCELED ;
Actually here's an even simpler suggestion. We could just do:
if (!ct_enabled) CT_DEBUG(ct, "Request %#x (fence %u) cancelled as CTB is disabled\n", ...);
And return 0 as before. This way we won't have to make any changes in either ct_send() or intel_guc_ct_send(). So intel_guc_ct_enabled() just serves to get us out of the wait early and prevent the -ETIMEDOUT return (and 0 return avoids all the error messages we are trying to eliminate).
Quoted 57 lines · Ashutosh
Quoted 42 lines · Zhanjun Dong
We are seeing error message of "No response for request". Some cases happened while waiting for response and reset/suspend action was triggered. In this case, no response is not an error, active requests will be cancelled.
This patch will handle this condition and change the error message into debug message.
Signed-off-by Zhanjun Dong <[email protected]>--- drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 24 ++++++++++++++++------- 1 file changed, 17 insertions(+), 7 deletions(-)drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c +3
-1@@ -455,6 +455,7 @@ static int ct_write(struct intel_guc_ct *ct,/** * wait_for_ct_request_update - Wait for CT request state update. +* @ct: pointer to CT * @req: pointer to pending request * @status: placeholder for status * @@ -467,9 +468,10 @@ static int ct_write(struct intel_guc_ct *ct,* * 0 response received (status is valid) * * -ETIMEDOUT no response within hardcoded timeout */ -static int wait_for_ct_request_update (struct ct_request *req,u32 *status) +static int wait_for_ct_request_update (struct intel_guc_ct *ct,struct ct_request *req,u32 *status) {int err; +bool ct_enabled;/* * Fast commands should complete in less than 10us, so sample quickly @@ -481,12 +483,15 @@ static int wait_for_ct_request_update(struct ct_request *req, u32 *status)#define GUC_CTB_RESPONSE_TIMEOUT_SHORT_MS 10#define GUC_CTB_RESPONSE_TIMEOUT_LONG_MS 1000#define done \drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c static int wait_for_ct_request_update(struct ct_request *req, u32 *status) · line 494
Quoted 10 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c +4
-1- (FIELD_GET (GUC_HXG_MSG_0_ORIGIN ,READ_ONCE (req->status)) == \ + (!(ct_enabled =intel_guc_ct_enabled (ct)) || \ +FIELD_GET (GUC_HXG_MSG_0_ORIGIN ,READ_ONCE (req->status)) == \GUC_HXG_ORIGIN_GUC ) err = wait_for_us(done, GUC_CTB_RESPONSE_TIMEOUT_SHORT_MS);if (err) err =wait_for (done,GUC_CTB_RESPONSE_TIMEOUT_LONG_MS );#undef done +if (!ct_enabled) + err = -ECANCELED ;Actually here's an even simpler suggestion. We could just do:
Quoted 7 lines
if (!ct_enabled) CT_DEBUG(ct, "Request %#x (fence %u) cancelled as CTB is disabled\n", ...);And return 0 as before. This way we won't have to make any changes in either
ct_send()orintel_guc_ct_send(). Sointel_guc_ct_enabled()just serves to get us out of the wait early and prevent the-ETIMEDOUTreturn (and 0 return avoids all the error messages we are trying to eliminate).
Actually will need to unlink the request too, so it will be something like:
if (!ct_enabled) {
CT_DEBUG(ct, "Request %#x (fence %u) cancelled as CTB is disabled\n", ...);
spin_lock_irqsave(&ct->requests.lock, flags);
list_del(&request.link);
spin_unlock_irqrestore(&ct->requests.lock, flags);
}Quoted 90 lines
-----Original Message-----
From: Dixit, Ashutosh <[email protected]>
Sent: July 12, 2022 3:48 PM
To: Dong, Zhanjun <[email protected]>
Cc: [email protected]; [email protected]
Subject: Re: [Intel-gfx] [PATCH] drm/i915/guc: Check for ct enabled while waiting for responseQuoted 5 lines · Ashutosh
Quoted 3 lines · Zhanjun Dong
We are seeing error message of "No response for request". Some cases happened while waiting for response and reset/suspend action was
triggered.
Quoted 37 lines
Quoted 37 lines
In this case, no response is not an error, active requests will be cancelled.
This patch will handle this condition and change the error message into debug message.
Signed-off-by Zhanjun Dong <[email protected]>--- drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c | 24 ++++++++++++++++------- 1 file changed, 17 insertions(+), 7 deletions(-)drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c +4
-1@@ -455,6 +455,7 @@ static int ct_write(struct intel_guc_ct *ct,/** * wait_for_ct_request_update - Wait for CT request state update. +* @ct: pointer to CT * @req: pointer to pending request * @status: placeholder for status * @@ -467,9 +468,10 @@ static int ct_write(struct intel_guc_ct *ct,* * 0 response received (status is valid) * * -ETIMEDOUT no response within hardcoded timeout */ -static int wait_for_ct_request_update (struct ct_request *req,u32 *status) +static int wait_for_ct_request_update (struct intel_guc_ct *ct, +struct ct_request *req,u32 *status) {int err; +bool ct_enabled;Quoted 8 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c
Quoted 8 lines
/* * Fast commands should complete in less than 10us, so samplequickly @@ -481,12 +483,15 @@ static int
wait_for_ct_request_update(struct ct_request *req, u32 *status)
#defineGUC_CTB_RESPONSE_TIMEOUT_SHORT_MS10
#defineGUC_CTB_RESPONSE_TIMEOUT_LONG_MS1000 #define done \drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c +0
-1- (FIELD_GET(GUC_HXG_MSG_0_ORIGIN, READ_ONCE(req->status)) ==\
Quoted 2 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c
Quoted 2 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c +2
-0+ (!(ct_enabled =intel_guc_ct_enabled (ct)) || \ + FIELD_GET(GUC_HXG_MSG_0_ORIGIN, READ_ONCE(req->status)) ==\
Quoted 4 lines
Quoted 4 lines
GUC_HXG_ORIGIN_GUC) err = wait_for_us(done, GUC_CTB_RESPONSE_TIMEOUT_SHORT_MS); if (err) err = wait_for(done,
GUC_CTB_RESPONSE_TIMEOUT_LONG_MS);Quoted 8 lines
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c static int wait_for_ct_request_update(struct ct_request *req, u32 *status) · line 494
Quoted 3 lines
#undef done
drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c +2
-0+if (!ct_enabled) + err = -ECANCELED ;Actually here's an even simpler suggestion. We could just do:
if (!ct_enabled)
CT_DEBUG(ct, "Request %#x (fence %u) cancelled as CTB isdisabled\n",
Quoted 6 lines
...);
And return 0 as before. This way we won't have to make any changes in either
ct_send()orintel_guc_ct_send(). Sointel_guc_ct_enabled()just serves to get us out of the wait early and prevent the-ETIMEDOUTreturn (and 0 return avoids all the error messages we are trying toeliminate).
Actually will need to unlink the request too, so it will be something like:
Quoted 8 lines
if (!ct_enabled) { CT_DEBUG(ct, "Request %#x (fence %u) cancelled as CTB isdisabled\n", ...);
spin_lock_irqsave(&ct->requests.lock, flags); list_del(&request.link); spin_unlock_irqrestore(&ct->requests.lock, flags); }
I agree, the caller function need the err is non-zero to know the request is not success, and unlink the request. The caller function ct_send will do the unlink.
For the err code ECANCELED, while in intel_guc_ct_send, it returns ENODEV if ct is disabled. This patch will be changed to ENODEV to match it.
Patchwork
CI[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/guc: Check for ct enabled while waiting for response
In reply to Zhanjun Dong== Series Details ==
== Series Details ==
Series: drm/i915/guc: Check for ct enabled while waiting for response
URL : https://patchwork.freedesktop.org/series/105258/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11773_full -> Patchwork_105258v1_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Participating hosts (10 -> 10)
------------------------------
No changes in participating hosts
Known issues
------------
Here are the changes found in Patchwork_105258v1_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_eio@in-flight-10ms:
- shard-tglb: [PASS][1] -> [TIMEOUT][2] ([i915#3063]) +1 similar issue
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-tglb3/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-tglb8/igt@[email protected]
* igt@gem_eio@in-flight-contexts-1us:
- shard-snb: [PASS][3] -> [FAIL][4] ([i915#4409])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-snb5/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-snb5/igt@[email protected]
* igt@gem_exec_balancer@parallel-bb-first:
- shard-iclb: [PASS][5] -> [SKIP][6] ([i915#4525])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-iclb2/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-iclb5/igt@[email protected]
* igt@gem_exec_fair@basic-flow@rcs0:
- shard-tglb: [PASS][7] -> [FAIL][8] ([i915#2842]) +1 similar issue
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-tglb3/igt@gem_exec_fair@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-tglb6/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none-share@rcs0:
- shard-iclb: [PASS][9] -> [FAIL][10] ([i915#2842])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-iclb8/igt@gem_exec_fair@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-iclb5/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-none@vecs0:
- shard-apl: [PASS][11] -> [FAIL][12] ([i915#2842])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-apl8/igt@gem_exec_fair@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-apl8/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-kbl: [PASS][13] -> [FAIL][14] ([i915#2842]) +1 similar issue
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-kbl3/igt@gem_exec_fair@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-kbl4/igt@gem_exec_fair@[email protected]
* igt@gem_exec_whisper@basic-queues-all:
- shard-glk: [PASS][15] -> [DMESG-WARN][16] ([i915#118])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-glk2/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-glk5/igt@[email protected]
* igt@i915_suspend@fence-restore-tiled2untiled:
- shard-apl: [PASS][17] -> [DMESG-WARN][18] ([i915#180])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-apl7/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-apl1/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-suspend:
- shard-kbl: [PASS][19] -> [DMESG-WARN][20] ([i915#180]) +2 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-kbl4/igt@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-kbl7/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-spr-indfb-draw-mmap-wc:
- shard-apl: NOTRUN -> [SKIP][21] ([fdo#109271]) +12 similar issues
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-apl6/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-spr-indfb-draw-mmap-wc.html
* igt@kms_pipe_crc_basic@nonblocking-crc-pipe-d-frame-sequence:
- shard-apl: NOTRUN -> [SKIP][22] ([fdo#109271] / [i915#533])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-apl6/igt@[email protected]
* igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-5@pipe-a-edp-1:
- shard-iclb: [PASS][23] -> [SKIP][24] ([i915#5235]) +2 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-iclb4/igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-5@pipe-a-edp-1.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-iclb2/igt@kms_plane_scaling@planes-upscale-factor-0-25-downscale-factor-0-5@pipe-a-edp-1.html
* igt@kms_psr@psr2_no_drrs:
- shard-iclb: [PASS][25] -> [SKIP][26] ([fdo#109441]) +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-iclb2/igt@kms_psr@psr2_no_drrs.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-iclb5/igt@kms_psr@psr2_no_drrs.html
* igt@kms_psr_stress_test@invalidate-primary-flip-overlay:
- shard-tglb: [PASS][27] -> [SKIP][28] ([i915#5519])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-tglb6/igt@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-tglb5/igt@[email protected]
* igt@sw_sync@sync_multi_timeline_wait:
- shard-apl: NOTRUN -> [FAIL][29] ([i915#6140])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-apl6/igt@sw_sync@sync_multi_timeline_wait.html
#### Possible fixes ####
* igt@gem_exec_balancer@parallel:
- shard-iclb: [SKIP][30] ([i915#4525]) -> [PASS][31]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-iclb6/igt@[email protected]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-iclb4/igt@[email protected]
* igt@gem_exec_fair@basic-none@vcs0:
- shard-kbl: [FAIL][32] ([i915#2842]) -> [PASS][33] +3 similar issues
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-kbl3/igt@gem_exec_fair@[email protected]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-kbl1/igt@gem_exec_fair@[email protected]
* igt@gem_huc_copy@huc-copy:
- shard-tglb: [SKIP][34] ([i915#2190]) -> [PASS][35]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-tglb6/igt@[email protected]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-tglb3/igt@[email protected]
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [FAIL][36] ([i915#454]) -> [PASS][37]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-iclb6/igt@[email protected]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-iclb4/igt@[email protected]
* igt@i915_pm_dc@dc9-dpms:
- shard-apl: [FAIL][38] ([i915#4275]) -> [PASS][39]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-apl4/igt@[email protected]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-apl3/igt@[email protected]
* igt@kms_cursor_legacy@cursor-vs-flip-legacy:
- shard-iclb: [DMESG-WARN][40] ([i915#1888]) -> [PASS][41]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-iclb1/igt@[email protected]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-iclb6/igt@[email protected]
* igt@kms_cursor_legacy@cursor-vs-flip-toggle:
- shard-iclb: [FAIL][42] ([i915#5072]) -> [PASS][43]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-iclb7/igt@[email protected]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-iclb8/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size:
- shard-glk: [FAIL][44] ([i915#2346] / [i915#533]) -> [PASS][45]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-glk4/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-glk1/igt@kms_cursor_legacy@flip-vs-cursor-atomic-transitions-varying-size.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs-upscaling:
- shard-glk: [FAIL][46] ([i915#4911]) -> [PASS][47]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-glk8/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs-upscaling.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-glk4/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytileccs-upscaling.html
* igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile-downscaling:
- shard-iclb: [SKIP][48] ([i915#3701]) -> [PASS][49] +2 similar issues
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile-downscaling.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-iclb1/igt@kms_flip_scaled_crc@flip-64bpp-ytile-to-16bpp-ytile-downscaling.html
* igt@kms_hdr@bpc-switch-dpms@pipe-a-dp-1:
- shard-kbl: [FAIL][50] ([i915#1188]) -> [PASS][51]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-kbl4/igt@kms_hdr@[email protected]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-kbl6/igt@kms_hdr@[email protected]
* igt@kms_hdr@bpc-switch-suspend@pipe-a-dp-1:
- shard-apl: [DMESG-WARN][52] ([i915#180]) -> [PASS][53] +3 similar issues
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-apl3/igt@kms_hdr@[email protected]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-apl8/igt@kms_hdr@[email protected]
* igt@kms_plane_scaling@planes-downscale-factor-0-5@pipe-a-edp-1:
- shard-iclb: [SKIP][54] ([i915#5235]) -> [PASS][55] +2 similar issues
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-iclb2/igt@kms_plane_scaling@[email protected]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-iclb1/igt@kms_plane_scaling@[email protected]
* igt@kms_psr@psr2_sprite_mmap_gtt:
- shard-iclb: [SKIP][56] ([fdo#109441]) -> [PASS][57] +2 similar issues
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-iclb4/igt@kms_psr@psr2_sprite_mmap_gtt.html
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-iclb2/igt@kms_psr@psr2_sprite_mmap_gtt.html
* igt@perf@polling-parameterized:
- shard-tglb: [FAIL][58] ([i915#5639]) -> [PASS][59]
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-tglb8/igt@[email protected]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-tglb8/igt@[email protected]
#### Warnings ####
* igt@gem_exec_balancer@parallel-ordering:
- shard-iclb: [FAIL][60] ([i915#6117]) -> [SKIP][61] ([i915#4525])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-iclb4/igt@[email protected]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-iclb3/igt@[email protected]
* igt@kms_psr2_sf@cursor-plane-move-continuous-exceed-sf:
- shard-iclb: [SKIP][62] ([i915#658]) -> [SKIP][63] ([i915#2920])
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-iclb4/igt@[email protected]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-iclb2/igt@[email protected]
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area:
- shard-iclb: [SKIP][64] ([i915#2920]) -> [SKIP][65] ([fdo#111068] / [i915#658])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-iclb2/igt@[email protected]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-iclb1/igt@[email protected]
* igt@kms_psr2_sf@primary-plane-update-sf-dmg-area-big-fb:
- shard-iclb: [SKIP][66] ([i915#2920]) -> [SKIP][67] ([i915#658]) +1 similar issue
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11773/shard-iclb2/igt@[email protected]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_105258v1/shard-iclb1/igt@[email protected]
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1888]: https://gitlab.freedesktop.org/drm/intel/issues/1888
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2920]: https://gitlab.freedesktop.org/drm/intel/issues/2920
[i915#3063]: https://gitlab.freedesktop.org/drm/intel/issues/3063
[i915#3701]: https://gitlab.freedesktop.org/drm/intel/issues/3701
[i915#4275]: https://gitlab.freedesktop.org/drm/intel/issues/4275
[i915#4409]: https://gitlab.freedesktop.org/drm/intel/issues/4409
[i915#4525]: https://gitlab.freedesktop.org/drm/intel/issues/4525
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#4911]: https://gitlab.freedesktop.org/drm/intel/issues/4911
[i915#5072]: https://gitlab.freedesktop.org/drm/intel/issues/5072
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5519]: https://gitlab.freedesktop.org/drm/intel/issues/5519
[i915#5639]: https://gitlab.freedesktop.org/drm/intel/issues/5639
[i915#6117]: https://gitlab.freedesktop.org/drm/intel/issues/6117
[i915#6140]: https://gitlab.freedesktop.org/drm/intel/issues/6140
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
Build changes
-------------
* Linux: CI_DRM_11773 -> Patchwork_105258v1
CI-20190529: 20190529
CI_DRM_11773: 8025a295b7aa707f64c7984b7781c6f25e22a901 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6533: 6b5107d91827962808441db6b98e478aa9e67bdb @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_105258v1: 8025a295b7aa707f64c7984b7781c6f25e22a901 @ 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_105258v1/index.html