[Bug 119991] New: Screen is corrupt upon resume from hybrid-sleep with Radeon HD5xxx cards

[bugzilla-daemon at bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=119991

            Bug ID: 119991
           Summary: Screen is corrupt upon resume from hybrid-sleep with
                    Radeon HD5xxx cards
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.6.1
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri at kernel-bugs.osdl.org
          Reporter: j.markus.maunus at gmail.com
        Regression: No

When resuming from hybrid-sleep, the screen is blank/corrupt (usually
white-ish, resembling static with some random colours, but sometimes black or a
pattern of black/white boxes) and the GUI is essentially unusable as nothing is
visible. The system is still responsive, however; I can switch to/from virtual
consoles without issue (and ssh into the box). 

I can reproduce this every time, but only on resume from hybrid sleep - normal
suspend works fine, as does hibernate. In fact, after resuming from hybrid
sleep I can "fix" the corruption by hibernating the system, and then resuming -
some corruption remains, but is quickly cleared by doing something simple such
as alt-tabbing or moving/resizing the topmost window, and the system appears to
work normally.

This does not happen with my HD 4670, but does appear with HD 5750 and HD 5850.

A possibly related symptom: sometimes both hibernate and hybrid-sleep take
extraordinarily long (hard disks spin down normally, but the system remains
powered and fans running for considerable time, anywhere from ~10 seconds to
several minutes after the disks have stopped). This happens with both 5-series
cards as well, but not on the 4670. However, I have had this happen even on
kernels which do not exhibit screen corruption after resume from hybrid sleep,
and can't consistently reproduce it.

I did a git bisect on Linus' tree and the first bad commit is
b9729b17a414f99c61f4db9ac9f9ed987fa0cbfe

-- 
You are receiving this mail because:
You are watching the assignee of the bug.