[Bug 94848] New: GPU HANG: ecode 9:0:0x85dfffff on i5-6260U

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 94848
           Summary: GPU HANG: ecode 9:0:0x85dfffff on i5-6260U
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: pthomas8589 at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 122772
  --> https://bugs.freedesktop.org/attachment.cgi?id=122772&action=edit
two faults

I know others have seen this error, but I'll add it if folks want the logs.

I'm using Ubuntu 14.04, the kernel is drm-intel-nightly, but I ran into compile
issues with libdrm so everything else is the latest Ubuntu.

Some more details;
arch: x86_64
kernel: 4.6.0-rc2+ (drm-intel-nightly from 4/4/16)
Machine: NUC6I5SYH (i5-6260U)
Display: HDMI & DP

First I captured dmesg & card0/error without the drm.debug command line option,
this is the f1 folder in the bz2, but then I saw the note about wanting that so
the f2_dbg_cmdline folder is with "drm.debug=0x1e log_buf_len=1M"

In both of these cases the screens freeze, but the mouse continues to work,
then about 10-20 seconds later it comes back to normal. There is a message in
the lower right corner "KWin Window Manager, desktop effects were restarted due
to a graphics restart" I've also had instances where both the screens & mouse
freeze, and when this happens a reboot is needed even ssh doesn't work.

thanks,
Paul

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