From: "Christian König" <christian.koenig@amd.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>,
Alex Deucher <alexander.deucher@amd.com>
Cc: Alan Liu <haoping.liu@amd.com>,
amd-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] drm/amdgpu: Avoid unnecessary Call Traces in amdgpu_irq_put()
Date: Mon, 19 Jan 2026 11:45:38 +0100 [thread overview]
Message-ID: <434e6332-2520-4ed7-9dea-8f5118dbb02e@amd.com> (raw)
In-Reply-To: <1a0dab04-cb13-9307-2853-38221193e38e@loongson.cn>
On 1/19/26 09:53, Tiezhu Yang wrote:
> On 2026/1/16 下午6:03, Christian König wrote:
>> On 1/16/26 02:20, Tiezhu Yang wrote:
>>> On 2026/1/15 下午9:47, Christian König wrote:
>>>> On 1/15/26 02:28, Tiezhu Yang wrote:
>>>>> Currently, there are many Call Traces when booting kernel on LoongArch,
>>>>> here are the trimmed kernel log messages:
>>>>>
>>>>> amdgpu 0000:07:00.0: amdgpu: hw_init of IP block <gfx_v6_0> failed -110
>>>>> amdgpu 0000:07:00.0: amdgpu: amdgpu_device_ip_init failed
>>>>> amdgpu 0000:07:00.0: amdgpu: Fatal error during GPU init
>>>>> amdgpu 0000:07:00.0: amdgpu: amdgpu: finishing device.
>>>>> ------------[ cut here ]------------
>>>>> WARNING: drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:639 at amdgpu_irq_put+0xb0/0x140 [amdgpu], CPU#0: kworker/0:0/9
>>>>> ...
>>>>> Call Trace:
>
> ...
>
>> The warning can basically only be triggered by two conditions:
>> 1. A fatal problem while loading the driver and the error handling is not 100% clean.
>> 2. A driver coding error.
>>
>> And we really need to catch all of those, so there is no real rational to limit the warning.
>>
>> I mean when you run into any of those they should potentially be fixed at some point.
>
> I did the following change and it can fix the problem, given that I am
> not familiar with amdgpu driver, could you please check it? If it is OK,
> I will send a formal patch later.
>
> ----->8-----
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c
> index 8112ffc85995..ac19565e7c45 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c
> @@ -138,6 +138,9 @@ void amdgpu_irq_disable_all(struct amdgpu_device *adev)
> if (!src || !src->funcs->set || !src->num_types)
> continue;
>
> + kfree(src->enabled_types);
> + src->enabled_types = NULL;
> +
Mhm, I need to double check that but that looks like not such a bad idea of hand.
Christian.
> for (k = 0; k < src->num_types; ++k) {
> r = src->funcs->set(adev, src, k,
>
> AMDGPU_IRQ_STATE_DISABLE);
>
> Thanks,
> Tiezhu
>
next prev parent reply other threads:[~2026-01-19 10:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 1:28 Tiezhu Yang
2026-01-15 13:47 ` Christian König
2026-01-16 1:20 ` Tiezhu Yang
2026-01-16 10:03 ` Christian König
2026-01-16 16:34 ` Alex Deucher
2026-01-19 8:53 ` Tiezhu Yang
2026-01-19 10:45 ` Christian König [this message]
2026-01-22 9:37 ` Tiezhu Yang
2026-01-22 12:53 ` Christian König
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=434e6332-2520-4ed7-9dea-8f5118dbb02e@amd.com \
--to=christian.koenig@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=haoping.liu@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yangtiezhu@loongson.cn \
/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
all inboxes | Powered by JetHome®