From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 200695] Blank screen on RX 580 with amdgpu.dc=1 enabled (no displays detected)
Date: Tue, 18 Sep 2018 15:02:45 +0000 [thread overview]
Message-ID: <bug-200695-2300-zTgjEe29NX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200695-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200695
--- Comment #14 from Claude Heiland-Allen (claude@mathr.co.uk) ---
I checked out linux v4.19-rc4 from git, then reverted that commit - no change,
display goes blank about 5 seconds into boot.
I noticed something else in the dmesg (it was there in 4.19-rc1,rc2,rc3,rc4,rc4
with reverted commit, but not earlier versions):
[ 5.109572] amdgpu: [powerplay] Failed to retrieve minimum clocks.
[ 5.109577] amdgpu: [powerplay] Error in phm_get_clock_info
[ 5.109627] [drm] DM_PPLIB: values for Engine clock
[ 5.109629] [drm] DM_PPLIB: 300000
[ 5.109631] [drm] DM_PPLIB: 600000
[ 5.109632] [drm] DM_PPLIB: 900000
[ 5.109633] [drm] DM_PPLIB: 1145000
[ 5.109634] [drm] DM_PPLIB: 1215000
[ 5.109636] [drm] DM_PPLIB: 1257000
[ 5.109637] [drm] DM_PPLIB: 1300000
[ 5.109638] [drm] DM_PPLIB: 1366000
[ 5.109640] [drm] DM_PPLIB: Validation clocks:
[ 5.109641] [drm] DM_PPLIB: engine_max_clock: 136600
[ 5.109642] [drm] DM_PPLIB: memory_max_clock: 200000
[ 5.109644] [drm] DM_PPLIB: level : 8
[ 5.109646] [drm] DM_PPLIB: values for Memory clock
[ 5.109647] [drm] DM_PPLIB: 300000
[ 5.109648] [drm] DM_PPLIB: 1000000
[ 5.109649] [drm] DM_PPLIB: 2000000
[ 5.109651] [drm] DM_PPLIB: Validation clocks:
[ 5.109652] [drm] DM_PPLIB: engine_max_clock: 136600
[ 5.109653] [drm] DM_PPLIB: memory_max_clock: 200000
[ 5.109655] [drm] DM_PPLIB: level : 8
[ 5.124083] [drm] Display Core initialized with v3.1.59!
The last (largest) value for "engine clock" and "memory clock" are 10x the
validation values for "engine clock max" and "memory clock max". I see in the
amd/powerplay sources some values are in units of 10kHz, some in units of
1kHz(?) - maybe a conversion was missed somewhere? Or maybe the printout is
totally normal and I know nothing :)
The error message common to all kernels with amdgpu.dc=1 since 4.17 is:
[ 5.256378] [drm] Cannot find any crtc or sizes
--
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:[~2018-09-18 15:03 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 18:32 [Bug 200695] New: Blank screen on RX 580 with amdgpu.dc=1 enabled (no displays detected) bugzilla-daemon
2018-07-31 18:33 ` [Bug 200695] " bugzilla-daemon
2018-07-31 18:34 ` bugzilla-daemon
2018-07-31 18:37 ` bugzilla-daemon
2018-07-31 18:37 ` bugzilla-daemon
2018-07-31 18:38 ` bugzilla-daemon
2018-08-28 15:40 ` bugzilla-daemon
2018-08-28 15:42 ` bugzilla-daemon
2018-09-06 6:51 ` bugzilla-daemon
2018-09-10 13:45 ` bugzilla-daemon
2018-09-17 17:46 ` bugzilla-daemon
2018-09-17 18:09 ` bugzilla-daemon
2018-09-18 2:10 ` bugzilla-daemon
2018-09-18 13:43 ` bugzilla-daemon
2018-09-18 15:02 ` bugzilla-daemon [this message]
2018-10-01 17:30 ` bugzilla-daemon
2018-10-10 21:16 ` bugzilla-daemon
2018-10-22 18:52 ` bugzilla-daemon
2018-11-06 16:13 ` bugzilla-daemon
2018-11-13 19:54 ` bugzilla-daemon
2018-11-19 18:15 ` bugzilla-daemon
2018-12-04 23:12 ` bugzilla-daemon
2018-12-28 6:07 ` bugzilla-daemon
2019-01-12 11:18 ` bugzilla-daemon
2019-01-13 19:35 ` bugzilla-daemon
2019-02-25 17:51 ` bugzilla-daemon
2019-02-26 16:43 ` bugzilla-daemon
2019-02-27 12:42 ` bugzilla-daemon
2019-03-07 15:42 ` bugzilla-daemon
2019-03-07 16:26 ` bugzilla-daemon
2019-03-07 16:57 ` bugzilla-daemon
2019-04-02 16:38 ` bugzilla-daemon
2019-04-02 16:39 ` bugzilla-daemon
2019-09-20 11:22 ` bugzilla-daemon
2019-11-05 14:07 ` bugzilla-daemon
2019-12-16 21:43 ` bugzilla-daemon
2019-12-16 23:52 ` bugzilla-daemon
2020-02-15 14:42 ` bugzilla-daemon
2020-02-16 13:47 ` bugzilla-daemon
2020-02-16 21:12 ` bugzilla-daemon
2020-05-08 10:55 ` bugzilla-daemon
2020-05-08 15:12 ` bugzilla-daemon
2020-05-08 18:20 ` bugzilla-daemon
2020-05-30 19:22 ` bugzilla-daemon
2020-06-16 23:39 ` bugzilla-daemon
2020-06-17 2:24 ` bugzilla-daemon
2020-06-17 3:11 ` bugzilla-daemon
2020-06-28 9:25 ` bugzilla-daemon
2020-06-28 9:26 ` bugzilla-daemon
2020-06-28 9:27 ` bugzilla-daemon
2021-04-06 7:51 ` 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-200695-2300-zTgjEe29NX@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.