Hardware acceleration not working since recent kernel update

ndavid · 2023-12-11 19:21:31

Updated my Arch to 6.6.6 a few hours ago and recently noticed that hardware acceleration is not working in my browser (seems to be using CPU even though hardware acceleration is on).
Was working fine at least a few days ago, haven't downgraded the kernel ever so I haven't been able to check whether it is the source of the problem.
Also noticed a very recent Reddit post talking about broken hardware acceleration in a different context: https://www.reddit.com/r/obs/comments/1 … esnt_work/

My specs:
Kernel: 6.6.6-arch1-1
CPU: AMD Ryzen 5 5600H with Radeon Graphics (12) @ 4.280GHz
GPU: NVIDIA GeForce RTX 3060 Mobile / Max-Q

seth · 2023-12-11 21:07:51

seems to be using CPU even though hardware acceleration is on

Seems by what metric and in what context?
For video playback, brace yourself: https://bbs.archlinux.org/viewtopic.php?id=244031&p=38

Otherwise, what display server, if wayland, native or xwayland, https://wiki.archlinux.org/title/Chromi … nd_support

glxinfo -B

And what does "chrome://gpu" report?

ndavid · 2023-12-11 21:17:44

Hello. I'm on X11. I've been with the exact same setup and a few days ago hardware acceleration was working.
Now I get freezes if a lot of tabs are open (around 10 or so) and web apps like Figma are crashing.

gpu report from the browser: https://pastebin.com/5zXn6gtu

ndavid · 2023-12-11 21:30:27

Also worth noting that I even tried in a different browser (I'm currently on Brave). So I installed Chromium and got exactly the same issue.

seth · 2023-12-11 21:30:48

The browser very much thinks it's using HW acceleration and detects the 545xx nvidia driver

Now I get freezes if a lot of tabs are open (around 10 or so) and web apps like Figma are crashing.

What doesn't mean you're rendering on the CPU.
Do you have a backtrace for the crash(es)?
https://wiki.archlinux.org/title/Core_d … _core_dump

Edit:

a few days ago [stuff] was working

Maybe also post the relevant part of your pacman log.
Do things still work w/ the LTS kernel?

Last edited by seth (2023-12-11 21:32:06)

ndavid · 2023-12-11 21:38:52

Do you have a backtrace for the crash(es)?
https://wiki.archlinux.org/title/Core_d … _core_dump

The crashes happened on the browser, not the kernel.

Do things still work w/ the LTS kernel?

I tested it and no they don't work there either.

BTW, do you have similar hardware? If so, could you try to reproduce? Literally with any web app that uses gpu stuff, Figma, phew I even have my own which is where I first noticed it https://ncube.ndavd.com

seth · 2023-12-11 21:43:50

The crashes happened on the browser, not the kernel.

Which is why they might have left a coredump…

*every* "web app […] uses gpu stuff"

seth wrote:

Maybe also post the relevant part of your pacman log.

Also check your system journal, nvidia driver errors will often produce xid errors.

ndavid · 2023-12-11 21:59:54

The browser itself didn't crash. There are two things that happen:
- Freezes when a lot of tabs are opened, needed to way a couple minutes until it became responsive again.
- Web apps that make use of the GPU (WASM) don't load, the dead face icon is shown instead.

ndavid · 2023-12-11 22:02:26

Also worth noting that such behavior is being consistent across other browsers (fresh installs). So it's not anything on my config.
It would be nice if someone else could try to reproduce, please

seth · 2023-12-11 22:03:14

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

after such "crash", but "Freezes when a lot of tabs are opened, needed to way a couple minutes until it became responsive again." sounds like you're going OOM.
=> monitor the RAM usage

Does the rest of the system remain responsive?

seth wrote:

seth wrote:
Maybe also post the relevant part of your pacman log.

Edit: also https://bbs.archlinux.org/viewtopic.php?id=290105 - but that was fixed.

Last edited by seth (2023-12-11 22:05:19)

ndavid · 2023-12-11 22:32:52

Please post your complete system journal for the boot:

https://0x0.st/H3YF.txt

=> monitor the RAM usage

I did, had htop running on the side. Saw the CPU spikes. That's why I said that hardware acceleration was not working.

Maybe also post the relevant part of your pacman log.

I don't see how my pacman log would be relevant.

EDIT: To answer your other question, only the browser becomes unresponsive, not the whole system.

Last edited by ndavid (2023-12-11 22:38:07)

ndavid · 2023-12-11 23:49:48

Thought about launching the browser from the terminal and seeing whether it logs anything during the attempt of launching an app, and it did:

[104448:104448:1211/234356.060173:ERROR:shared_context_state.cc(946)] SharedContextState context lost via ARB/EXT_robustness. Reset status = GL_GUILTY_CONTEXT_RESET_KHR
[104448:104448:1211/234356.060460:ERROR:gpu_service_impl.cc(1105)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
[104726:1:1211/234356.077667:ERROR:command_buffer_proxy_impl.cc(319)] GPU state invalid after WaitForGetOffsetInRange.
[104760:1:1211/234356.077806:ERROR:command_buffer_proxy_impl.cc(319)] GPU state invalid after WaitForGetOffsetInRange.
[104657:10:1211/234356.078012:ERROR:command_buffer_proxy_impl.cc(319)] GPU state invalid after WaitForGetOffsetInRange.
[105162:1:1211/234356.078066:ERROR:command_buffer_proxy_impl.cc(319)] GPU state invalid after WaitForGetOffsetInRange.
[105271:1:1211/234356.078082:ERROR:command_buffer_proxy_impl.cc(319)] GPU state invalid after WaitForGetOffsetInRange.
[104414:104414:1211/234356.128676:ERROR:gpu_process_host.cc(992)] GPU process exited unexpectedly: exit_code=8704
[105319:8:1211/234456.520562:ERROR:command_buffer_proxy_impl.cc(127)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
Warning: loader_scanned_icd_add: Could not get 'vkCreateInstance' via 'vk_icdGetInstanceProcAddr' for ICD libGLX_nvidia.so.0
Warning: vkCreateInstance: Found no drivers!
Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
    at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:101)
    at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:493)
    at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:379)
    at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:301)
    at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:556)

