[Bug 81175] New: Kernel panic on boot or after wake from suspend

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 81175
                CC: intel-gfx-bugs at lists.freedesktop.org
          Assignee: intel-gfx-bugs at lists.freedesktop.org
           Summary: Kernel panic on boot or after wake from suspend
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: jmcclure at cns.umass.edu
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: DRM/Intel
           Product: DRI

I've been experiencing frequent kernel panics during boot or shortly after
waking from suspend.  I'm running ArchLinux on a Lenovo X200 laptop.  I had
traced the problem to any/all of intel-dri, mesa, or mesa-libgl as downgrading
all three to version 10.1.4 prevents the issues.  The problem persists with all
10.2.x upgrades up to and including 10.2.3.

Based on logs, it seems the failed boots actually do completely boot, but
nothing appears on screen after boot loader and kernel line.  If I do nothing,
the kernel panics several seconds later - I am able to shutdown with the power
button during this period which appears as a normal shutdown in the "failed
boot" log.  I have not been able to get logs from sessions that end in a kernel
panic.

The failed boots are frequent, but sporadic - roughly every other boot attempt.

I have a journalctl log from a failed boot [1], a successful boot for reference
[2], and the drm/card0/error content [3].

The successful boot log includes the following which led me to post here:

[drm] stuck on render ring
[drm] GPU HANG: ecode 0:0x880e2084, in X [228], reason: Ring hung, action:
reset
[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] GPU crash dump saved to /sys/class/drm/card0/error
[drm:intel_pipe_set_base] *ERROR* pin & fence failed


While I've checked open bugs on DRM/Intel, I've not been able to assess whether
this is related to any open reports.  Pardon the noise if it is.

-Jesse
jmcclure at cns.umass.edu

[1] https://raw.githubusercontent.com/TrilbyWhite/junkdrawer/master/boot_fail

[2]
https://raw.githubusercontent.com/TrilbyWhite/junkdrawer/master/boot_success

[3 LARGE 1.4M]
https://raw.githubusercontent.com/TrilbyWhite/junkdrawer/master/drm_error

-- 
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/20140710/f0c76db8/attachment.html>