[Bug 220512] New: The amdgpu driver fails to initialize my dedicated Navi33 GPU at boot, logging a "Fatal error during GPU init" and "gmc_v11_0 failed" despite using the most recent kernels.

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=220512

            Bug ID: 220512
           Summary: The amdgpu driver fails to initialize my dedicated
                    Navi33 GPU at boot, logging a "Fatal error during GPU
                    init" and "gmc_v11_0 failed" despite using the most
                    recent kernels.
           Product: Drivers
           Version: 2.5
          Hardware: AMD
                OS: Linux
            Status: NEW
          Severity: high
          Priority: P3
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: ricardo1529@gmail.com
        Regression: No

Created attachment 308574
  --> https://bugzilla.kernel.org/attachment.cgi?id=308574&action=edit
various logs combined into one file because i can't upload more than one or
don't know any other way to upload more than one log

My system, which has an AMD APU and a dedicated AMD GPU (Navi33), fails to
initialize the dedicated GPU. The system boots successfully and uses the
integrated GPU, but the dedicated card is not functional. This issue persists
even on the latest linux-image-liquorix kernel.

Steps to Reproduce:

    Boot the system with the dedicated AMD GPU installed.

    Start the Linux kernel (the issue persists across recent kernels, including
the latest from the Liquorix repository).

Expected Behavior:
The amdgpu kernel driver should initialize the Navi33 dGPU, enabling it for
graphical output and compute tasks. The dGPU should be listed by lspci and
appear in the X.Org log and other system tools as a functional device.

Actual Behavior:
The kernel logs show a fatal error during the amdgpu driver's initialization of
the dGPU. The boot process continues, but the dGPU remains inactive, and the
system relies on the integrated graphics. The dmesg output shows the following
key errors:

[drm:amdgpu_bo_init [amdgpu]] *ERROR* Unable to set WC memtype for the aperture
base
[drm:amdgpu_device_init.cold [amdgpu]] *ERROR* sw_init of IP block <gmc_v11_0>
failed -22
amdgpu 0000:03:00.0: amdgpu: Fatal error during GPU init
amdgpu 0000:03:00.0: amdgpu: amdgpu: finishing device.
amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22

The error appears to be a low-level initialization failure related to the
gmc_v11_0 IP block, which is the Graphics Memory Controller. The "Unable to set
WC memtype" error suggests a problem with setting up the write-combining memory
aperture for the GPU.

System Details:

    CPU: ryzen  7 7700x

    Motherboard: ASUS TUF GAMING B850-PLUS WIFI

    BIOS Version: 1079

    Integrated GPU (iGPU): AMD AMD Radeon™ Graphics, which is working
correctly.

    Dedicated GPU (dGPU): AMD rx 7600xt (Navi33)

    Kernel Version: Linux debian 6.16.3-1-liquorix-amd64 #1 ZEN SMP
PREEMPT_DYNAMIC liquorix 6.16-2.1~sid (2025-08-24) x86_64 GNU/Linux

    Distribution: Debian Trixie

    Boot Parameters: audit=0 intel_pstate=disable amd_pstate=disable 
BOOT_IMAGE=/boot/vmlinuz-6.16.3-1-liquorix-amd64
root=UUID=acec125d-fb52-4e62-a417-7d8e976e34f7 ro quiet
usbcore.quirks=1-6:hub_port_remap,13d3:3602:no-auto-suspend


Additional Notes:

    I have confirmed this behavior on both the standard Debian kernel and a
newer Liquorix kernel, suggesting the issue is not specific to a single kernel
package version.

    The system functions normally when using the iGPU

attached various bug report logs combined into one

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.