Arch Linux

pacmancrashedagain

Member

Registered: 2024-12-14

Posts: 9

Issues with Mesa 24.3.X and Raven Ridge/Vega(new thread)

As requested by lone_wolf on this thread: https://bbs.archlinux.org/viewtopic.php … 0#p2214710

I'm using qtile on xorg with a AMD 3200G and 8GB of RAM, picom is running as a compositor, i'll update the firmware later as suggested but right now it's not a good time. 

lspci -k: http://0x0.st/XFUi.txt
glxinfo -B: http://0x0.st/XFU-.txt
eglinfo -B: http://0x0.st/XFUo.txt

The eglinfo -B also had this:

_amdgpu_device_initialize: amdgpu_query_info(ACCEL_WORKING) failed (-13)
amdgpu: amdgpu_device_initialize failed.

Possibly related issue since i also have Raven Ridge and use a chromium derivative(qutebrowser):

https://gitlab.freedesktop.org/mesa/mesa/-/issues/12310

Last edited by pacmancrashedagain (2024-12-16 14:02:02)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,097

Re: Issues with Mesa 24.3.X and Raven Ridge/Vega(new thread)

eglinfo gives that message if something else has already initialised the card, usually that something else is the gui environment itself .

Nothing weird in the outputs as far as I can see.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

pacmancrashedagain

Member

Registered: 2024-12-14

Posts: 9

Re: Issues with Mesa 24.3.X and Raven Ridge/Vega(new thread)

I went on and updated the firmware and now upgraded mesa to see if it still happens.

If it still does, i guess i'll take it to the mesa tracker since all the people having problems seem to have Raven Ridge so maybe they can figure something out.

Thanks for all the help Lone_Wolf, i'll update this post if it still crashes or not.

EDIT: Sadly it still froze after like an half of hour of usage, back to Mesa 24.2.7 for now.

I made a post on that thread i found on the mesa tracker before, let's see if they can help.

https://gitlab.freedesktop.org/mesa/mes … te_2705331

Last edited by pacmancrashedagain (2024-12-17 14:08:51)

flemingfleming

Member

Registered: 2024-12-27

Posts: 1

Re: Issues with Mesa 24.3.X and Raven Ridge/Vega(new thread)

I have also experienced the same issue

Output of inxi -G (after downgrading):

Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Raven Ridge [Radeon Vega Series
    / Radeon Mobile Series] driver: amdgpu v: kernel
  Device-2: Chicony Integrated Camera (1280x720@30) driver: uvcvideo
    type: USB
  Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.4
    compositor: kwin_wayland driver: X: loaded: modesetting dri: radeonsi
    gpu: amdgpu resolution: 1280x720
  API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.2.7-arch1.1
    renderer: AMD Radeon Vega 8 Graphics (radeonsi raven LLVM 18.1.8 DRM 3.59
    6.12.6-arch1-1)
  API: Vulkan v: 1.4.303 drivers: N/A surfaces: xcb,xlib,wayland

Downgrading mesa and vulkan-radeon to 1:24.2.7-1 was the only thing that worked for me. Also tried downgrading the kernel, using the LTS kernel, downgrading kwin and switching between Wayland and X, to no avail.

Note that although the linked issue on the mesa bugtracker refers to freezing when using chromium based applications, I experienced the freeze occurring anytime a graphical session was active, though it seems to be the same issue as referred to before on this thread and the previous.

Unfortunately I don't get anything at all in the logs from after the freeze if I REISUB immediately, and if I don't do that then even REISUB stops working, so I have no useful logs

orbit-oc

Member

Registered: 2024-12-15

Posts: 25

Re: Issues with Mesa 24.3.X and Raven Ridge/Vega(new thread)

Note that although the linked issue on the mesa bugtracker refers to freezing when using chromium based applications, I experienced the freeze occurring anytime a graphical session was active, though it seems to be the same issue as referred to before on this thread and the previous.

Yes, I would confirm that.

Unfortunately I don't get anything at all in the logs from after the freeze if I REISUB immediately, and if I don't do that then even REISUB stops working, so I have no useful logs.

It seems that @flemingfleming is not the only one without a reasonably analyzable error message. Thanks for the hint about the delayed execution of REISUB. It was the same for me the last time. The system could boot, but the file system had errors that had to be fixed.

For me it has turned out that it is not good that there are several threads about the same problem, at least when it comes to the AMD Vega graphics in connection with the current mesa package.
If it turns out that there even are several errors in mesa and vega, then - in my opinion - it is bad to have to search for everything in that already existing confusion.

My suggestion is to continue on *one* place:
https://bbs.archlinux.org/viewtopic.php?id=301798