From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 119991] New: Screen is corrupt upon resume from hybrid-sleep with Radeon HD5xxx cards
Date: Sat, 11 Jun 2016 02:41:35 +0000 [thread overview]
Message-ID: <bug-119991-2300@https.bugzilla.kernel.org/> (raw)
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@kernel-bugs.osdl.org
Reporter: j.markus.maunus@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.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-06-11 2:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 2:41 bugzilla-daemon [this message]
2016-06-12 10:26 ` [Bug 119991] Screen is corrupt upon resume from hybrid-sleep with Radeon HD5xxx cards bugzilla-daemon
2016-06-12 13:17 ` bugzilla-daemon
2016-06-13 7:20 ` bugzilla-daemon
2016-06-13 12:13 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-119991-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.