FS#74733 - Chromium graphic acceleration GPU on AMD after updating to GCC 12 is just heavily bugged

Attached to Project: Arch Linux
Opened by Lahfa Samy (AkechiShiro) - Friday, 13 May 2022, 23:14 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 19 June 2022, 13:58 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Graphical artifacts are appearing on X11, wayland was not tested.
I'm under the AMDGPU driver.
Mesa version : 22.2.0_devel.153875.f575b0d7b51.d41d8cd98f00b204e9800998ecf8427e-1

Additional info:
* package version(s)
[1453773:1453773:0100/000000.917371:ERROR:angle_platform_impl.cc(44)] Display.cpp:977 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1273.
[1453773:1453773:0100/000000.920111:ERROR:gl_surface_egl.cc(837)] EGL Driver message (Critical) eglInitialize: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1273.
[1453773:1453773:0100/000000.920184:ERROR:gl_surface_egl.cc(1473)] eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED
[1453773:1453773:0100/000000.920493:ERROR:gl_ozone_egl.cc(21)] GLSurfaceEGL::InitializeOneOff failed.
I don't know if there is an upstream bug for now, in Mesa or if it is in the vulkan drivers.

Steps to reproduce:
Launch chromium with --enable-gpu.

Workaround: --disable-gpu
This task depends upon

Closed by  Antonio Rojas (arojas)
Sunday, 19 June 2022, 13:58 GMT
Reason for closing:  Not a bug
Comment by Lahfa Samy (AkechiShiro) - Friday, 13 May 2022, 23:15 GMT
Chromium version: 101.0.4951.64-1
Hardware: Thinkpad T495 AMD Ryzen 7 3700U with iGPU Radeon Vega RX 10
Comment by Otto Laari (Niinu) - Thursday, 19 May 2022, 20:04 GMT
I'm getting word to word same slew of errors without graphical artifacts or any unusual performance degradation on my old thinkpad so they might not be related (unless the errors appeared specifically after the gcc update).
Is there any specific situation where gpu accel isn't working or the artifacts appear?

Chromium: 101.0.4951.64, GCC: 12.1.0, OpenGL: ES 2.0, Mesa: 22.0.3, X11: 1.21.1.3
Hardware: Thinkpad Edge 13 with Intel SU7300 cpu and Intel GMA4500MHD igpu (i915 drivers)
(Launching with --disable-gpu doesn't take away the errors on my end)
Comment by Lahfa Samy (AkechiShiro) - Saturday, 21 May 2022, 08:30 GMT
Just to clarify, I do have the errors regardless of using --disable-gpu or not, I'm looking at some mesa issue : https://gitlab.freedesktop.org/mesa/mesa/-/issues/6486 and it could be related to this issue or not. But my issue is with the latest mesa-git and not according to the package inside the extra repository.
Comment by Lahfa Samy (AkechiShiro) - Tuesday, 31 May 2022, 04:22 GMT
The errors, we are getting, seem to be totally unrelated to the graphical glitches.
I'm closing this bug as it won't be reproducible with Mesa from the ArchLinux repos, as according to a comment : https://gitlab.freedesktop.org/mesa/mesa/-/issues/6486 the mesa pkg in the ArchLinux repos is built with no LTO which does not trigger the bug.
Hence, I'm closing it.

Loading...