Seems the following behavior started after dnf update to the 6.18
kernel and all subsequent minor revs.

After initial startup or after reboot, Chromium-based browsers start
and run fine. Second attempt results in following, only resolved
with another reboot:


user@localhost:~$ google-chrome-stable
radeon: Failed to allocate virtual address for buffer:
radeon:    size      : 65536 bytes
radeon:    alignment : 4096 bytes
radeon:    domains   : 4
radeon:    va        : 0x0000000100000000
radeon: Failed to deallocate virtual address for buffer:
radeon:    size      : 65536 bytes
radeon:    va        : 0x100000000
radeon: Failed to allocate virtual address for buffer:
radeon:    size      : 65536 bytes
radeon:    alignment : 4096 bytes
radeon:    domains   : 4
radeon:    va        : 0x0000000100000000
radeon: Failed to deallocate virtual address for buffer:
radeon:    size      : 65536 bytes
radeon:    va        : 0x100000000
radeonsi: error: can't create border_color_buffer
radeonsi: error: Failed to create a context.
Created TensorFlow Lite XNNPACK delegate for CPU.
[9095:9095:0125/123845.017117:ERROR:content/browser/gpu/gpu_process_host.cc:1004]
GPU process exited unexpectedly: exit_code=139
radeon: Failed to allocate virtual address for buffer:
radeon:    size      : 65536 bytes
radeon:    alignment : 4096 bytes
radeon:    domains   : 4
radeon:    va        : 0x0000000100000000
radeon: Failed to deallocate virtual address for buffer:
radeon:    size      : 65536 bytes
radeon:    va        : 0x100000000
radeon: Failed to allocate virtual address for buffer:
radeon:    size      : 65536 bytes
radeon:    alignment : 4096 bytes
radeon:    domains   : 4
radeon:    va        : 0x0000000100000000
radeon: Failed to deallocate virtual address for buffer:
radeon:    size      : 65536 bytes
radeon:    va        : 0x100000000
radeonsi: error: can't create border_color_buffer
radeonsi: error: Failed to create a context.
[9095:9095:0125/123846.859251:ERROR:content/browser/gpu/gpu_process_host.cc:1004]
GPU process exited unexpectedly: exit_code=139
radeon: Failed to allocate virtual address for buffer:
radeon:    size      : 65536 bytes
radeon:    alignment : 4096 bytes
radeon:    domains   : 4
radeon:    va        : 0x0000000100000000
radeon: Failed to deallocate virtual address for buffer:
radeon:    size      : 65536 bytes
radeon:    va        : 0x100000000
radeon: Failed to allocate virtual address for buffer:
radeon:    size      : 65536 bytes
radeon:    alignment : 4096 bytes
radeon:    domains   : 4
radeon:    va        : 0x0000000100000000
radeon: Failed to deallocate virtual address for buffer:
radeon:    size      : 65536 bytes
radeon:    va        : 0x100000000
radeonsi: error: can't create border_color_buffer
radeonsi: error: Failed to create a context.
[9095:9095:0125/123848.665358:ERROR:content/browser/gpu/gpu_process_host.cc:1004]
GPU process exited unexpectedly: exit_code=139
[9095:9095:0125/123848.665415:FATAL:content/browser/gpu/gpu_data_manager_impl_private.cc:415]
GPU process isn't usable. Goodbye.
[0125/123848.708552:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64]
tag not found
[0125/123848.710446:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64]
tag not found
[0125/123848.712883:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64]
tag not found
[0125/123848.713955:ERROR:third_party/crashpad/crashpad/snapshot/elf/elf_dynamic_array_reader.h:64]
tag not found
Trace/breakpoint trap      (core dumped) google-chrome-stable

user@localhost:~$ lspci -k | grep -EA3 'VGA|3D|Display'
00:02.0 VGA compatible controller: Intel Corporation Skylake-H GT2 [HD
Graphics 530] (rev 06)
        DeviceName:  Onboard IGD
        Subsystem: Dell Device 06e0
        Kernel driver in use: i915
--
01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape
Verde PRO / Venus LE / Tropo PRO-L [Radeon HD 8830M / R7 250 / R7 M465X] (rev 
87)
        Subsystem: Dell Device 06e0
        Kernel driver in use: radeon
        Kernel modules: radeon, amdgpu

user@localhost:~$ sudo lshw -C display
[sudo] password for user:
   *-display
        description: Display controller
        product: Cape Verde PRO / Venus LE / Tropo PRO-L [Radeon HD
8830M / R7 250 / R7 M465X]
        vendor: Advanced Micro Devices, Inc. [AMD/ATI]
        physical id: 0
        bus info: pci@0000:01:00.0
        version: 87
        width: 64 bits
        clock: 33MHz
        capabilities: pm pciexpress msi bus_master cap_list rom
        configuration: driver=radeon latency=0
        resources: irq:140 memory:c0000000-cfffffff
memory:ec300000-ec33ffff ioport:e000(size=256) memory:ec340000-ec35ffff
   *-display
        description: VGA compatible controller
        product: Skylake-H GT2 [HD Graphics 530]
        vendor: Intel Corporation
        physical id: 2
        bus info: pci@0000:00:02.0
        version: 06
        width: 64 bits
        clock: 33MHz
        capabilities: pciexpress msi pm vga_controller bus_master
cap_list rom
        configuration: driver=i915 latency=0
        resources: irq:141 memory:eb000000-ebffffff
memory:80000000-8fffffff ioport:f000(size=64) memory:c0000-dffff

user@localhost:~$ uname -a
Linux localhost 6.18.6-200.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Jan
18 18:57:00 UTC 2026 x86_64 GNU/Linux

user@localhost:~$ printf 'Desktop: %s\nSession: %s\n'
"$XDG_CURRENT_DESKTOP" "$GDMSESSION"
Desktop: X-Cinnamon
Session: cinnamon


What I've done based on Ms. Google's suggestions (all no-joy, same
result):

-Start in incognito mode
-Move .config/google-chrome folder(s) and remove profiles
-dnf remove google-chrome-stable and reinstall
-Disable hardware acceleration in Chrome

Mozilla browsers work as expected.

Suggestions on what to do next? Seems it's a radeon driver thing to my
untrained eye? Is this a kernel or driver bug that needs to be filed?

Thanks - Glenn

I'm using KDE, and thinking Chrome wasn't already installed I ran "sudo dnf install chrome", which installed chromedriver. After installation I ran google-chrome-stable in a konsole session and even though I produced lots of error in the terminal window it still started up quite happily. I did this 3 times and got the same results every time on kernel 6.18.15. I've also just installed 6.18.6, but I haven't tested that yet.

regards,

BEGIN:VCARD
VERSION:4.0
N:Morris;Stephen;;;
FN:Stephen Morris
EMAIL;PREF=1;TYPE=home:[email protected]
END:VCARD
-- 
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to