[Bug 94534] New: Kernel 4.5.0 crashes when docking Lenovo T450s (with external monitor connected)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Mar 14 16:18:58 UTC 2016


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

            Bug ID: 94534
           Summary: Kernel 4.5.0 crashes when docking Lenovo T450s (with
                    external monitor connected)
           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: cs_gon at yahoo.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

I have also reported this bug on bugzilla.kernel.org (
https://bugzilla.kernel.org/show_bug.cgi?id=114601 ), not sure where the best
place to report this is.



When docking the T450s into the docking station (Lenovo Pro Dock) with an
external monitor connected, the kernel frequently crashes.

I have enabled kernel crash dumps and drm.debug=0x1e, and at least got the
dmesg output. But I currently don't have the debugging symbols (the kernel is
from the Ubuntu mainline PPA), so cannot provide a full backtrace at the
moment.

Please let me know if this is needed. And is compiling with CONFIG_DEBUG_INFO=y
enough, or are additional steps needed?

I also tested the drm-intel-nightly kernel
(linux-image-4.5.0-994-generic_4.5.0-994.201603132257_amd64.deb from the Ubuntu
kernel PPA), which causes the same crash (apart from the addresses the exact
same stack trace).

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


More information about the intel-gfx-bugs mailing list