drm/i915/guc: Update log for unsolicited CTB response
Instead of printing message fence twice, include HXG header of the unexpected message and its len. Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com> Signed-off-by: John Harrison <John.C.Harrison@Intel.com> Reviewed-by: John Harrison <John.C.Harrison@Intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20230526235538.2230780-3-John.C.Harrison@Intel.com
This commit is contained in:
parent
edfd93e60b
commit
d9911020ca
@ -994,9 +994,8 @@ static int ct_handle_response(struct intel_guc_ct *ct, struct ct_incoming_msg *r
|
||||
break;
|
||||
}
|
||||
if (!found) {
|
||||
CT_ERROR(ct, "Unsolicited response (fence %u)\n", fence);
|
||||
CT_ERROR(ct, "Could not find fence=%u, last_fence=%u\n", fence,
|
||||
ct->requests.last_fence);
|
||||
CT_ERROR(ct, "Unsolicited response message: len %u, data %#x (fence %u, last %u)\n",
|
||||
len, hxg[0], fence, ct->requests.last_fence);
|
||||
list_for_each_entry(req, &ct->requests.pending, link)
|
||||
CT_ERROR(ct, "request %u awaits response\n",
|
||||
req->fence);
|
||||
|
Loading…
x
Reference in New Issue
Block a user