What version of mesa are you running? Could you update to 10.2 or later?

Le 09/08/2014 09:47, bugzilla-daemon@freedesktop.org a écrit :
>
> *Comment # 1 <https://bugs.freedesktop.org/show_bug.cgi?id=82379#c1> 
> on bug 82379 <https://bugs.freedesktop.org/show_bug.cgi?id=82379> from 
> Chris Wilson <mailto:chris@chris-wilson.co.uk> *
> What version of mesa are you running? Could you update to 10.2 or later?
> ------------------------------------------------------------------------
> You are receiving this mail because:
>
>   * You reported the bug.
>

Thank you for your reply.

$ dpkg -l |grep -i mesa
ii  libegl1-mesa:amd64           10.1.3-0ubuntu0.1  amd64
ii  libegl1-mesa-drivers:amd64   10.1.3-0ubuntu0.1  amd64
ii  libgl1-mesa-dri:amd64        10.1.3-0ubuntu0.1  amd64
ii  libgl1-mesa-glx:amd64        10.1.3-0ubuntu0.1  amd64
ii  libglapi-mesa:amd64          10.1.3-0ubuntu0.1  amd64
ii  libglu1-mesa:amd64           9.0.0-2            amd64
ii  libopenvg1-mesa:amd64        10.1.3-0ubuntu0.1  amd64
ii  libtxc-dxtn-s2tc0:amd64      0~git20131104-1.1  amd64
ii  libwayland-egl1-mesa:amd64   10.1.3-0ubuntu0.1  amd64
ii  mesa-utils                   8.1.0-2            amd64

I do not know how to update mesa but I can wait for a dist-upgrade as 
the bug is not too annoying.

Created attachment 104449 [details]
/sys/class/drm/card0/error

Mesa upgraded to version 10.3.0~git20140805.fc2b2d33-0ubuntu0sarvatt2~trusty.

Problem still present:

[drm] stuck on render ring
[drm] GPU crash dump saved to /sys/class/drm/card0/error
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0xc831000 ctx 0) at 0xc831754

Mesa: 10.3.0~git20140812.fa5b76e3-0ubuntu0ricotz~trusty
Linux hal 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13 15:45:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

/sys/class/drm/card0/error attached.

Bug much less frequent.

Created attachment 104661 [details]
/sys/class/drm/card0/error

Hmm, another one that would be useful to run with xf86-video-intel compiled with --enable-debug to rule out that component.

Arthur, any possibility of running a debug enabled DDX driver to collect more info?

Does it mean I have to build it from sources or can I download a ready-made one from somewhere?

*** Bug 89703 has been marked as a duplicate of this bug. ***

You can get a pretty recent build from the xorg-edgers ppa, but I don't know if it builds with --enable-debug.  Chris would probably know.

Similar issue on my system, all attempts to use i915 driver end in
"intel_do_flush_locked failed Input/Output error"
or silmilar

[  102.816080] [drm] stuck on render ring
[  102.822122] [drm] GPU HANG: ecode 2:0:0x43dfffc1, in Xorg [1793], reason: Ring hung, action: reset
[  102.822126] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[  102.822128] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[  102.822130] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[  102.822132] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[  102.822134] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[  102.829628] drm/i915: Resetting chip after gpu hang
[  102.829675] [drm:i915_reset [i915]] *ERROR* Failed to reset chip: -19


tvuser@TELEVISION:~$ intel_gpu_top
(intel_gpu_top:15914) intel-mmio-CRITICAL: Test assertion failure function intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:144:
Failed assertion: !(error != 0)
Last errno: 13, Permission denied
Couldn't map MMIO region
Stack trace:
  #0 [_init+0x6ae2]
  #1 [_init+0x4972]
  #2 [_init+0xf9f]
  #3 [__libc_start_main+0xde]
  #4 [_init+0x32c1]
Test (null) failed.
**** DEBUG ****
(intel_gpu_top:15914) intel-mmio-CRITICAL: Test assertion failure function intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:144:
Failed assertion: !(error != 0)
Last errno: 13, Permission denied
Couldn't map MMIO region
****  END  ****
FAIL (4259.318s)

==========================================
We seem to have neglected the bug a bit, apologies.

Arthur H. Fonzarelli , since There were improvements pushed in kernel & xf86-video-intel that will benefit to your system, so please re-test with latest kernel & xf86-video-intel -alternatively you may use modesetting/glamor with latest mesa version- and mark as REOPENED if you can reproduce (and attach fresh gpu error dump & kernel log) and RESOLVED/* if you cannot reproduce.

No problem with the same hardware now using Ubuntu 16.04.2 LTS (Linux hal 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux).

(In reply to Arthur H. Fonzarelli from comment #14)
> No problem with the same hardware now using Ubuntu 16.04.2 LTS (Linux hal
> 4.4.0-64-generic #85-Ubuntu SMP Mon Feb 20 11:50:30 UTC 2017 x86_64 x86_64
> x86_64 GNU/Linux).

Thanks Arthur for you feedback. Therefore closing this ticket.

Thanks Yann for your concern!