From: Raag Jadav <raag.jadav@intel.com>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: Andi Shyti <andi.shyti@linux.intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Sebastian Brzezinka <sebastian.brzezinka@intel.com>
Subject: Re: [PATCH RESEND v2] drm/i915/gt: Log reason for setting TAINT_WARN at reset
Date: Tue, 24 Dec 2024 13:04:33 +0200 [thread overview]
Message-ID: <Z2qVQSiZ7ZmMS5kp@black.fi.intel.com> (raw)
In-Reply-To: <c66ibuhmcte6fu5vkdrl73icqts4yzlwlui4qolrlw5yaxxu6q@vqhtozsh5d46>
On Mon, Dec 23, 2024 at 08:18:46PM +0100, Andi Shyti wrote:
> Hi Sebastian,
>
> On Fri, Dec 20, 2024 at 02:17:14PM +0100, Andi Shyti wrote:
> > From: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
> >
> > TAINT_WARN is used to notify CI about non-recoverable failures, which
> > require device to be restarted. In some cases, there is no sufficient
> > information about the reason for the restart. The test runner is just
> > killed, and DUT is rebooted, logging only 'probe with driver i915 failed
> > with error -4' to dmesg.
> >
> > Printing error to dmesg before TAINT_WARN, would explain why the device
> > has been restarted, and what caused the malfunction in the first place.
> >
> > Signed-off-by: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
> > Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
> > Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com>
>
> it's hard to receive green lights from CI. Anyway, I merged it to
> drm-intel-gt-next since all the failures look completely
> unrelated.
Side note: You can trigger a re-run from patchwork without resend.
Raag
next prev parent reply other threads:[~2024-12-24 11:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 13:17 [PATCH RESEND v2] drm/i915/gt: Log reason for setting TAINT_WARN at reset Andi Shyti
2024-12-20 13:34 ` Rodrigo Vivi
2024-12-20 14:07 ` ✗ i915.CI.BAT: failure for " Patchwork
2024-12-20 21:16 ` ✗ i915.CI.BAT: failure for drm/i915/gt: Log reason for setting TAINT_WARN at reset (rev2) Patchwork
2024-12-20 22:08 ` ✗ i915.CI.BAT: failure for drm/i915/gt: Log reason for setting TAINT_WARN at reset (rev3) Patchwork
2024-12-21 0:18 ` ✓ i915.CI.BAT: success for drm/i915/gt: Log reason for setting TAINT_WARN at reset (rev4) Patchwork
2024-12-21 21:27 ` ✗ i915.CI.Full: failure " Patchwork
2024-12-23 19:18 ` [PATCH RESEND v2] drm/i915/gt: Log reason for setting TAINT_WARN at reset Andi Shyti
2024-12-24 11:04 ` Raag Jadav [this message]
2024-12-24 11:18 ` Raag Jadav
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=Z2qVQSiZ7ZmMS5kp@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=andi.shyti@kernel.org \
--cc=andi.shyti@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=sebastian.brzezinka@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