On Tue, 19 Jun 2012 16:15:30 +0200, Daniel Vetter <[email protected]> wrote: > Now I still think that having unified hw frobbing paths between driver > load, resume and gpu reset is highly desirable, so I've opted to just > add a reset argument to disable the offending code for gpu resets. I > have no idea why it actually blows up.
Did you look at whether it was an IRQ firing during the reset may have been an issue? One of the patches I have is to disable interrupts across the hw reset during i915_reset(). Otherwise, bisect the register writes int the offending ironlake_enable_drps(). -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
