Quoting Chris Wilson (2017-08-21 15:55:34)
> Quoting Michel Thierry (2017-08-18 18:23:42)
> > The corruption in CSB mmio reads we were seeing has been tracked down to
> > incorrectly touching forcewake of all domains, following an engine reset.
> > It is still a mistery why we only catched this in Broxton, since it
> > could happen in any platform.
> >
> > With that fix already merged, commit 4055dc75d6b5 ("drm/i915: Stop
> > touching forcewake following a gen6+ engine reset"), lets try to enable
> > per-engine resets in Broxton one more time.
> >
> > This reverts commit f188258bde0f ("drm/i915: Disable per-engine reset for
> > Broxton").
> >
> > Cc: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>
> > Signed-off-by: Michel Thierry <michel.thierry@xxxxxxxxx>
>
> My bxt has survived about 72 hours of hang testing, which is far more
> than it was able to previously.
>
> Acked-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>
> Tested-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>
Uh oh, seemingly just hit it again...
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
