Re: [PATCH RESEND v2] drm/i915/gt: Log reason for setting TAINT_WARN at reset

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxx>
> > 
> > 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@xxxxxxxxx>
> > Reviewed-by: Andi Shyti <andi.shyti@xxxxxxxxxxxxxxx>
> > Signed-off-by: Andi Shyti <andi.shyti@xxxxxxxxxxxxxxx>
> 
> 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



[Index of Archives]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux