From: Andi Shyti <andi.shyti@linux.intel.com>
To: Nirmoy Das <nirmoy.das@linux.intel.com>
Cc: Andi Shyti <andi.shyti@linux.intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
Nirmoy Das <nirmoy.das@intel.com>,
Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>,
Andi Shyti <andi.shyti@kernel.org>
Subject: Re: [PATCH 2/2] drm/i915: Don't treat FLR resets as errors
Date: Fri, 17 May 2024 21:34:32 +0200 [thread overview]
Message-ID: <ZkexSOO9MYt7Y9-8@ashyti-mobl2.lan> (raw)
In-Reply-To: <e2a23879-c69e-4b57-a0a0-4c1ac81d9403@linux.intel.com>
Hi Nirmoy,
On Fri, May 17, 2024 at 04:00:02PM +0200, Nirmoy Das wrote:
> On 5/17/2024 1:25 PM, Andi Shyti wrote:
> > If we timeout while waiting for an FLR reset, there is nothing we
> > can do and i915 doesn't have any control on it. In any case the
> > system is still perfectly usable
>
> If a FLR reset fails then we will have a dead GPU, I don't think the GPU is
> usable without a cold reboot.
fact is that the GPU keeps going and even though the timeout has
expired, the system moves to the next phase.
> This is a serious issue and should be report as an error. I think we need
> to create a HW ticket to understand
>
> why is FLR reset fails.
Maybe it takes longer and longer to reset. We've been sending
several patches in the latest years to fix the timings.
Andi
next prev parent reply other threads:[~2024-05-17 19:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 11:25 [PATCH 0/2] Don't be alarmed at FLR timeouts Andi Shyti
2024-05-17 11:25 ` [PATCH 1/2] drm/i915: Increase FLR timeout from 3s to 9s Andi Shyti
2024-05-17 11:25 ` [PATCH 2/2] drm/i915: Don't treat FLR resets as errors Andi Shyti
2024-05-17 14:00 ` Nirmoy Das
2024-05-17 19:34 ` Andi Shyti [this message]
2024-05-17 20:13 ` Nirmoy Das
2024-05-21 10:56 ` Andi Shyti
2024-05-22 9:07 ` Nirmoy Das
2024-05-17 12:45 ` ✓ Fi.CI.BAT: success for Don't be alarmed at FLR timeouts Patchwork
2024-05-17 17:53 ` ✗ Fi.CI.IGT: failure " Patchwork
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=ZkexSOO9MYt7Y9-8@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=janusz.krzysztofik@linux.intel.com \
--cc=nirmoy.das@intel.com \
--cc=nirmoy.das@linux.intel.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