From: Jiri Slaby <jirislaby@kernel.org>
To: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>,
"Wentland, Harry" <Harry.Wentland@amd.com>
Cc: "Li, Sun peng (Leo)" <Sunpeng.Li@amd.com>,
siqueira@igalia.com, Alex Deucher <alexander.deucher@amd.com>,
Tony.Cheng@amd.com,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
DRI devel <dri-devel@lists.freedesktop.org>,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: amdgpu crashes in get_ss_info_from_atombios()
Date: Wed, 15 Jul 2026 10:51:05 +0200 [thread overview]
Message-ID: <a9ee54e6-2413-4156-9bde-d528ae3c63a3@kernel.org> (raw)
Hi,
SUSE received a bug report:
https://bugzilla.suse.com/show_bug.cgi?id=1271175
get_ss_info_from_atombios() crashes in 7.1.2.
calc_pll_cs->ctx (dc_context) is NULL while trying to log by the first
DC_LOG_SYNC() in get_ss_info_from_atombios():
if (as_signal == AS_SIGNAL_TYPE_HDMI
&&
ss_info_cur->spread_spectrum_percentage > 6){
/* invalid input, do nothing */
DC_LOG_SYNC(
"Invalid SS percentage ");
DC_LOG_SYNC(
"for HDMI in ATOMBIOS info Table!!!\n");
continue;
}
Note dce110_clk_src_construct() calls:
-> ss_info_from_atombios_create()
-> get_ss_info_from_atombios() <- uses calc_pll_cs->ctx
-> calc_pll_max_vco_construct() <- sets calc_pll_cs->ctx AFAICT
calc_pll_cs->ctx should not be used in the former, or something.
This was likely introduced by:
commit 1296423bf23c7a58133970e223b1f47ec6570308
Author: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
Date: Tue Feb 20 17:42:50 2018 -0500
drm/amd/display: define DC_LOGGER for logger
Before the commit,
clk_src->base.ctx->logger
was used in get_ss_info_from_atombios(). The commit unified all users to
use:
clk_src->ctx->logger
The former is set at the beginning of dce110_clk_src_construct() (before
the crash location). The latter only in calc_pll_max_vco_construct()
(after the crash location).
Any ideas how to fix this? Redefine DC_LOGGER to clk_src->base in
get_ss_info_from_atombios()?
I'm not sure if this is a regression and there is some underlying issue
provoking the "Invalid SS percentage" dump -- asked in the bug and
waiting for a reply.
thanks,
--
js
suse labs
next reply other threads:[~2026-07-15 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 8:51 Jiri Slaby [this message]
2026-07-15 21:52 ` amdgpu crashes in get_ss_info_from_atombios() Lakha, Bhawanpreet
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=a9ee54e6-2413-4156-9bde-d528ae3c63a3@kernel.org \
--to=jirislaby@kernel.org \
--cc=Bhawanpreet.Lakha@amd.com \
--cc=Harry.Wentland@amd.com \
--cc=Sunpeng.Li@amd.com \
--cc=Tony.Cheng@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=siqueira@igalia.com \
--cc=tzimmermann@suse.de \
/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