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

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

Bug#1142908: linux-image-6.12.85+deb13-amd64: [REGRESSION 6.12.74..6.12.85] amdgpu UVD v6 ring timeout on Polaris12/Lexa 1002:6987

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#1142908: linux-image-6.12.85+deb13-amd64: [REGRESSION 6.12.74..6.12.85] amdgpu UVD v6 ring timeout on Polaris12/Lexa 1002:6987 Salvatore Bonaccorso <carnil@debian.org> - 2026-07-27 21:50 +0200

#93479 — Bug#1142908: linux-image-6.12.85+deb13-amd64: [REGRESSION 6.12.74..6.12.85] amdgpu UVD v6 ring timeout on Polaris12/Lexa 1002:6987

Control: tags -1 + moreinfo upstream

On Mon, Jul 27, 2026 at 01:30:42PM -0600, Kai Chatterton wrote:
> Package: src:linux
> Version: 6.12.85-1
> Severity: important
> X-Debbugs-Cc: kchatt@ls.byu.edu
> 
> Dear Maintainer,
> 
> I am reporting an amdgpu regression affecting three identical Dell OptiPlex 7090 systems.
> 
> System:
> - Dell OptiPlex 7090
> - Intel Core i7, Rocket Lake generation
> 
> Integrated GPU:
> - Intel RocketLake-S GT1 / UHD Graphics 750
> - PCI ID 8086:4c8a
> - Driver: i915
> 
> Discrete GPU:
> - AMD Lexa / Polaris12
> - PCI ID 1002:6987
> - Subsystem ID 1028:1713
> - Driver: amdgpu
> 
> The last known good Debian kernel is 6.12.74+deb13+1-amd64. The
> first known bad is 6.12.85+deb13-amd64.

As you seem to fairly easy reproduce the issue, can you pleas bisect
the kernel between 6.12.74 and 6.12.85 upstream and report back which
commits breaks the usecase?

Are you familiar with bisecting the kernel or do you need instructions
on how to do it?

Regards,
Salvatore

[toc] | [standalone]

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

csiph-web