From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107296] WARNING: CPU: 0 PID: 370 at drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calcs.c:1355 dcn_bw_update_from_pplib+0x16b/0x280 [amdgpu]
Date: Thu, 17 Oct 2019 12:12:56 +0000 [thread overview]
Message-ID: <bug-107296-502-FyfUiPHpIG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107296-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1923 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107296
Janpieter Sollie <janpieter.sollie@dommel.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #144689|0 |1
is obsolete| |
--- Comment #21 from Janpieter Sollie <janpieter.sollie@dommel.be> ---
Created attachment 145764
--> https://bugs.freedesktop.org/attachment.cgi?id=145764&action=edit
dmesg of PPLIB error
still present on linux 5.3, with the following exceptions:
- the values in mV seem to be initialized,
- DRM does not complain about 'Cannot find any crtc or sizes' after GPU adding
- DRM: construct error is gone
So it's going the good way, I guess ...
I investigated the source around dcn_bw_update_from_pplib
And I saw the following code in gpu/drm/amd/display/dc/calcs/dcn_calcs.c
========================================
bool res;
/* TODO: This is not the proper way to obtain
fabric_and_dram_bandwidth, should be min(fclk, memclk) */
res = dm_pp_get_clock_levels_by_type_with_voltage(
ctx, DM_PP_CLOCK_TYPE_FCLK, &fclks);
kernel_fpu_begin();
if (res)
res = verify_clock_values(&fclks);
if (res) {
//unimportant, left out
} else
BREAK_TO_DEBUGGER();
=============================================
which probably explains what happens: fclks gets a number of clock values from
dm_pp_get_clock_levels_by_type_with_voltage, setting res to true.
It tries to validate the clock values then, which fails because of the invalid
numbers
After that, it breaks to debugger.
Is it possible the vega11 needs more time to initialize its clock limits?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3652 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-10-17 12:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 17:13 [Bug 107296] WARNING: CPU: 0 PID: 370 at drivers/gpu/drm/amd/amdgpu/../display/dc/calcs/dcn_calcs.c:1355 dcn_bw_update_from_pplib+0x16b/0x280 [amdgpu] bugzilla-daemon
2018-07-23 14:29 ` bugzilla-daemon
2018-07-23 15:39 ` bugzilla-daemon
2018-08-08 16:20 ` bugzilla-daemon
2018-10-07 1:14 ` bugzilla-daemon
2018-11-11 15:14 ` bugzilla-daemon
2018-12-16 18:34 ` bugzilla-daemon
2019-01-13 16:52 ` bugzilla-daemon
2019-02-17 12:28 ` bugzilla-daemon
2019-02-22 15:05 ` bugzilla-daemon
2019-03-18 23:03 ` bugzilla-daemon
2019-04-29 20:08 ` bugzilla-daemon
2019-05-25 21:46 ` bugzilla-daemon
2019-05-25 22:02 ` bugzilla-daemon
2019-05-27 11:06 ` bugzilla-daemon
2019-07-03 6:49 ` bugzilla-daemon
2019-07-13 18:30 ` bugzilla-daemon
2019-08-30 20:49 ` bugzilla-daemon
2019-09-12 10:33 ` bugzilla-daemon
2019-09-25 14:16 ` bugzilla-daemon
2019-09-25 14:18 ` bugzilla-daemon
2019-10-17 12:12 ` bugzilla-daemon [this message]
2019-11-01 16:16 ` bugzilla-daemon
2019-11-06 16:14 ` bugzilla-daemon
2019-11-19 8:26 ` bugzilla-daemon
2019-11-20 7:56 ` 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-107296-502-FyfUiPHpIG@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 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.