From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 77562] New: Display keep blank after resume
Date: Thu, 17 Apr 2014 08:33:17 +0000 [thread overview]
Message-ID: <bug-77562-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1097 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=77562
Priority: medium
Bug ID: 77562
Assignee: dri-devel@lists.freedesktop.org
Summary: Display keep blank after resume
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: rdp.effort@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Created attachment 97496
--> https://bugs.freedesktop.org/attachment.cgi?id=97496&action=edit
dmesg with dri.debug=4
I have a behaviour very similar to
https://bugs.freedesktop.org/show_bug.cgi?id=42960.
After resuming from suspend, display is blank.
I have tried the tricks suggested in #42960 (acpi_sleep=s3_bios) with no luck,
when I use that the laptop doesn't resume correctly.
With the catalyst driver the display resumes correctly.
It's an Ubuntu 13.10 with a 3.14 kernel, DPM is activated.
Feel free to ask for tests.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2674 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2014-04-17 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 8:33 bugzilla-daemon [this message]
2014-04-17 8:33 ` [Bug 77562] Display keep blank after resume bugzilla-daemon
2014-04-17 8:35 ` [Bug 77562] Display keep blank after resume with radeon HD7310 bugzilla-daemon
2014-04-17 8:37 ` bugzilla-daemon
2014-04-17 12:49 ` 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-77562-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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.