From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201139] New: amdgpu: [drm] enabling link 1 failed: 15 (vega)
Date: Sat, 15 Sep 2018 14:29:33 +0000 [thread overview]
Message-ID: <bug-201139-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=201139
Bug ID: 201139
Summary: amdgpu: [drm] enabling link 1 failed: 15 (vega)
Product: Drivers
Version: 2.5
Kernel Version: 4.19-rc3
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: mezin.alexander@gmail.com
Regression: No
My setup:
- RX Vega 64
- Arch Linux
- GNOME 3.28.3 on Xorg 1.20.1
- modesetting Xorg driver
- LG 27UD69P and Dell P2415Q
I have "screen blanking" enabled in Gnome. Sometimes (very rarely) one display
(Dell, connected to 2nd DisplayPort) doesn't wake up correctly. It turns on,
shows only black screen, then quickly shows "no signal" message. In kernel log
I see:
[39215.008773] [drm] enabling link 1 failed: 15
If I manually turn the display off and on, it starts to work.
Can't tell if it is a regression (hardly it is) because on 4.18 and earlier
screen blanking just makes the driver hang:
https://bugzilla.kernel.org/show_bug.cgi?id=200531
I've never seen a similar issue on Windows on the same machine.
If I'm not mistaken, I've seen the same issue with Gnome on Wayland too (but
I'm not sure).
--
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
next reply other threads:[~2018-09-15 14:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-15 14:29 bugzilla-daemon [this message]
2018-09-17 10:25 ` [Bug 201139] amdgpu: [drm] enabling link 1 failed: 15 (vega) 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
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@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 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.