From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Matthew Auld <matthew.william.auld@gmail.com>
Cc: Intel Graphics Development <Intel-gfx@lists.freedesktop.org>,
ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Skip error capture when wedged on init
Date: Wed, 10 Nov 2021 11:34:27 +0000 [thread overview]
Message-ID: <42489a16-292d-7ba3-64e6-de79dfa3dfb4@linux.intel.com> (raw)
In-Reply-To: <CAM0jSHOyj3ydgn-bZwk69RfpZLcG03Td_kxowEoJ1fg5PO=W3A@mail.gmail.com>
On 10/11/2021 10:48, Matthew Auld wrote:
> On Tue, 9 Nov 2021 at 12:20, Tvrtko Ursulin
> <tvrtko.ursulin@linux.intel.com> wrote:
>>
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> Trying to capture uninitialised engines when we wedged on init ends in
>> tears. Skip that together with uC capture, since failure to initialise the
>> latter can actually be one of the reasons for wedging on init.
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> This fixes the issue with missing GuC wedging the GPU and then blowing
> up when trying to use the driver?
Probably does not blow up when using the driver, but definitely does
when accessing error state. Someone suggested it would instead be better
to call i915_disable_error_state from wedge on init/fini, and I think
indeed it would, so I plan to send v2 looking like that.
Regards,
Tvrtko
> Reviewed-by: Matthew Auld <matthew.auld@intel.com>
>
>> ---
>> drivers/gpu/drm/i915/i915_gpu_error.c | 10 +++++++---
>> 1 file changed, 7 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c b/drivers/gpu/drm/i915/i915_gpu_error.c
>> index 2a2d7643b551..aa2b3aad9643 100644
>> --- a/drivers/gpu/drm/i915/i915_gpu_error.c
>> +++ b/drivers/gpu/drm/i915/i915_gpu_error.c
>> @@ -1866,10 +1866,14 @@ i915_gpu_coredump(struct intel_gt *gt, intel_engine_mask_t engine_mask)
>> }
>>
>> gt_record_info(error->gt);
>> - gt_record_engines(error->gt, engine_mask, compress);
>>
>> - if (INTEL_INFO(i915)->has_gt_uc)
>> - error->gt->uc = gt_record_uc(error->gt, compress);
>> + if (!intel_gt_has_unrecoverable_error(gt)) {
>> + gt_record_engines(error->gt, engine_mask, compress);
>> +
>> + if (INTEL_INFO(i915)->has_gt_uc)
>> + error->gt->uc = gt_record_uc(error->gt,
>> + compress);
>> + }
>>
>> i915_vma_capture_finish(error->gt, compress);
>>
>> --
>> 2.30.2
>>
prev parent reply other threads:[~2021-11-10 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 12:20 [Intel-gfx] [PATCH] drm/i915: Skip error capture when wedged on init Tvrtko Ursulin
2021-11-09 14:39 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2021-11-10 10:48 ` [Intel-gfx] [PATCH] " Matthew Auld
2021-11-10 11:34 ` Tvrtko Ursulin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42489a16-292d-7ba3-64e6-de79dfa3dfb4@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=matthew.william.auld@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox