From: Raag Jadav <raag.jadav@intel.com>
To: Alan Previn <alan.previn.teres.alexis@intel.com>
Cc: intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Matt Roper <matthew.d.roper@intel.com>,
Riana Tauro <riana.tauro@intel.com>
Subject: Re: [PATCH 1/1] drm/xe/survivability: broadcast dmesg when engaging survivability
Date: Wed, 28 Oct 2026 04:18:13 +0100 [thread overview]
Message-ID: <auFpdeRIafjgKSV9@black.igk.intel.com> (raw)
In-Reply-To: <20261023173625.601113-2-alan.previn.teres.alexis@intel.com>
On Fri, Oct 23, 2026 at 10:36:25AM -0700, Alan Previn wrote:
> Today, when the driver faces issues with early pcode errors
> and attempts to enter survivabilty (when explicitly requested)
> it may either succeed or fail (latter being possible due to
> underlying subsystem blockers). During this flow the driver remains
> loaded and completely silent. No messages indicate that it may need
> or it attempted and succeeded or it attempted and failed, to enter
> survivability mode. This patch adds some awareness in dmesg.
What case are you exactly hitting here? From what I understand both pcode
and survivability failures are logged inside their helpers.
Raag
next prev parent reply other threads:[~2026-10-28 3:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 17:36 [PATCH 1/1] drm/xe/survivability: broadcast dmesg when engaging survivability Alan Previn
2026-10-28 3:18 ` Raag Jadav [this message]
2026-10-28 21:01 ` Teres Alexis, Alan Previn
2026-10-29 4:48 ` Raag Jadav
2026-10-29 9:38 ` Tauro, Riana
2026-10-29 18:41 ` Teres Alexis, Alan Previn
2026-10-29 18:57 ` Teres Alexis, Alan Previn
-- strict thread matches above, loose matches on Subject: below --
2026-10-30 17:17 Alan Previn
2026-10-30 17:24 ` sashiko-bot
2026-10-23 0:18 Alan Previn
2026-10-23 0:27 ` sashiko-bot
2026-10-23 16:43 ` Teres Alexis, Alan Previn
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=auFpdeRIafjgKSV9@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=riana.tauro@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