Comment 23 for bug 1243261

Revision history for this message
In , Freaky (freaky) wrote :

Hi,

sorry it took a bit longer - I'm quite sick at the moment.

Anyways - things seem to become worse. I'm running the latest GIT version now: 2.99.906-21-gb14228f and whilst XBMC already didn't log any errors (not with 906, 905, etc. either) mplayer did output errors earlier.

It does no longer.

However, the issue itself hasn't changed. Although I must say I had it working properly with 906 once. Think it was a timing thing. Turned on the PC first and the television somewhat later. It might have to do with the time the television came 'online'. Haven't been able to reproduce it, having the television on before powering on the computer or after always results in the same now, about 1 frame every 5-6 secs.

I'd provide logs - but nothing is outputted anymore thus. I'll provide the dump I caught when it was still on 905.

Nov 4 20:56:07 www kernel: [ 58.732555] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring
Nov 4 20:56:11 www kernel: [ 62.734225] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring
Nov 4 20:56:18 www kernel: [ 69.741146] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring
Nov 4 20:56:22 www kernel: [ 73.738820] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring
Nov 4 20:56:26 www kernel: [ 77.740491] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring
Nov 4 20:56:30 www kernel: [ 81.742158] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring
Nov 4 20:56:34 www kernel: [ 85.743838] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring
Nov 4 20:56:42 www kernel: [ 93.747174] [drm:ring_stuck] *ERROR* Kicking stuck wait on render ring
Nov 4 20:56:42 www kernel: [ 93.747190] [drm:i915_hangcheck_elapsed] *ERROR* no progress on render ring
Nov 4 20:56:42 www kernel: [ 93.747195] [drm] capturing error event; look for more information in /sys/kernel/debug/dri/0/i915_error_state
Nov 4 20:56:42 www kernel: [ 93.768363] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x898000 ctx 0) at 0x89802c