From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 197925] [amdgpu_dc][carrizo] multiple monitor handling errors
Date: Fri, 01 Dec 2017 23:26:47 +0000 [thread overview]
Message-ID: <bug-197925-2300-skluzDrPJA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-197925-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=197925
Miłosz Rachwał (kbz-me@milek7.pl) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kbz-me@milek7.pl
--- Comment #4 from Miłosz Rachwał (kbz-me@milek7.pl) ---
I have similar issue on Polaris (RX 580) with DC enabled. After reenabling
monitors from powersave one display is cycling on/off every few seconds, each
time printing dc_link_detect to dmesg.
On kernels compiled from amd-staging-drm-next tree this issue also occured
after wakeup from sleep, but now on 4.15-rc1 whole system crashes after wakeup.
--
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 prev parent reply other threads:[~2017-12-01 23:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 18:30 [Bug 197925] New: [amdgpu_dc][carrizo] multiple monitor handling errors bugzilla-daemon
2017-11-21 20:09 ` [Bug 197925] " bugzilla-daemon
2017-11-28 9:31 ` bugzilla-daemon
2017-12-01 18:50 ` bugzilla-daemon
2017-12-01 23:26 ` bugzilla-daemon [this message]
2017-12-02 2:37 ` bugzilla-daemon
2017-12-02 10:45 ` bugzilla-daemon
2017-12-03 23:00 ` bugzilla-daemon
2017-12-15 22:41 ` bugzilla-daemon
2017-12-16 2:15 ` bugzilla-daemon
2017-12-18 10:18 ` bugzilla-daemon
2017-12-20 9:34 ` bugzilla-daemon
2018-02-07 20:14 ` bugzilla-daemon
2018-02-27 0:48 ` bugzilla-daemon
2018-03-10 21:50 ` bugzilla-daemon
2018-03-12 13:32 ` bugzilla-daemon
2018-03-12 19:28 ` 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-197925-2300-skluzDrPJA@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.