From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 42162] [r600g][kms] Display not enabled on resume (HP DV6)
Date: Tue, 06 Aug 2013 04:31:52 +0000 [thread overview]
Message-ID: <bug-42162-502-qvH4mUpprI@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-42162-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 754 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=42162
--- Comment #19 from Johan Brannlund <freedesktop-bugs@nullinfinity.org> ---
I just tried 3.11-rc3, with the important difference that I kept both cards
active when suspending.
When resuming, the backlight now came on for a second but the screen then
turned dark again. Looking at the logs, the failure now seems less catastrophic
than before.
Could it be that if I disable one card before suspending (using vgaswitcheroo),
the resume code unsuccessfully tries to power up the previously disabled card?
Also, I don't seem to get any dpm options in /sys for the discrete card (the
5650), but that's a separate bug I guess.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1549 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 prev parent reply other threads:[~2013-08-06 4:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-42162-502@http.bugs.freedesktop.org/>
2012-02-03 19:10 ` [Bug 42162] Display not enabled on resume (HP DV6) bugzilla-daemon
2012-04-19 21:15 ` bugzilla-daemon
2012-07-08 15:31 ` bugzilla-daemon
2013-01-04 16:54 ` bugzilla-daemon
2013-01-04 16:56 ` bugzilla-daemon
2013-01-04 16:59 ` bugzilla-daemon
2013-01-04 17:16 ` bugzilla-daemon
2013-01-04 17:32 ` bugzilla-daemon
2013-02-21 19:40 ` bugzilla-daemon
2013-04-24 18:43 ` [Bug 42162] [r600g][kms] " bugzilla-daemon
2013-07-13 3:02 ` bugzilla-daemon
2013-07-13 4:18 ` bugzilla-daemon
2013-07-13 15:54 ` bugzilla-daemon
2013-07-26 19:50 ` bugzilla-daemon
2013-07-26 19:51 ` bugzilla-daemon
2013-08-06 4:31 ` bugzilla-daemon [this message]
2013-08-06 4:32 ` bugzilla-daemon
2013-08-06 4:44 ` bugzilla-daemon
2013-08-06 5:00 ` bugzilla-daemon
2013-11-17 11:56 ` bugzilla-daemon
2013-11-17 12:04 ` bugzilla-daemon
2014-03-10 15:52 ` bugzilla-daemon
2014-03-10 15:53 ` bugzilla-daemon
2014-03-12 16:45 ` bugzilla-daemon
2019-11-19 8:22 ` 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-42162-502-qvH4mUpprI@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).