All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 76483] [NV50, bisected, RFC patch] xset dpms force {on, off} does not work over DP
Date: Mon, 30 Jun 2014 14:19:54 +0000	[thread overview]
Message-ID: <bug-76483-8800-nuFezycIje@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-76483-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 657 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=76483

--- Comment #23 from Karl Schendel <schendel-zf86OBlHRo2+XT7JhA+gdA@public.gmane.org> ---
Created attachment 102016
  --> https://bugs.freedesktop.org/attachment.cgi?id=102016&action=edit
dmesg from garbled display

The interesting thing here is that I waited for the dpms timeout, and the
screen flashed and came back on more or less immediately, but clean.  It's as
if something decided that the DPMS-off transition was "activity" and turned the
screen back on, properly this time.  I don't think that's a driver issue
though.

-- 
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: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2014-06-30 14:19 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-22 17:17 [Bug 76483] New: [NV50, bisected, RFC patch] xset dpms force {on, off} does not work over DP bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-76483-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-03-24  3:58   ` [Bug 76483] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-24  9:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-28 18:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-24  9:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-11 23:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-12 11:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-12 14:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-13  7:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-19 23:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-19 23:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-19 23:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-20 13:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-20 13:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-25  5:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-25  5:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-25 13:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-29 15:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-29 16:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-30  0:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-30  3:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-30 11:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-30 11:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-30 14:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-07-01  1:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-01 11:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-01 21:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-02 17:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-02 17:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-02 22:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-02 22:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-03  0:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-09  9:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-22  5:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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-76483-8800-nuFezycIje@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.