On Fri, Oct 20, 2017 at 03:20:22PM +0100, Chris Wilson wrote: > We only suppress the error state from the context, iff we triggering the > GPU reset by hangcheck (igt_hang_ring). If we trigger an immediate reset > via igt_force_gpu_reset(), we will populate the error-state but not free > it because we thought we have it suppressed by the context parameter. > Always eat the error after we expect a GPU reset, and have not specified > that we want to keep it. > > The side-effect of keeping the error-state around after we deliberately > created it is that subsequent GPU hangs are not prominently recorded, as > the kernel believes they are secondary hangs (and we only announce the > first). > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> Reviewed-by: Michał Winiarski <michal.winiarski@xxxxxxxxx> -Michał > --- > lib/igt_gt.c | 31 ++++++++++++++++--------------- > 1 file changed, 16 insertions(+), 15 deletions(-) _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
