All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107390] [BISECTED] EDID read failure breaks display mirroring
Date: Wed, 01 Aug 2018 12:49:15 +0000	[thread overview]
Message-ID: <bug-107390-502-Apa40rSQwj@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107390-502@http.bugs.freedesktop.org/>


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

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

--- Comment #14 from Justinas Narusevicius <junaru@gmail.com> ---
(In reply to Harry Wentland from comment #9)
> That commit is correct. I don't think we should revert it.
You are probably correct. Some more things i have noticed:

When using Gnome Display Manager on pre
ac916c914c3156e53505e9ea3a9d1495518bf873 kernels my displays would always loose
signal for half a second after login and then come right back up.

Same 'signal flicker' (atleast form users perspective) could be observed on one
display when other was being turned on or powered off.

This no longer happens post ac916c914c3156e53505e9ea3a9d1495518bf873. The
transition form GDM login to desktop is smooth and i can even see the desktop
fadein animation.

> Are you able to take another set of kernel logs from amd-staging-drm-next,
> both with the regression commit and without, with drm.debug=0x4 set both
> times?

Logs are attached. Please let me know if i can do anything more to help.

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

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

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

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-08-01 12:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-26 18:10 [Bug 107390] [BISECTED] EDID read failure breaks display mirroring bugzilla-daemon
2018-07-26 18:12 ` bugzilla-daemon
2018-07-26 18:13 ` bugzilla-daemon
2018-07-26 18:15 ` bugzilla-daemon
2018-07-26 18:16 ` bugzilla-daemon
2018-07-26 18:16 ` bugzilla-daemon
2018-07-26 18:17 ` bugzilla-daemon
2018-07-26 20:55 ` bugzilla-daemon
2018-07-26 20:56 ` bugzilla-daemon
2018-07-27 12:11 ` bugzilla-daemon
2018-07-27 12:12 ` bugzilla-daemon
2018-07-27 14:33 ` bugzilla-daemon
2018-07-31 19:33 ` bugzilla-daemon
2018-07-31 21:16 ` bugzilla-daemon
2018-07-31 21:23 ` bugzilla-daemon
2018-08-01 11:59 ` bugzilla-daemon
2018-08-01 11:59 ` bugzilla-daemon
2018-08-01 12:49 ` bugzilla-daemon [this message]
2018-08-01 13:55 ` bugzilla-daemon
2018-08-01 14:10 ` bugzilla-daemon
2018-08-01 14:51 ` bugzilla-daemon
2018-08-01 14:53 ` bugzilla-daemon
2018-08-01 15:34 ` bugzilla-daemon
2019-11-19  8:45 ` 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-107390-502-Apa40rSQwj@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 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.