(In reply to comment #139)
> Oh that's interesting. We might be able to find a register to prevent rc6
> whilst waiting on a semaphore. (Hmm, too bad it isn't ivb or we could just
> frob forcewake directly.)
Happy to test patches. I'm updating to 3.13.9 tonight. I could add
something on top if y
My stuck ring faults are completely gone with i915.i915_enable_rc6=0.
Fan stays on a bit more (subjectively) seems to be the only side effect.
HP Pavilion dv6 (Sandybridge).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://
(In reply to comment #139)
> Oh that's interesting. We might be able to find a register to prevent rc6
> whilst waiting on a semaphore. (Hmm, too bad it isn't ivb or we could just
> frob forcewake directly.)
Happy to test patches. I'm updating to 3.13.9 tonight. I could add
something on top if y
My stuck ring faults are completely gone with i915.i915_enable_rc6=0.
Fan stays on a bit more (subjectively) seems to be the only side effect.
HP Pavilion dv6 (Sandybridge).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel
For what its worth, running 3.13.7 greatly mitigates this bug, to where
the dead time is barely noticeable. It happened three times in short
order here and I didn't notice any of them:
[ 4562.551141] [drm:ring_stuck] *ERROR* Kicking stuck semaphore on render ring
[ 4582.530028] [drm:ring_stuck] *
For what its worth, running 3.13.7 greatly mitigates this bug, to where
the dead time is barely noticeable. It happened three times in short
order here and I didn't notice any of them:
[ 4562.551141] [drm:ring_stuck] *ERROR* Kicking stuck semaphore on render ring
[ 4582.530028] [drm:ring_stuck] *
6 matches
Mail list logo
