Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #93715 > unrolled thread

Bug#1142158: Fwd: Fwd: linux-image-7.0.13+deb13-amd64: This appears similar to #1104269 but affects a Radeon RX 9060 XT (RDNA4) on Debian 13 with kernel 7.0.13 from backports. Unlike earlier reports, the known workarounds (amdgpu.dcdebugmask=0x10, 0x12, amdgpu.runpm=0) do not mitigate the issue. In recent occurrences it required a hard reset.

Started byYunseong Kim <ysk@kzalloc.com>
First post2026-08-13 11:30 +0200
Last post2026-08-22 15:20 +0200
Articles 3 — 2 participants

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#1142158: Fwd: Fwd: linux-image-7.0.13+deb13-amd64: This appears similar to #1104269 but affects a Radeon RX 9060 XT (RDNA4) on Debian 13 with kernel 7.0.13 from backports. Unlike earlier reports, the known workarounds (amdgpu.dcdebugmask=0x10, 0x12, amdgpu.runpm=0) do not mitigate the issue. In recent occurrences it required a hard reset. Yunseong Kim <ysk@kzalloc.com> - 2026-08-13 11:30 +0200
    Bug#1142158: Fwd: Fwd: linux-image-7.0.13+deb13-amd64: This appears similar to #1104269 but affects a Radeon RX 9060 XT (RDNA4) on Debian 13 with kernel 7.0.13 from backports. Unlike earlier reports, the known workarounds (amdgpu.dcdebugmask=0x10, 0x12, amdgpu.runpm=0) do not mitigate the issue. In recent occurrences it required a hard reset. Salvatore Bonaccorso <carnil@debian.org> - 2026-08-19 15:20 +0200
      Bug#1142158: Fwd: Fwd: linux-image-7.0.13+deb13-amd64: This appears similar to #1104269 but affects a Radeon RX 9060 XT (RDNA4) on Debian 13 with kernel 7.0.13 from backports. Unlike earlier reports, the known workarounds (amdgpu.dcdebugmask=0x10, 0x12, amdgpu.runpm=0) do not mitigate the issue. In recent occurrences it required a hard reset. Salvatore Bonaccorso <carnil@debian.org> - 2026-08-22 15:20 +0200

#93715 — Bug#1142158: Fwd: Fwd: linux-image-7.0.13+deb13-amd64: This appears similar to #1104269 but affects a Radeon RX 9060 XT (RDNA4) on Debian 13 with kernel 7.0.13 from backports. Unlike earlier reports, the known workarounds (amdgpu.dcdebugmask=0x10, 0x12, amdgpu.runpm=0) do not mitigate the issue. In recent occurrences it required a hard reset.

FromYunseong Kim <ysk@kzalloc.com>
Date2026-08-13 11:30 +0200
SubjectBug#1142158: Fwd: Fwd: linux-image-7.0.13+deb13-amd64: This appears similar to #1104269 but affects a Radeon RX 9060 XT (RDNA4) on Debian 13 with kernel 7.0.13 from backports. Unlike earlier reports, the known workarounds (amdgpu.dcdebugmask=0x10, 0x12, amdgpu.runpm=0) do not mitigate the issue. In recent occurrences it required a hard reset.
Message-ID<NrzV7-aEYA-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

-------- Forwarded Message --------
Subject: 	Re: Fwd: linux-image-7.0.13+deb13-amd64: This appears similar
to #1104269 but affects a Radeon RX 9060 XT (RDNA4) on Debian 13 with
kernel 7.0.13 from backports. Unlike earlier reports, the known
workarounds (amdgpu.dcdebugmask=0x10, 0x12, amdgpu.runpm=0) do not
mitigate the issue. In recent occurrences it required a hard reset.
Date: 	Wed, 12 Aug 2026 20:22:14 -0300
From: 	Gabriel Elias de Aquino <gabriel.aquino86@gmail.com>
To: 	Yunseong Kim <ysk@kzalloc.com>



Hi Yunseong,


I didn't test it without the workaround yet, but I've received a new
update from the amdgpu maintainer and he informed me that the issue was
fixed in *6.18.44*, *7.1.8* and *7.2-rc7*.


Guess I'll wait for the 7.1.8 version to be shipped in trixie-backports
just in case.


Best regards,
-- 

Gabriel Elias de Aquino

*gabriel.aquino86@gmail.com*

[toc] | [next] | [standalone]


#93793

FromSalvatore Bonaccorso <carnil@debian.org>
Date2026-08-19 15:20 +0200
Message-ID<NtOmZ-bTpk-9@gated-at.bofh.it>
In reply to#93715
Hi Gabriel,

On Thu, Aug 13, 2026 at 11:25:53AM +0200, Yunseong Kim wrote:
> Hi Yunseong,
> 
> 
> I didn't test it without the workaround yet, but I've received a new
> update from the amdgpu maintainer and he informed me that the issue was
> fixed in *6.18.44*, *7.1.8* and *7.2-rc7*.
> 
> 
> Guess I'll wait for the 7.1.8 version to be shipped in trixie-backports
> just in case.

Would it be an option/possible for you to rather just fetch the update
from testing already so we can confirm it is fixed in 7.1.8?
Otherwise,  7.1.8-1~bpo13+1 is pending to be processed.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]


#93848

FromSalvatore Bonaccorso <carnil@debian.org>
Date2026-08-22 15:20 +0200
Message-ID<NuTND-cw7M-7@gated-at.bofh.it>
In reply to#93793
Hi Gabriel,

On Wed, Aug 19, 2026 at 03:09:45PM +0200, Salvatore Bonaccorso wrote:
> Hi Gabriel,
> 
> On Thu, Aug 13, 2026 at 11:25:53AM +0200, Yunseong Kim wrote:
> > Hi Yunseong,
> > 
> > 
> > I didn't test it without the workaround yet, but I've received a new
> > update from the amdgpu maintainer and he informed me that the issue was
> > fixed in *6.18.44*, *7.1.8* and *7.2-rc7*.
> > 
> > 
> > Guess I'll wait for the 7.1.8 version to be shipped in trixie-backports
> > just in case.
> 
> Would it be an option/possible for you to rather just fetch the update
> from testing already so we can confirm it is fixed in 7.1.8?
> Otherwise,  7.1.8-1~bpo13+1 is pending to be processed.

7.1.8-1~bpo13+1 is now as well available in trixie-backports, can you
please test it and report back if the issue is fixed?

Regards,
Salvatore

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web