[Bug 99829] New: [IVB] xrandr fails after resume from hibernation since kernel 4.7+

[bugzilla-daemon at freedesktop.org]

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

            Bug ID: 99829
           Summary: [IVB] xrandr fails after resume from hibernation since
                    kernel 4.7+
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: pedrib at gmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 129647
  --> https://bugs.freedesktop.org/attachment.cgi?id=129647&action=edit
Dmesg after first boot

Since kernel 4.7 (at least, see below), whenever I resume from hibernation and
try to use xrandr to manipulate any video output, my screen goes off and on
again and this message is displayed:
xrandr: Configure crtc X failed

With no effect happening, whatever the xrandr command I issued.

This has been confirmed in kernel 4.7, 4.8, 4.9 and 4.10-rc8 drm-tip that I've
just built now up to commit 890e171e84eb11944701de9d53c1162dd5c38142.

I can't recall exactly, but I'm pretty sure 4.6 has this issue, and MAYBE 4.5.
I am pretty sure however that 4.4 works just fine as I've been using that for a
long time.

This is the same issue described here, and already bisected in October last
year by another user:
https://lkml.org/lkml/2016/10/28/441

My hardware is a Lenovo X230 Ivy Bridge i5-3320m. Distro is Debian amd64, mix
of stable and testing.

I'm attaching the dmesg logs before and after hibernation using drm-tip and
drm.debug=0xf.

-- 
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/20170215/a28df91e/attachment.html>