[Bug 109047] [gen3] [drm] GPU HANG: ecode 3:0:7ee06741 in Chrome_InProcGp, hang on rcs0, reset

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Feb 7 12:36:22 UTC 2019


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

Vasily Galkin <galkin-vv at ya.ru> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #142794|0                           |1
        is obsolete|                            |
 Attachment #142795|0                           |1
        is obsolete|                            |

--- Comment #7 from Vasily Galkin <galkin-vv at ya.ru> ---
Created attachment 143322
  --> https://bugs.freedesktop.org/attachment.cgi?id=143322&action=edit
/sys/class/drm/card0/error on 4.20

Forgot to mention that /sys/class/drm/card0/error was already included in
attachment 143111: Compressed logs of crash on 4.20 with drm.debug=0x1e

However now attaching it for simplicity as separate file (and obsoleting all
attachments from non-last reproduction).

About testing on drm-tip:
note that the problem typically reproduces only after several weeks of uptime -
so it is always "nearly 1 kernel release late" - for example my last test was
from drm-tip/2018-12-13

Since testing time is so long - it may need some planning of what version start
to test - it may be more useful to wait 1-2-3 weeks and test some "new release
full of changes" than restarting testing with "nearly same code".

Does current drm-tip since 2018-12-13 include any changes that may affect this
bug or it's better to wait for some future pull?

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


More information about the intel-gfx-bugs mailing list