From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201139] amdgpu: [drm] enabling link 1 failed: 15 (vega)
Date: Sat, 12 Dec 2020 10:39:22 +0000 [thread overview]
Message-ID: <bug-201139-2300-95VojrkLBZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201139-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=201139
James Ettle (james@ettle.org.uk) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |james@ettle.org.uk
--- Comment #13 from James Ettle (james@ettle.org.uk) ---
Also seen here under kernel 5.9.12 with a Ryzen 3400G and a Samsung LU32H850UM
on DisplayPort:
[drm] enabling link 1 failed: 15
This is somewhat intermittent, and it comes back after power-cycling the
monitor (which is configured with manual input selection).
Not seen with Dell or Lenovo monitors on same port.
I'll try a different DisplayPort cable just to check...
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2020-12-12 10:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-15 14:29 [Bug 201139] New: amdgpu: [drm] enabling link 1 failed: 15 (vega) bugzilla-daemon
2018-09-17 10:25 ` [Bug 201139] " bugzilla-daemon
2018-11-01 8:38 ` bugzilla-daemon
2018-11-01 8:38 ` bugzilla-daemon
2018-11-01 8:39 ` bugzilla-daemon
2018-11-01 8:56 ` bugzilla-daemon
2018-11-01 12:57 ` bugzilla-daemon
2018-11-02 23:26 ` bugzilla-daemon
2018-11-10 2:11 ` bugzilla-daemon
2020-01-01 18:46 ` bugzilla-daemon
2020-02-24 0:36 ` bugzilla-daemon
2020-04-10 20:09 ` bugzilla-daemon
2020-06-25 17:33 ` bugzilla-daemon
2020-12-03 5:24 ` bugzilla-daemon
2020-12-12 10:39 ` bugzilla-daemon [this message]
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-201139-2300-95VojrkLBZ@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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;
as well as URLs for NNTP newsgroup(s).