Bug 2405284 - Corrupted graphics, broken acceleration on some AMD APUs/GPUs with Chromium 141.0.7390.65
Summary: Corrupted graphics, broken acceleration on some AMD APUs/GPUs with Chromium 1...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: chromium
Version: 42
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL: https://discussion.fedoraproject.org/...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-21 06:36 UTC by Federico Leva
Modified: 2025-10-22 15:03 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)
/etc/chromium/chromium.conf with chromium-141.0.7390.54-1.fc41.x86_64 (2.12 KB, text/plain)
2025-10-22 15:03 UTC, Federico Leva
no flags Details

Description Federico Leva 2025-10-21 06:36:24 UTC
Chromium 141.0.7390.65 is unusable on my AMD A8-7600 PC, while chromium-141.0.7390.54-1 works just fine. Immediately at launch, the window displays some graphic corruption like green bands, and input is so laggy I can barely type "about://gpu". These errors appear to be related:

```

    $ LANG=en_US chromium-browser
    Warning: ../src/amd/vulkan/radv_physical_device.c:2041: Device ‘/dev/dri/renderD128’ is not using the AMDGPU kernel driver: Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER)
    [11692:11729:1013/154641.544102:ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
    Warning: maxDynamicUniformBuffersPerPipelineLayout artificially reduced from 500000 to 16 to fit dynamic offset allocation limit.
    Warning: maxDynamicStorageBuffersPerPipelineLayout artificially reduced from 500000 to 16 to fit dynamic offset allocation limit.
    [11754:11754:1013/154641.567985:ERROR:ui/gl/egl_util.cc:92] EGL Driver message (Error) eglCreateContext: Requested version is not supported
    Warning: eglCreateContext failed with EGL_BAD_ATTRIBUTE

        While trying to discover a BackendType::OpenGL adapter.
        at CheckEGL (../../third_party/dawn/src/dawn/native/opengl/UtilsEGL.cpp:98)

    Warning: maxDynamicUniformBuffersPerPipelineLayout artificially reduced from 72 to 16 to fit dynamic offset allocation limit.
    Warning: maxDynamicStorageBuffersPerPipelineLayout artificially reduced from 64 to 16 to fit dynamic offset allocation limit.

```

The functioning version only prints these (not in this order).

```

ERROR:components/dbus/xdg/request.cc:165] Request cancelled by user.
ERROR:components/viz/service/gl/exit_code.cc:13] Restarting GPU process due to unrecoverable error. Context was lost.
ERROR:content/browser/gpu/gpu_process_host.cc:970] GPU process exited unexpectedly: exit_code=8704
ERROR:google_apis/gcm/engine/registration_request.cc:291] Registration response error message: DEPRECATED_ENDPOINT
ERROR:gpu/command_buffer/service/shared_image/shared_image_factory.cc:940] CreateSharedImage: could not create backing.
ERROR:gpu/command_buffer/service/shared_image/shared_image_manager.cc:389] SharedImageManager::ProduceSkia: Trying to Produce a Skia representation from a non-existent mailbox.
ERROR:gpu/ipc/client/command_buffer_proxy_impl.cc:128] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
ERROR:ui/base/accelerators/global_accelerator_listener/global_accelerator_listener_linux.cc:285] Failed to call BindShortcuts (error code 4).
ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:83] Cannot create bo with format= RGBA_8888 and usage=Scanout|Rendering|Texturing
ERROR:ui/ozone/platform/wayland/gpu/gbm_pixmap_wayland.cc:83] Cannot create bo with format= RGBA_8888 and usage=Texturing

```

The discussion at https://discussion.fedoraproject.org/t/wayland-and-chromium-brave-gpu-acceleration-is-suddenly-broken-videos-hella-laggy/167520/18 has different users with slightly different issues, it's not clear if the root cause of my issue is the same as theirs.

Reproducible: Always

Steps to Reproduce:
1. Install chromium 141.0.7390.65 on an AMD A8-7600
2. Launch chromium
Actual Results:
Warnings about acceleration printed, graphics corrupted.

Expected Results:
No graphic corruption

Additional Information:
There were some problems with AMD A8-7600 in mesa drivers version 25.0, which were since resolved. The issue did not appear in connection with a mesa upgrade and a downgrade didn't help. Using an earlier kernel also didn't help. I've not tried switching away from Wayland.

My system information:

$ uname -a
Linux a88x 6.16.10-200.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Oct  2 19:23:55 UTC 2025 x86_64 GNU/Linux
$ rpm -qa *mesa-dri*
mesa-dri-drivers-25.1.9-1.fc42.x86_64
$ chromium-browser --version
Chromium 141.0.7390.65 Fedora Project
$ lsmod | grep amdgpu 
amdgpu              20701184  0
amdxcp                 12288  1 amdgpu
gpu_sched              65536  1 amdgpu
drm_panel_backlight_quirks    12288  1 amdgpu
drm_buddy              32768  1 amdgpu
drm_ttm_helper         16384  2 amdgpu,radeon
ttm                   135168  3 amdgpu,radeon,drm_ttm_helper
drm_exec               12288  2 amdgpu,radeon
i2c_algo_bit           20480  2 amdgpu,radeon
drm_suballoc_helper    20480  2 amdgpu,radeon
drm_display_helper    327680  2 amdgpu,radeon
cec                   106496  2 drm_display_helper,amdgpu
video                  81920  2 amdgpu,radeon
$ inxi -Gx
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Kaveri [Radeon R7 Graphics]
    driver: radeon v: kernel arch: GCN-2 bus-ID: 00:01.0
  Display: wayland server: Xwayland v: 24.1.8 compositor: kwin_wayland
    driver: X: loaded: radeon unloaded: fbdev,modesetting,vesa dri: radeonsi
    gpu: radeon resolution: 1920x1080~60Hz
  API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast platforms:
    active: gbm,wayland,x11,surfaceless,device inactive: N/A
  API: OpenGL v: 4.5 vendor: amd mesa v: 25.1.9 glx-v: 1.4
    direct-render: yes renderer: KAVERI (radeonsi ACO DRM 2.50
    6.16.10-200.fc42.x86_64)
  API: Vulkan v: 1.4.313 drivers: llvmpipe surfaces: N/A devices: 1
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdriinfo,
    xdpyinfo, xprop, xrandr

Comment 1 Than Ngo 2025-10-22 12:44:05 UTC
I have made some changes in /etc/chromium/chromium.conf in version 141.0.7390.65, It could be that this change causes problem in your case.

Could you please attach your /etc/chromium/chromium.conf file here so i can have a look at it?

Thank you!

Comment 2 Federico Leva 2025-10-22 15:03:52 UTC
Created attachment 2110470 [details]
/etc/chromium/chromium.conf with chromium-141.0.7390.54-1.fc41.x86_64

(In reply to Than Ngo from comment #1)
> Could you please attach your /etc/chromium/chromium.conf file here so i can
> have a look at it?

Thanks for looking into this! Currently it's like this, but I don't know what it was before I downgraded chromium. Should I test upgrading again?


Note You need to log in before you can comment on or make changes to this bug.