AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@sig21.net>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Alex Deucher <alexdeucher@gmail.com>, amd-gfx@lists.freedesktop.org
Subject: Re: amdgpu causes boot failure after BIOS update AGESA ComboAM5 1.3.0.1a on Asrock X600
Date: Tue, 6 Oct 2026 20:49:35 +0200	[thread overview]
Message-ID: <asVCvyFPc9QagfLL@sig21.net> (raw)
In-Reply-To: <asCs8oMOdN56x2tk@sig21.net>

On Sat, Oct 03, 2026 at 09:21:22AM +0200, Johannes Stezenbach wrote:
> On Fri, Oct 02, 2026 at 07:18:31PM -0500, Mario Limonciello wrote:
> > Here's your first indication of a problem:
> > 
> > [   13.423543] amdgpu 0000:6e:00.0: [drm:amdgpu_ring_test_helper [amdgpu]]
> > *ERROR* ring mes_kiq_3.1.0 test failed (-110)
> > [   13.423719] amdgpu 0000:6e:00.0: hw_init of IP block <gfx_v11_0> failed
> > -110
> > [   13.423723] amdgpu 0000:6e:00.0: amdgpu_device_ip_init failed
> > [   13.423727] amdgpu 0000:6e:00.0: Fatal error during GPU init
> > [   13.423732] amdgpu 0000:6e:00.0: finishing device.
> > 
> > Basically there is a graphics ring buffer test that happens and fails.
> > Then the hardware init fails as a result of that failing.
> > 
> > From your logs the notable versions:
> > [    0.414349] AGESA: AGESA!V9 ComboAm5PI 1.3.0.1a
> > and
> > smu fw version = 0x004c6700 (76.103.0)
> > 
> > Was the only think you changed BIOS?  Or did you happen to upgrade
> > linux-firmware recently too and that could have been the cause?
> > 
> > Can you downgrade back to existing BIOS and see if it's OK?
> 
> Everything gets updated all the time since this is
> a rolling distribution. However, I encountered the
> problem already a few weeks ago but had to put it aside since
> I had work to do. Downgrading the BIOS had resolved the problem.
> I've been using a 7.2.6 kernel with the old BIOS for daily
> work without problems. Prior to this BIOS update now I upgraded
> the kernel to 7.2.8 and confirmed it can boot with the old BIOS.
> 
> FWIW, other Asrock boards got AGESA ComboAM5 1.3.0.1b Patch A
> recently, but the mini-PC product line seem to be always
> notoriously late in getting BIOS updates.

What's your idea about this, is there anything you want me
to try or shall I just give up on this and go back to the
working BIOS version?


Thanks,
Johannes

      reply	other threads:[~2026-10-07 13:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 10:26 amdgpu causes boot failure after BIOS update AGESA ComboAM5 1.3.0.1a on Asrock X600 Johannes Stezenbach
2026-10-02 15:47 ` Alex Deucher
2026-10-02 16:12   ` Mario Limonciello
2026-10-02 19:25     ` Johannes Stezenbach
2026-10-02 19:33       ` Johannes Stezenbach
2026-10-03  0:18       ` Mario Limonciello
2026-10-03  7:21         ` Johannes Stezenbach
2026-10-06 18:49           ` Johannes Stezenbach [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=asVCvyFPc9QagfLL@sig21.net \
    --to=js@sig21.net \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=mario.limonciello@amd.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