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 78439] [NVC1] Display corruption when DP connector is reattached
Date: Fri, 08 May 2015 18:17:56 +0000	[thread overview]
Message-ID: <bug-78439-8800-kVcxtT1S4z@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-78439-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

Andrius Štikonas <andrius-4ZmsDwijFH7sq35pWSNszA@public.gmane.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #100924|0                           |1
        is obsolete|                            |
 Attachment #101299|0                           |1
        is obsolete|                            |

--- Comment #24 from Andrius Štikonas <andrius-4ZmsDwijFH7sq35pWSNszA@public.gmane.org> ---
Created attachment 115643
  --> https://bugs.freedesktop.org/attachment.cgi?id=115643&action=edit
dmesg.txt (higher modes)

Ilia asked to create dmesg with the following nouveau_dp_rates[] enabled:

{  648000, 0x06, 4 },
{  324000, 0x06, 2 },
{  162000, 0x06, 1 },

In this 648 mode the whole screen flickers a lot (no reattaching is necessary
to reproduce it, it happens immediately)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2574 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2015-05-08 18:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 13:28 [Bug 78439] New: Display corruption when DP connector is reattached bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-78439-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-05-08 13:28   ` [Bug 78439] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-08 13:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-08 13:33   ` [Bug 78439] [NVC1] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-21  0:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-21  9:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-11 23:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-12 13:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-12 13:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-12 14:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-12 14:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-12 15:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-13  0:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-13  0:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-14 23:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-16 11:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-16 12:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-16 15:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-17  5:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-17 11:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-17 12:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-17 22:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-18 13:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-18 16:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-24 23:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-05-08 18:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2015-05-08 18:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-09-21 13:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-20 14:44   ` 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-78439-8800-kVcxtT1S4z@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.