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


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

Bug#1035971: linux-image-6.3.0-0-amd64: IRQ warnings from amdgpu Navi 33 / Radeon RX 7700S ...

Started byDiederik de Haas <didi.debian@cknow.org>
First post2023-05-12 11:20 +0200
Last post2023-06-03 12:00 +0200
Articles 5 — 3 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#1035971: linux-image-6.3.0-0-amd64: IRQ warnings from amdgpu Navi 33 / Radeon RX 7700S ... Diederik de Haas <didi.debian@cknow.org> - 2023-05-12 11:20 +0200
    Bug#1035971: linux-image-6.3.0-0-amd64: IRQ warnings from amdgpu Navi 33 / Radeon RX 7700S ... David Reviejo <dreviejo@gmail.com> - 2023-05-18 13:00 +0200
      Bug#1035971: linux-image-6.3.0-0-amd64: IRQ warnings from amdgpu Navi 33 / Radeon RX 7700S ... Diederik de Haas <didi.debian@cknow.org> - 2023-05-18 13:30 +0200
        Bug#1035971: linux-image-6.3.0-0-amd64: IRQ warnings from amdgpu Navi 33 / Radeon RX 7700S ... Diederik de Haas <didi.debian@cknow.org> - 2023-05-18 13:40 +0200
          Bug#1035971: linux-image-6.3.0-0-amd64: IRQ warnings from amdgpu Navi 33 / Radeon RX 7700S ... Nathan Schulte <nmschulte@gmail.com> - 2023-06-03 12:00 +0200

#79038 — Bug#1035971: linux-image-6.3.0-0-amd64: IRQ warnings from amdgpu Navi 33 / Radeon RX 7700S ...

FromDiederik de Haas <didi.debian@cknow.org>
Date2023-05-12 11:20 +0200
SubjectBug#1035971: linux-image-6.3.0-0-amd64: IRQ warnings from amdgpu Navi 33 / Radeon RX 7700S ...
Message-ID<Gux6p-8kH1-5@gated-at.bofh.it>

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

On Friday, 12 May 2023 04:05:42 CEST Nathan Schulte wrote:
> amdgpu 0000:03:00.0: andgpu: Fetched VBIOS from ATRM
> amdgpu: ATOM BIOS: 113-BRT112124.001

I don't know if (or how) that^ bios can be updated, but I did see:
BIOS FA617XT.303 03/23/2023
And I did see that a 307 BIOS is available, so my first suggestion would be to 
first update to that latest BIOS.

Since this seems to be a _very_ new device, keeping an eye on BIOS updates is 
recommended as this is the time most issues will be found and hopefully fixed.
And I expect that you would need a very new kernel and 6.1 probably won't work 
(also in the future), so trying out the latest kernels could help too.

At https://salsa.debian.org/diederik/linux/-/commits/update-to-6.3.2-rt13 I'm 
working on an update to 6.3.2 (+ 6.3.1-rt13) so if you know how to 'grab' that 
and build a 6.3.2 kernel, you could try that too.

[toc] | [next] | [standalone]


#79081

FromDavid Reviejo <dreviejo@gmail.com>
Date2023-05-18 13:00 +0200
Message-ID<GwJwt-9Kbz-1@gated-at.bofh.it>
In reply to#79038
Hi, Nathan

I have similar warnings with the last longterm 6.1.27 image from
bookworm, in my case when suspending to RAM.

Seems to be an amdgpu bug introduced two or three kernel releases ago, as
you can see googling around; for example here:

https://bugzilla.redhat.com/show_bug.cgi?id=2191739

or here:

https://gitlab.freedesktop.org/drm/amd/-/issues/2522

If it's this bug, the fix seems to be in yesterday's latest upstream
kernel update: 6.3.3 (and 6.1.29 for the stable longterm).

We can only hope that the developers are not too busy with the bookworm
release to apply these patches ASAP ;)

Cheers,
-- 
David

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


#79082

FromDiederik de Haas <didi.debian@cknow.org>
Date2023-05-18 13:30 +0200
Message-ID<GwJZv-9KAQ-1@gated-at.bofh.it>
In reply to#79081

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

On Thursday, 18 May 2023 12:52:24 CEST David Reviejo wrote:
> Seems to be an amdgpu bug introduced two or three kernel releases ago, as
> you can see googling around; for example here:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=2191739
> 
> or here:
> 
> https://gitlab.freedesktop.org/drm/amd/-/issues/2522
> 
> If it's this bug, the fix seems to be in yesterday's latest upstream
> kernel update: 6.3.3 (and 6.1.29 for the stable longterm).

I _think_ I got the right commit for the 6.3 branch attached.

Para 4.5(.2) of the Debian Kernel Handbook describes how to test a simple patch:
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-common-official

Could you try that and see whether it indeed fixes your issue?

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


#79083

FromDiederik de Haas <didi.debian@cknow.org>
Date2023-05-18 13:40 +0200
Message-ID<GwK9c-9KE3-3@gated-at.bofh.it>
In reply to#79082

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

On Thursday, 18 May 2023 13:19:52 CEST Diederik de Haas wrote:
> I _think_ I got the right commit for the 6.3 branch attached.

It seems a '>' snuck in the attachment/patch as the very first char, so you may 
want to remove that.

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


#79212

FromNathan Schulte <nmschulte@gmail.com>
Date2023-06-03 12:00 +0200
Message-ID<GCwdb-dlxs-5@gated-at.bofh.it>
In reply to#79083
This patch, which now seems upstreamed, does not seem to resolve the
IRQ warnings for me.  Tried 6.3.5, and 6.4-rc4, and they persist.

On Thu, May 18, 2023 at 6:26 AM Diederik de Haas <didi.debian@cknow.org> wrote:
>
> On Thursday, 18 May 2023 13:19:52 CEST Diederik de Haas wrote:
> > I _think_ I got the right commit for the 6.3 branch attached.
>
> It seems a '>' snuck in the attachment/patch as the very first char, so you may
> want to remove that.

[toc] | [prev] | [standalone]


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


csiph-web