From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 83331] radeon: Laptop panel out of sync after dpms standby/suspend/off
Date: Sat, 04 Oct 2014 12:05:33 +0000 [thread overview]
Message-ID: <bug-83331-2300-7ScYwMU5es@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-83331-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=83331
--- Comment #9 from Klaus Kusche <klaus.kusche@computerix.info> ---
Anything else I can try?
Any debug outputs I could add?
I think we are hunting two different problems:
1.) Why does the internal display crash
after a dpms standby/suspend/off?
This is extremely annoying, because it happens all the time
while giving my presentations in the lecture halls,
and with all the students in front of me,
blindly fixing things is irritating.
Without knowing the code, I'd assume that this should be easy to find:
What's the difference in code paths between "dpms on" and "xrandr
off+auto"?
"xrandr off+auto" obviously does something more than "dpms on"?
Couldn't this be simply added to "dpms on", too?
Note that just "xrandr auto" alone does not fix the crashed display,
a "xrandr off" is needed first.
2.) Why do the switch from VGA to framebuffer during boot
and an "xrandr off+auto" both take ages (> 5 sec)?
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2014-10-04 12:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 12:11 [Bug 83331] New: radeon: Laptop panel out of sync after dpms standby/suspend/off bugzilla-daemon
2014-08-27 13:30 ` [Bug 83331] " bugzilla-daemon
2014-08-27 14:00 ` bugzilla-daemon
2014-08-27 14:00 ` bugzilla-daemon
2014-08-27 14:03 ` bugzilla-daemon
2014-09-14 9:43 ` bugzilla-daemon
2014-09-16 23:54 ` bugzilla-daemon
2014-09-17 5:56 ` bugzilla-daemon
2014-09-17 5:59 ` bugzilla-daemon
2014-10-04 12:05 ` bugzilla-daemon [this message]
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-83331-2300-7ScYwMU5es@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.