From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 210321] /display/dc/dcn20/dcn20_resource.c:3240 dcn20_validate_bandwidth_fp+0x8b/0xd0 [amdgpu]
Date: Fri, 12 Mar 2021 15:58:43 +0000 [thread overview]
Message-ID: <bug-210321-2300-J4gYV1tUoU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210321-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=210321
--- Comment #5 from Tristen Hayfield (tristen.hayfield@gmail.com) ---
I did some more digging into this. I put some logging inside the if block to
see if that branch is ever taken:
if (voltage_supported && dummy_pstate_supported) {
context->bw_ctx.bw.dcn.clk.p_state_change_support = false;
goto restore_dml_state;
}
in order to log when or if the fallback worked. The logs confirmed that the
fallback is often used and generally works. Upon starting up the system and
starting up Xorg I get about a dozen log messages indicating that it entered
the if block. The only exception seems to be as Florian describes above, that
when the display shuts off due to power-saving it triggers the assertion.
--
You may reply to this email to add a comment.
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
prev parent reply other threads:[~2021-03-12 15:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 16:45 [Bug 210321] New: /display/dc/dcn20/dcn20_resource.c:3240 dcn20_validate_bandwidth_fp+0x8b/0xd0 [amdgpu] bugzilla-daemon
2020-12-27 20:17 ` [Bug 210321] " bugzilla-daemon
2021-01-07 2:49 ` bugzilla-daemon
2021-01-19 22:25 ` bugzilla-daemon
2021-03-12 12:31 ` bugzilla-daemon
2021-03-12 15:58 ` bugzilla-daemon [this message]
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-210321-2300-J4gYV1tUoU@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).