[Bug 90686] New: stuck on render ring

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=90686

            Bug ID: 90686
           Summary: stuck on render ring
           Product: DRI
           Version: XOrg git
          Hardware: x86 (IA32)
                OS: Linux (All)
            Status: NEW
          Severity: blocker
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: mathias.aldrin at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 116094
  --> https://bugs.freedesktop.org/attachment.cgi?id=116094&action=edit
card0

Just instaled Linux Mint 17.1 and updated all packages.
After this I tried to do some work but mouse pointer freezes.
Looking in syslog I found the following:

May 27 20:28:36 fujitsu pulseaudio[2321]: [pulseaudio] pid.c: Daemon already
running.
May 27 20:30:39 fujitsu kernel: [  169.808065] [drm] stuck on render ring
May 27 20:30:39 fujitsu kernel: [  169.808077] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
May 27 20:30:39 fujitsu kernel: [  169.808079] [drm] GPU hangs can indicate a
bug anywhere in the entire gfx stack, including userspace.
May 27 20:30:39 fujitsu kernel: [  169.808089] [drm] Please file a _new_ bug
report on bugs.freedesktop.org against DRI -> DRM/Intel
May 27 20:30:39 fujitsu kernel: [  169.808093] [drm] drm/i915 developers can
then reassign to the right component if it's not a kernel issue.
May 27 20:30:39 fujitsu kernel: [  169.808095] [drm] The gpu crash dump is
required to analyze gpu hangs, so please always attach it.
May 27 20:30:39 fujitsu kernel: [  169.808873] [drm:i915_set_reset_status]
*ERROR* render ring hung inside bo (0x5f95000 ctx 0) at 0x5f951cc
May 27 20:30:39 fujitsu kernel: [  169.864012] [drm] GMBUS [i915 gmbus vga]
timed out, falling back to bit banging on pin 2
May 27 20:30:40 fujitsu kernel: [  170.320016] [drm:i915_reset] *ERROR* Failed
to reset chip.


Time: 1432751439 s 812273 us
Kernel: 3.13.0-37-generic
PCI ID: 0x2992
EIR: 0x00000000
IER: 0x00028053
PGTBL_ER: 0x00000000
FORCEWAKE: 0x00000000
DERRMR: 0x00000000
CCID: 0x00000000
Missed interrupts: 0x00000000
  fence[0] = a5f0000056009d
  fence[1] = 605c0000605500d
  fence[2] = 8b0d0000630e07d
  fence[3] = 14bb0000146409d
  fence[4] = 8ded00008b6e06d
  fence[5] = 56c5000056b200d
  fence[6] = 4f7300004ce009d
  fence[7] = 45db000045d000d
  fence[8] = 9467000092e802d
  fence[9] = f7700000f6400d
  fence[10] = 57ad000056dc02d
  fence[11] = 599e000058ef01d
  fence[12] = 5a0a0000599f01d
  fence[13] = 605300005fb404d
  fence[14] = 607b0000606804d
  fence[15] = 630d0000608e06d
  INSTDONE_0: 0x3fe5fafd
  INSTDONE_1: 0x000ffffd
  INSTDONE_2: 0x00000000
  INSTDONE_3: 0x00000000
render command stream:
  HEAD: 0x00013200
  TAIL: 0x00013420
  CTL: 0x0001f001
  ACTHD: 0x05f951cc
  IPEIR: 0x00000000
  IPEHR: 0x79010003
  INSTDONE: 0x3fe5fafd
  BBADDR: 0x05f951cb
  BB_STATE: 0x000000a0
  INSTPS: 0x8001e022
  INSTPM: 0x00000000
  FADDR: 0x05f95280
  seqno: 0xfffff7a4
  waiting: yes
  ring->head: 0x00000000
  ring->tail: 0x00013420
  hangcheck: hung [40]
Active [181]:
  05f95000    32768 7e 00 fffff7a5 0 dirty purgeable render uncached
  06054000     4096 76 00 fffff7a5 0 dirty purgeable render uncached
  08b22000     4096 76 00 fffff7a5 0 dirty purgeable render uncached
  08b23000     4096 76 00 fffff7a5 0 dirty purgeable render uncached
  00544000     4096 7e 00 fffff7a6 0 p dirty render uncached
  08e11000  4423680 02 02 fffff7a6 fffff7a6 X dirty render uncached

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20150527/74fe0243/attachment.html>