Am Saturday, 24. September 2011 schrieben Sie:
> On Fri, 23 Sep 2011 21:05:37 +0200, Rainer Dorsch wrote:
> > Are there any other data I could gather to figure out what is going
> > wrong?
>
> Oh, have we gotten register dumps from a working vs non-working resume?
>
> git://anongit.freed
v1:
Idle GPU before and after unmaps.
v2: (untested)
Read GMCH_CTRL to find if VT-d is enable
Pulled David's patch into the series
Only stall for unmaps
Add warning for list_empty && !rings_idle
Ben Widawsky (3):
drm/i915: add warning for unidle GPU
drm/i915: Ironlake mobile GPU with VT-d fix
When we attempt to idle the GPU we take a shortcut by checking if our
lists are empty and if so, avoid doing a synchronizing flush. The
warning will let us know if this assumption turns out to not be correct.
Cc: Chris Wilson
Signed-off-by: Ben Widawsky
---
drivers/gpu/drm/i915/i915_gem.c |
Under certain circumstances, an IOTLB flush never completes and the hardware
just locks up. The fix is meant to idle the GPU both before and after
any unmap occurs.
This patch also disables the warning which is meant to detect mismatches
between when we think the command parse and arbiter should
From: David Woodhouse
To work around a hardware issue, we have to submit IOTLB flushes while
the graphics engine is idle. The graphics driver will go to great
lengths to ensure that it gets that right on the affected chipset(s)...
so let's not screw it over by deferring the unmap and doing it lat
The warning really does belong there even though it is not part of the
workaround. Once we rootcause how our lists and HW get out of sync, this
patch should be sucked back in.
Cc: Chris Wilson
Signed-off-by: Ben Widawsky
---
drivers/gpu/drm/i915/i915_gem.c |2 +-
1 files changed, 1 insertio
Under certain circumstances, an IOTLB flush never completes and the hardware
just locks up. The fix is meant to idle the GPU both before and after
any unmap occurs.
This patch also disables the warning which is meant to detect mismatches
between when we think the command parse and arbiter should
On Fri, 23 Sep 2011 17:36:16 -0700
Ben Widawsky wrote:
> Clean the code up, and always use a BO when creating a new buffer.
> I've not seen any regressions but haven't yet tried this on < Gen6.
>
> Cc: Chad Versace
> Cc: Eric Anholt
> Cc: Mesa Devs
> Signed-off-by: Ben Widawsky
> ---
I scre
