On Sat, 2017-08-26 at 12:09 +0100, Chris Wilson wrote: > When we do a locked idle we know that afterwards all requests have been > completed and the engines have been cleared of tasks. For whatever > reason, this doesn't always happen and we may go into a suspend with > ELSP still full, and this causes an issue upon resume as we get very, > very confused. > > If the engines refuse to idle, mark the device as wedged. In the process > we get rid of the maybe unused open-coded version of wait_for_engines > reported by Nick Desaulniers and Matthias Kaehlcke. > > References: https://bugs.freedesktop.org/show_bug.cgi?id=101891 > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> > Cc: Mika Kuoppala <mika.kuoppala@xxxxxxxxxxxxxxx> > Cc: Joonas Lahtinen <joonas.lahtinen@xxxxxxxxxxxxxxx> > Cc: Matthias Kaehlcke <mka@xxxxxxxxxxxx> I assume GEM_WARN_ON -> DRM_ERROR was intentional. Reviewed-by: Joonas Lahtinen <joonas.lahtinen@xxxxxxxxxxxxxxx> Regards, Joonas -- Joonas Lahtinen Open Source Technology Center Intel Corporation _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
