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

[bugzilla-daemon at freedesktop.org]

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

--- Comment #8 from Lakshmi <lakshminarayana.vudum at intel.com> ---
(In reply to Vasily Galkin from comment #7)
> Created attachment 143322 [details]
> /sys/class/drm/card0/error on 4.20


(In reply to Vasily Galkin from comment #7)
> Created attachment 143322 [details]
> /sys/class/drm/card0/error on 4.20
> 
> Forgot to mention that /sys/class/drm/card0/error was already included in
> attachment 143111 [details]: 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).

Thanks for attaching the error file. There are no clues in the attached error
file.
As you said in the bug description, is that the only way to reproduce the hang?
If so, then the error file is also from the same scenario. Can you attach
Xorg.0.log?

> 
> 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?

There will be quiet a many changes going to drmtip regularly, so we always
recommend to use latest drmtip, logs from that will help during investigation.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee 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/2bfcfe1e/attachment.html>