From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 209225] [AMDGPU] oops on each boot: dc_link_set_backlight_level
Date: Sat, 12 Sep 2020 22:40:30 +0000 [thread overview]
Message-ID: <bug-209225-2300-alPukHGnhm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209225-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209225
--- Comment #6 from Arthur Borsboom (arthurborsboom@gmail.com) ---
I have applied and tested the patch.
Unfortunately it did not resolve the problem.
Apparently the ASSERT(0) in this piece of code triggering the oops.
----------------------
drivers/gpu/drm/amd/display/dc/clk_mgr/dcn21/rn_clk_mgr.c
rn_clk_mgr_helper_populate_bw_params
/* Find lowest DPM, FCLK is filled in reverse order*/
for (i = PP_SMU_NUM_FCLK_DPM_LEVELS - 1; i >= 0; i--) {
if (clock_table->FClocks[i].Freq != 0 &&
clock_table->FClocks[i].Vol != 0) {
j = i;
break;
}
}
if (j == -1) {
/* clock table is all 0s, just use our own hardcode */
ASSERT(0);
return;
}
----------------------
--
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:[~2020-09-12 22:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 14:46 [Bug 209225] New: [AMDGPU] oops each boot: dc_link_set_backlight_level bugzilla-daemon
2020-09-10 16:10 ` [Bug 209225] " bugzilla-daemon
2020-09-10 16:11 ` bugzilla-daemon
2020-09-12 9:27 ` bugzilla-daemon
2020-09-12 9:28 ` bugzilla-daemon
2020-09-12 9:29 ` bugzilla-daemon
2020-09-12 9:30 ` bugzilla-daemon
2020-09-12 20:38 ` [Bug 209225] [AMDGPU] oops on " bugzilla-daemon
2020-09-12 21:03 ` bugzilla-daemon
2020-09-12 22:40 ` bugzilla-daemon [this message]
2020-09-20 18: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-209225-2300-alPukHGnhm@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