From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101528] RX460 Memory clock stays high until card is "used"
Date: Thu, 29 Jun 2017 19:48:40 +0000 [thread overview]
Message-ID: <bug-101528-502-m00ki7JFdY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101528-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 2109 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101528
--- Comment #2 from Alexander Tsoy <alexander@tsoy.me> ---
I've added printing of some debug info into smu7_hwmgr.c and here what I get
before GPU enters that state:
[ 778.701843] AMDGPU: vblank_time_us: 630, switch_limit_us: 450
[ 778.707608] AMDGPU: vblank_time_us: 630, switch_limit_us: 450
[ 778.713379] AMDGPU: disable_mclk_switching: 0,
disable_mclk_switching_for_frame_lock: 0, info.display_count: 1,
smu7_vblank_too_short: 0, mode_info.refresh_rate: 60
[ 778.748777] AMDGPU: vblank_time_us: 0, switch_limit_us: 450
[ 778.754361] AMDGPU: vblank_time_us: 0, switch_limit_us: 450
[ 778.759951] AMDGPU: disable_mclk_switching: 1,
disable_mclk_switching_for_frame_lock: 0, info.display_count: 1,
smu7_vblank_too_short: 1, mode_info.refresh_rate: 0
For some reason if refresh_rate = 0 then vblank_time_us = 0. Shouldn't the
latter be 0xffffffff instead? So I guess the following commit is the culprit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=09be4a5219610a6fae3215d4f51f948d6f5d2609
and the following patch should fix (or workaround?) this issue:
- if (vblank_time_us < switch_limit_us)
+ if (vblank_time_us && (vblank_time_us < switch_limit_us))
After applying it:
[ 409.588673] AMDGPU: vblank_time_us: 630, switch_limit_us: 450
[ 409.594427] AMDGPU: vblank_time_us: 630, switch_limit_us: 450
[ 409.600182] AMDGPU: disable_mclk_switching: 0,
disable_mclk_switching_for_frame_lock: 0, info.display_count: 1,
smu7_vblank_too_short: 0, mode_info.refresh_rate: 60
[ 409.639750] AMDGPU: vblank_time_us: 0, switch_limit_us: 450
[ 409.645321] AMDGPU: vblank_time_us: 0, switch_limit_us: 450
[ 409.650917] AMDGPU: disable_mclk_switching: 0,
disable_mclk_switching_for_frame_lock: 0, info.display_count: 1,
smu7_vblank_too_short: 0, mode_info.refresh_rate: 0
$ cat /sys/class/drm/card0/device/pp_dpm_mclk
0: 150Mhz *
1: 300Mhz
2: 700Mhz
3: 1450Mhz
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3061 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:[~2017-06-29 19:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 18:58 [Bug 101528] RX460 Memory clock stays high until card is "used" bugzilla-daemon
2017-06-29 17:36 ` bugzilla-daemon
2017-06-29 19:48 ` bugzilla-daemon [this message]
2017-06-29 20:14 ` bugzilla-daemon
2017-06-29 22:14 ` bugzilla-daemon
2017-07-14 11:52 ` bugzilla-daemon
2017-07-14 11:53 ` [Bug 101528] RX460 Memory clock stays high until card / display " bugzilla-daemon
2017-08-30 15:13 ` 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-101528-502-m00ki7JFdY@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