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: Fri, 30 Oct 2026 11:03:40 +0100 [thread overview]
Message-ID: <auRrfMntlpc6rGhK@sig21.net> (raw)
In-Reply-To: <atCaRZrxxcz4xRje@sig21.net>
On Thu, Oct 15, 2026 at 11:17:57AM +0200, Johannes Stezenbach wrote:
> On Fri, Oct 02, 2026 at 09:25:22PM +0200, Johannes Stezenbach wrote:
> > However, my self-built kernel still crashes early after I changed
> > amdgpu to be a loadable module. So there is something else going
> > on, but lets concentrate on the andgpu failure with the Debian kernel.
>
> I was able to resolve this. I went through my kernel config and
> compared to Debian's and found the following suspicious
> configurations that had worked with previous BIOS v4.14:
>
> CONFIG_PCIEASPM_POWER_SUPERSAVE (should be CONFIG_PCIEASPM_DEFAULT)
> CONFIG_EFI_DISABLE_PCI_DMA
> CONFIG_EFI_DISABLE_RUNTIME
>
> After disabling them my kernel can boot and runs stable.
So I thought. But I had also enabled EFI_STUB because the
Debian kernel had it, but it causes "failed to unprotect
memory range at..." messages. Thus now after kernel upgrade
to 7.2.13 I disabled it -> can't boot.
Setting this is needed with BIOS v4.23:
CONFIG_EFI_STUB=y
CONFIG_EFI_HANDOVER_PROTOCOL=y (maybe, =n not tested)
Johannes
prev parent reply other threads:[~2026-10-30 14:27 UTC|newest]
Thread overview: 10+ 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
2026-10-15 9:17 ` Johannes Stezenbach
2026-10-30 10:03 ` 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=auRrfMntlpc6rGhK@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