ndavid · 2023-12-12 00:53:04

UPDATE: Tested on firefox and the WASM app works.. I think this confirms that the issue is with Chrome...

seth · 2023-12-12 07:00:23

vulkaninfo

https://wiki.archlinux.org/title/Vulkan

Edit, do you explicitly https://wiki.archlinux.org/title/Chromi … n_Xwayland ?

Last edited by seth (2023-12-12 07:02:16)

ndavid · 2023-12-12 11:24:18

I'm not on Wayland. I'm on X11

seth · 2023-12-12 14:02:14

The context is completely irrelevant, the question is whether you're directing chromium to --use-angle=vulkan.
Also post the vulkaninfo, your vulkan setup seems broken.

ndavid · 2023-12-12 14:04:50

I don't use any flags in brave. And just confirm that everything is working fine in firefox and in brave 1.60.
The bug was introduced in brave 1.61

seth · 2023-12-12 14:08:07

seth wrote:

Also post the vulkaninfo, your vulkan setup seems broken.

… This is going absolutely nowhere, good luck or use FF.

Arch Linux

#1 2023-12-11 19:21:31

Hardware acceleration not working since recent kernel update

#2 2023-12-11 21:07:51

Re: Hardware acceleration not working since recent kernel update

#3 2023-12-11 21:17:44

Re: Hardware acceleration not working since recent kernel update

#4 2023-12-11 21:30:27

Re: Hardware acceleration not working since recent kernel update

#5 2023-12-11 21:30:48

Re: Hardware acceleration not working since recent kernel update

#6 2023-12-11 21:38:52

Re: Hardware acceleration not working since recent kernel update

#7 2023-12-11 21:43:50

Re: Hardware acceleration not working since recent kernel update

#8 2023-12-11 21:59:54

Re: Hardware acceleration not working since recent kernel update

#9 2023-12-11 22:02:26

Re: Hardware acceleration not working since recent kernel update

#10 2023-12-11 22:03:14

Re: Hardware acceleration not working since recent kernel update

#11 2023-12-11 22:32:52

Re: Hardware acceleration not working since recent kernel update

#12 2023-12-11 23:49:48

Re: Hardware acceleration not working since recent kernel update

#13 2023-12-12 00:53:04

Re: Hardware acceleration not working since recent kernel update

#14 2023-12-12 07:00:23

Re: Hardware acceleration not working since recent kernel update

#15 2023-12-12 11:24:18

Re: Hardware acceleration not working since recent kernel update

#16 2023-12-12 14:02:14

Re: Hardware acceleration not working since recent kernel update

#17 2023-12-12 14:04:50

Re: Hardware acceleration not working since recent kernel update

#18 2023-12-12 14:08:07

Re: Hardware acceleration not working since recent kernel update

Board footer