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

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

Bug#1125155: Firmware issue; upstream workaround WIP

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#1125155: Firmware issue; upstream workaround WIP Tj <tj.iam.tj@proton.me> - 2026-01-29 08:20 +0100
    Bug#1125155: Firmware issue; upstream workaround WIP Felix Zielcke <fzielcke@z-51.de> - 2026-09-13 11:40 +0200
      Bug#1125155: Firmware issue; upstream workaround WIP Salvatore Bonaccorso <carnil@debian.org> - 2026-09-22 21:20 +0200

#91000 — Bug#1125155: Firmware issue; upstream workaround WIP

Followup-For: Bug #1125155
X-Debbugs-Cc: tj.iam.tj@proton.me

Olivier:

amdgpu 0000:03:00.0: [drm] *ERROR* [CRTC:91:crtc-0] flip_done timed out
[drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:91:crtc-0] hw_done 
or flip_done timed out

This is almost always a symptom of a failure of the GPU's firmware.
These GPUs consist of many "IP blocks" (Intellectual Property) - better 
known as firmware - for the
different functions each 'block' provides.

The error is telling us the driver is waiting for an acknowledgement 
from the GPU firmware but it never arrives.

In most cases it would require the firmware/block to be reset and 
restarted to regain functionality.

The causes of these errors across a vast number of AMD GPUs are not
understood even by the AMD Linux GPU developers!

  Recently though there's an initiative to try to deal with the symptom 
by identifying where the
problem is and restarting the IP block.

We'll have to wait and hope they follow through and we get a commit that 
can also be back-ported.

See https://lkml.org/lkml/2026/1/22/2079

I build and run latest mainline (currently on 6.19.0-rc7+debian+tj) and
see the flip_done timeout occassionally so if the thread leads to a
usuable patch I'll be testing it.

Tj.

[toc] | [next] | [standalone]

#94080

On Wed, 28 Jan 2026 21:48:39 +0000 Tj <tj.iam.tj@proton.me> wrote:
> 
> amdgpu 0000:03:00.0: [drm] *ERROR* [CRTC:91:crtc-0] flip_done timed
out
> [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:91:crtc-0]
hw_done 
> or flip_done timed out
> 
> This is almost always a symptom of a failure of the GPU's firmware.

[...]

> We'll have to wait and hope they follow through and we get a commit
that 
> can also be back-ported.
> 
> See https://lkml.org/lkml/2026/1/22/2079
> 
> I build and run latest mainline (currently on 6.19.0-rc7+debian+tj)
and
> see the flip_done timeout occassionally so if the thread leads to a
> usuable patch I'll be testing it.
> 
> Tj.

Hi,

I switched 3 months ago as a long time Nvidia user to a 
AMD Radeon 9060 XT
I'm using alway up2date unstable. 
I didn't have this problem in the beginning. But recently (I guess
since Linux 7.1.x) this happens regularly.

Is there some upstream bug or so to follow?

Felix

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

#94173

Hi Felix,

On Sun, Sep 13, 2026 at 11:32:34AM +0200, Felix Zielcke wrote:
> On Wed, 28 Jan 2026 21:48:39 +0000 Tj <tj.iam.tj@proton.me> wrote:
> > 
> > amdgpu 0000:03:00.0: [drm] *ERROR* [CRTC:91:crtc-0] flip_done timed
> out
> > [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:91:crtc-0]
> hw_done 
> > or flip_done timed out
> > 
> > This is almost always a symptom of a failure of the GPU's firmware.
> 
> [...]
> 
> > We'll have to wait and hope they follow through and we get a commit
> that 
> > can also be back-ported.
> > 
> > See https://lkml.org/lkml/2026/1/22/2079
> > 
> > I build and run latest mainline (currently on 6.19.0-rc7+debian+tj)
> and
> > see the flip_done timeout occassionally so if the thread leads to a
> > usuable patch I'll be testing it.
> > 
> > Tj.
> 
> Hi,
> 
> I switched 3 months ago as a long time Nvidia user to a 
> AMD Radeon 9060 XT
> I'm using alway up2date unstable. 
> I didn't have this problem in the beginning. But recently (I guess
> since Linux 7.1.x) this happens regularly.
> 
> Is there some upstream bug or so to follow?

I think there is some potential the original reporters issue and yours
might be distinct, can you fill please a separate bug about your issue
with reportbug, so we get as well the required information collected
by the bugscripts?

Thanks already!

Regards,
Salvatore

[toc] | [prev] | [standalone]

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

csiph-web