From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106735] [amdgpu] all displays reconnect after failed EDID read
Date: Wed, 30 May 2018 20:15:43 +0000 [thread overview]
Message-ID: <bug-106735-502-XYLvPMX2os@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106735-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 744 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106735
--- Comment #3 from dwagner <jb5sgc1n.nya@20mm.eu> ---
(In reply to Matthias from comment #2)
> Should I try to force a binary EDID for the connected PSVR?
At this time, I would recommend against this: I experience consistent crashes
on evey S3 resume if use the kernel command line parameter to force a certain
binary EDID.
Which is a pity, because (a) this worked fine with prior kernel versions until
early October 2017 and (b) it was useful when waking up the computer remotely
while the connected display is still switched off.
See also: https://bugs.freedesktop.org/show_bug.cgi?id=103277
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1831 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
next prev parent reply other threads:[~2018-05-30 20:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 15:05 [Bug 106735] [amdgpu] all displays reconnect after failed EDID read bugzilla-daemon
2018-05-30 15:05 ` bugzilla-daemon
2018-05-30 15:14 ` bugzilla-daemon
2018-05-30 20:15 ` bugzilla-daemon [this message]
2018-05-31 8:02 ` bugzilla-daemon
2018-05-31 8:02 ` bugzilla-daemon
2019-11-19 8:40 ` 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-106735-502-XYLvPMX2os@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