[Bug 98986] New: [i915][SNB] black screen after disconnecting HDMI monitor

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Dec 3 21:28:49 UTC 2016


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

            Bug ID: 98986
           Summary: [i915][SNB] black screen after disconnecting HDMI
                    monitor
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: kernel at stefaus.de
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 128322
  --> https://bugs.freedesktop.org/attachment.cgi?id=128322&action=edit
dmesg with drm.debug=14

Since new install of my Linux System and using a 4.4+ Kernel (before 3.19) I'm
getting kernel exceptions every time I disconnect my via HDMI connected
Monitor.

Steps:
- booting to desktop without problems
- disconnect HDMI
- eDP is showing desktop for ~2 seconds
- eDP turns black, no keyboard inputs, the rest keeps running

No difference if HDMI connected while/after boot, I tried different 4.4+ Kernel
Versions from Ubuntu to Mainline, every time nearly the same output.

[   90.275535] [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe
A stuck
[   90.329696] ------------[ cut here ]------------
[   90.329789] WARNING: CPU: 3 PID: 1834 at
/home/kernel/COD/linux/drivers/gpu/drm/i915/intel_display.c:14221
intel_atomic_commit_tail+0xf93/0xfc0 [i915]

see attached dmesg for the full exception trace.

-- 
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/20161203/51f8d463/attachment.html>


More information about the intel-gfx-bugs mailing list