[Bug 89371] New: wake up from sleep state gives corrupt display (on both screen)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Feb 28 11:36:13 PST 2015


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

            Bug ID: 89371
           Summary: wake up from sleep state gives corrupt display (on
                    both screen)
           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: zebul666 at hotmail.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

hi
I am using ubuntu 14.10 with the oibaf ppa to use the latest intel driver.

After the update from 2.99.917+git1502260732.53d804~gd~u to
2.99.917+git1502271932.9fb815~gd~u, the screen is now corrupted and partially
frozen when waking up from sleep mode.

I am using a 2 monitor set-up with the internal LDVS of the laptop and another
one via HDMI.
I have an inspiron 15 3521 with an HD 4000

The way the screen look corrupt is: At least 2 windows appear on 2 monitors but
partially. the mouse cursor is visible and moving with the mouse. But the
windows are unreponsive.

I have to ssh into the laptop and run "DISPLAY:0 unity --replace" to partially
fix the freeze

I got no message in /var/log/syslog or Xorg.0.log

I wonder if it is really related to the 2 monitor setup as I wake up the laptop
with the external monitor shutdown and the screen was already corrupted.

Please move the bug to the correct project if I made a mistake.

-- 
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/20150228/fa9e9e1f/attachment.html>


More information about the intel-gfx-bugs mailing list