mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tj <tj.iam.tj@proton.me>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
	regressions@lists.linux.dev
Cc: amd-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	"Timur Kristóf" <timur.kristof@gmail.com>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>
Subject: Re: [REGRESSION] RIP: 0010:vce_v1_0_set_powergating_state+0x5b8/0x600 [amdgpu]
Date: Tue, 02 Jun 2026 11:23:57 +0000	[thread overview]
Message-ID: <43123501-2119-4ac6-b1cd-e59dfe6dca89@proton.me> (raw)
In-Reply-To: <59f38ae7-2d5a-4dcf-bff9-7e58c36f36d4@leemhuis.info>

v7.1-rc6 +  "drm/amdgpu: Align amdgpu_gtt_mgr entries to TLB size on all 
SI" and confirmed resolves this issue. Thank-you.
On 02/06/2026 10:22, Thorsten Leemhuis wrote:
> On 6/2/26 12:06, Tj wrote:
>> Repeatedly hit this with 7.1-rc6. I haven't yet got time to do a bisect.
>>
>> $ lspci -nnk -d ::0300
>> 0a:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde GL [FirePro W4100] [1002:682c]
>>          Subsystem: Dell Device [1028:2b1e]
>>          Kernel driver in use: amdgpu
>>          Kernel modules: radeon, amdgpu
>>
>> $ journalctl --boot 5e39a2d49af2432c8f14f2a866a6b275 --priority=warning
>> ...
>> Jun 02 09:25:11 sunny kernel: Linux version 7.1.0-rc6+debian+tj (linux@iam.tj) (gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44) #446 SMP PREEMPT_DYNAMIC Mon Jun  1 07:32:2>
>> ...
>> Jun 02 09:25:11 sunny kernel: WARNING: drivers/gpu/drm/amd/amdgpu/vce_v1_0.c:329 at vce_v1_0_set_powergating_state+0x5b8/0x600 [amdgpu], CPU#8: (udev-worker)/251
> Thx for reporting this. This is not my area of expertise, but from a
> very quick look that seems to be the issue
> https://gitlab.freedesktop.org/drm/amd/-/work_items/5336
> for which Timur sent a fix:
>
> drm/amdgpu: Align amdgpu_gtt_mgr entries to TLB size on all SI
> https://lore.kernel.org/all/20260525112204.12604-1-timur.kristof@gmail.com/
>
> According to Alex it's making it's way through the ranks. Consider
> testing it to ensure it really is the same problem.


      parent reply	other threads:[~2026-06-02 11:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02 10:06 Tj
2026-06-02 10:22 ` Thorsten Leemhuis
2026-06-02 10:29   ` Tj
2026-06-02 11:23   ` Tj [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=43123501-2119-4ac6-b1cd-e59dfe6dca89@proton.me \
    --to=tj.iam.tj@proton.me \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=timur.kristof@gmail.com \
    /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®