From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 62671] KDE thinks the monitor is reconnected each time it resumes
Date: Sat, 23 Mar 2013 15:11:28 +0000 [thread overview]
Message-ID: <bug-62671-502-F8p3qILrgq@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-62671-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 813 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=62671
--- Comment #1 from Filipus Klutiero <chealer@gmail.com> ---
Forgot to mention one oddity I noticed when debugging this. To reproduce
faster, I reduced the powerdevil delay to suspend the screens to 1 minute. This
works, and while the bug may not happen if I resume just after the monitor
suspends, waiting an extra 20 seconds (so a total of 80 seconds) seems to be
enough.
But I noticed that after my monitor suspends, it is kind of suspended a second
time 30 to 40 seconds later (the monitor reactivates to show "HDMI POWER
SAVING", then is disabled again). But I don't have to wait this second suspend
to get the bug, and it also happens on 3.2.35, so I'm not sure this is a clue.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1616 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-03-23 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 15:04 [Bug 62671] New: KDE thinks the monitor is reconnected each time it resumes bugzilla-daemon
2013-03-23 15:11 ` bugzilla-daemon [this message]
2013-03-25 13:01 ` [Bug 62671] " bugzilla-daemon
2013-03-25 23:32 ` bugzilla-daemon
2013-04-24 18:56 ` [Bug 62671] [r600g][kms] " bugzilla-daemon
2014-01-23 14:08 ` [Bug 62671] [Radeon HD 5650][kms] " bugzilla-daemon
2019-11-19 8:32 ` 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-62671-502-F8p3qILrgq@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