All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3] drm/i915: Add Guc/HuC firmware details to error state
Date: Fri, 20 Oct 2017 13:57:52 +0100	[thread overview]
Message-ID: <150850427204.29194.6877198306721417070@mail.alporthouse.com> (raw)
In-Reply-To: <op.y8eq99bqxaggs7@mwajdecz-mobl1.ger.corp.intel.com>

Quoting Michal Wajdeczko (2017-10-20 13:50:23)
> On Fri, 20 Oct 2017 14:43:46 +0200, Chris Wilson  
> <chris@chris-wilson.co.uk> wrote:
> > Heh, I would just go back and make sure we had a clear well of deducing
> > when fw was being utilised. Maybe
> >
> >       if (uc_fw.load_status != INTEL_UC_FIRMWARE_NONE)
> >
> 
> If we don't care about earlier fw fetch attempts/errors, then ok.

Just since the last reset is about all we aim for. It's a game of trying
to work out what information will be required to debug future hangs. Too
much and it's a needle-in-a-haystack-problem, too little and we have the
round-trip latency in getting a new kernel to where the problem is seen.
And then for the next few years being frustrated at seeing hangs with the
old error state.

I defer what information is required for debugging in the future to
those already attempting it; but I do know that recording what firmware
and what status we left the uc in will always be useful. :)
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-10-20 12:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19 20:23 [PATCH v3] drm/i915: Add Guc/HuC firmware details to error state Michal Wajdeczko
2017-10-19 20:47 ` ✗ Fi.CI.BAT: failure for drm/i915: Add Guc/HuC firmware details to error state (rev3) Patchwork
2017-10-20  9:41 ` [PATCH v3] drm/i915: Add Guc/HuC firmware details to error state Joonas Lahtinen
2017-10-20 11:44   ` Chris Wilson
2017-10-20 12:14     ` Michal Wajdeczko
2017-10-20 12:21       ` Chris Wilson
2017-10-20 12:36         ` Michal Wajdeczko
2017-10-20 12:43           ` Chris Wilson
2017-10-20 12:50             ` Michal Wajdeczko
2017-10-20 12:57               ` Chris Wilson [this message]
2017-10-20 14:44   ` Michal Wajdeczko
2017-10-20 14:50     ` Chris Wilson
2017-10-20 14:59       ` Michal Wajdeczko
2017-10-20 15:14         ` Chris Wilson

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=150850427204.29194.6877198306721417070@mail.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=michal.wajdeczko@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.