Issues with Mesa 24.3.x and amdgpu Vega graphics

bernd_b · 2025-01-05 19:49:49

Sure, if a binary packages are supplied, I can test as well. I failed so far building mesa with the PKBUILD from the arch-repo ...

So the devil came between 24.2.7 (8?) and 24.3.0? For the time being, I'll try 24.3.0 from arch repo, seeing if I missed this version.

Update:
And freeze this morning. Back to 24.2.7. So the devil in my system seems to be introduced between 24.2.7 (8?) and 24.3.0.

Last edited by bernd_b (2025-01-06 09:57:21)

NuSkool · 2025-01-05 22:55:10

@bernd_b, Looks like mesa 1:24.3.3-2 is available in the Extra staging repo. I haven't tested it yet and sounds like it wouldn't have fixes for this issue AFAIK.

I was hoping someone with the problematic hardware that was more knowledge than myself on troubleshooting would get involved. Since that appears not the case, I'll give it a shot.

@mesa-git Packager: Lone_Wolf, I'm looking into building mesa-git https://aur.archlinux.org/packages/mesa-git in a clean chroot.
It's failing with the following error when clean chroot building:

[3145/3449] Linking target src/gallium/targets/dri/libgallium-25.0.0-devel.so
FAILED: src/gallium/targets/dri/libgallium-25.0.0-devel.so

I'm not able to figure out which package provides 'libgallium-25.0.0-devel.so' with 'pacman -F', using several variations and having no luck trying to wildcard the version.
Searching for variations of package libgallium, 'gallium' results in mesa-amber...

Would building 'mesa 1:24.3.3-2' in a clean chroot work for the bisect testing? The wiki specifically suggests using an AUR git version.

The system I'll build and test on has a Ryzen 5 PRO 2400GE with Radeon Vega 11 Graphics. It's currently using 'mesa 1:24.2.7-1'.
An issue I'll have with testing will be very unpredictable time frame for system freezing and nothing useful in the journal.
So far it varies between min to days to freeze when testing newer versions of mesa.

Any pointers on how to proceed with bisect testing would be great.

Last edited by NuSkool (2025-01-06 21:48:09)

TheGameMaker · 2025-01-06 01:14:36

Sorry in advance if this is non value added but I wanted to chime in and let you all know that it doesn't just seem to be an issue only with integrated graphics. I'm running a 7900XTX on one monitor and a Radeon Pro WX 2100 on another monitor.

Both cards are in the same machine, but only the 7900XTX seems to be crashing as I'm still able to see my mouse and manipulate the computer on the monitor that's connected to the WX 2100. I'm pretty new to Linux in general but if anyone needs to me pull any specific info when it happens again, let me know.

Last edited by TheGameMaker (2025-01-06 01:15:32)

kclisp · 2025-01-06 04:19:45

@Lone_Wolf
I (and likely others) would be happy to test versions if they're built.

@TheGameMaker
From https://gitlab.freedesktop.org/drm/amd/-/issues/3861, https://gitlab.freedesktop.org/drm/amd/-/issues/3693, and https://gitlab.freedesktop.org/drm/amd/-/issues/3868, 7900XTX freezes should be a different issue from this one. There are patches available, so your issue should be resolved in a new kernel soon.

Last edited by kclisp (2025-01-06 22:45:26)

Lone_Wolf · 2025-01-06 10:32:11

bisectings needs to be done using clean chroot builds to avoid user settings influencing the build.
Those that wish to help build should have devtools & (optionally) pacman-contrib installed.

The builds need to be done from specific git commits and the PKGBUILD will be based on VCS packaging guidelines
In order to simplify the build/troubleshooting I have adjusted my mesa-minimal-git package to use repo llvm and build a mesa-test-git

Switching from repo mesa to mesa-test-git is easy, reverting is more work.
Another caveat is that for now there's no multilib version of mesa-test-git , so stuff that needs lib32 (steam/proton/wine) will be broken .
Also no support for NVK or opencl .

Note that pkgctl build will fail installing the built package with

==> WARNING: Failed to install built package(s).

This is due to mesa builds needing libglvnd present which depends on repo mesa being present in the chroot.
Since mesa and mesa git builds have to conflict pkgctl can't install the built package to test.
As far as I know there's no mechanism to circumvent that without compromising the clean chroot.

Here's the PKGBUILD

# Maintainer: Lone_Wolf <lone_wolf@klaas-de-kat.nl>

pkgname=mesa-test-git
pkgdesc="an open-source implementation of the OpenGL specification, stripped down git version"
pkgver=25.0.0_devel.199748.72351afe24f
pkgrel=1
arch=('x86_64')
makedepends=(git meson ninja libglvnd python-packaging python-mako xorgproto libxml2 libx11  libva elfutils libxrandr
                            wayland-protocols glslang llvm libdrm libclc clang
                            libvdpau systemd-libs python-ply libunwind libxdamage vulkan-icd-loader xcb-util-keysyms python-pyaml
                            spirv-llvm-translator
)

depends=(libdrm libxxf86vm libxdamage libxshmfence libelf
                        libunwind libglvnd wayland lm_sensors vulkan-icd-loader
                        zstd llvm-libs zlib expat libxext libxcb systemd-libs
                        glibc libx11 libxfixes gcc-libs xcb-util-keysyms
)
optdepends=('opengl-man-pages: for the OpenGL API man pages')
provides=(mesa vulkan-intel vulkan-radeon vulkan-mesa-layers libva-mesa-driver vulkan-swrast vulkan-virtio mesa-vdpau vulkan-driver opengl-driver)
conflicts=(mesa vulkan-intel vulkan-radeon vulkan-mesa-layers libva-mesa-driver vulkan-swrast mesa-vdpau vulkan-virtio
                vulkan-nouveau mesa-libgl  opencl-clover-mesa opencl-rusticl-mesa
)

url="https://www.mesa3d.org"
license=('MIT AND BSD-3-Clause AND SGI-B-2.0')
source=("mesa::git+https://gitlab.freedesktop.org/mesa/mesa.git#commit=72351afe24f9c880e07a944aaacf3a09681e1590"
)

md5sums=('249c8402cf8b7ed5a0834dc219b1c954')
sha512sums=('b2029902584afe67a5c867953acbb6f6624cbe14c37b5e279dea185c7a102866671ffb8c23d1296b238878032c1f2be9f7f23abd0499477b452bd88ab564cb24')
options=(!emptydirs !lto !debug)

# ninja grabs all available cores and leaves almost nothing for other processes.
# this package uses the environment variable NINJAFLAGS to allow the user to change this behaviour
# The responsibility to validate the value of NINJAFLAGS lies with the user.
# If unsure, use NINJAFLAGS=""

pkgver() {
    cd mesa
    local _ver
    read -r _ver < VERSION || [ -n "_ver" ]
    echo ${_ver/-/_}.$(git rev-list --count HEAD).$(git rev-parse --short HEAD)
}

build() {

    meson setup mesa _build \
       -D b_ndebug=true \
       -D b_lto=false \
       -D b_pie=true \
       -D buildtype=plain \
       --wrap-mode=nofallback \
       -D prefix=/usr \
       -D sysconfdir=/etc \
       -D platforms=x11,wayland \
       -D gallium-drivers=radeonsi,llvmpipe,zink,virgl,iris \
       -D vulkan-drivers=amd,swrast,intel \
       -D egl=enabled \
       -D gallium-extra-hud=true \
       -D gallium-nine=false \
       -D gallium-va=enabled \
       -D gallium-vdpau=enabled \
       -D gallium-xa=disabled \
       -D gbm=enabled \
       -D gles1=disabled \
       -D gles2=enabled \
       -D glvnd=enabled \
       -D glx=dri \
       -D libunwind=enabled \
       -D llvm=enabled \
       -D lmsensors=enabled \
       -D osmesa=false \
       -D shared-glapi=enabled \
       -D gallium-opencl=disabled \
       -D valgrind=disabled \
       -D vulkan-layers=device-select,overlay \
       -D tools=[] \
       -D zstd=enabled \
       -D microsoft-clc=disabled \
       -D video-codecs=all \
       -D gallium-rusticl=false \


    meson configure --no-pager _build
    ninja $NINJAFLAGS -C _build
}

package() {

    DESTDIR="${pkgdir}" ninja $NINJAFLAGS -C _build install

    ln -s /usr/lib/libGLX_mesa.so.0 "${pkgdir}/usr/lib/libGLX_indirect.so.0"
  
    install -m644 -Dt "${pkgdir}/usr/share/licenses/${pkgname}" mesa/docs/license.rst
}

I have uploaded builds for very recent trunk commit 72351afe24f and latest commit of the 24.2 branch

Please test both versions .

bernd_b · 2025-01-06 11:32:02

Lone_Wolf wrote:

I have uploaded builds for very recent trunk commit 72351afe24f and latest commit of the 24.2 branch
Please test both versions .

I took the first one, let's see if it lasts ...

glmark2
=======================================================
    glmark2 2023.01
=======================================================
    OpenGL Information
    GL_VENDOR:      AMD
    GL_RENDERER:    AMD Radeon Vega 11 Graphics (radeonsi, raven, ACO, DRM 3.59, 6.12.7-arch1-1.1)
    GL_VERSION:     4.6 (Compatibility Profile) Mesa 25.0.0-devel (git-72351afe24)
    Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 samples=0
    Surface Size:   800x600 windowed

orbit-oc · 2025-01-06 13:30:44

testing latest commit of the 24.2 branch

Name : mesa-test-git
Version : 24.2.8.193058.6552e32957b-1

$ glxinfo | grep OpenGL

OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon Vega 8 Graphics (radeonsi, raven, LLVM 18.1.8, DRM 3.54, 6.6.69-1-lts)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 24.2.8 (git-6552e32957)
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6 (Compatibility Profile) Mesa 24.2.8 (git-6552e32957)
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 24.2.8 (git-6552e32957)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

I simply downloaded and installed it. Is there anything to consider?

The system will be offline for a few hours, but after that I will use it... ;-)

Elmar Klausmeier · 2025-01-06 15:08:10

I can confirm that downgrading to `mesa 1:24.2.7-1` fixes the freezes. I did this

pacman -U /var/cache/pacman/pkg/mesa-1:24.2.7-1-x86_64.pkg.tar.zst

The freezes with `mesa 1:24.3*` occur with Firefox or Chromium. Once you put enough "pressure" on graphics the machine will freeze. First, CPU usage is going up like crazy, then it just freezes.

The issue is peculiar to the Raven Ridge Ryzen CPU family, here AMD Ryzen 3400G. The Cezanne family, here AMD Ryzen 7 5700G, seems to be unaffected. My particular system is https://eklausmeier.goip.de/blog/2020/0 … yzen-3400g.

Journalctl output is here: https://0x0.st/8iQh.txt.

Last edited by Elmar Klausmeier (2025-01-06 15:20:51)

beholder · 2025-01-06 18:56:09

I'm also getting those freezes. A workaround that works for me is this when it happens

- press CTRL+ALT+1 and then CTRL+ALT+2 repeatedly for a couple of minutes until the screen comes back on - on gnome CTRL+ALT+2 should bring you back to the desktop without needing to re-input the password.

my system

- gpu: AMD 7900 XTX
- cpu: 7800X3D

uname -a
Linux arch-pc 6.12.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 02 Jan 2025 22:52:26 +0000 x86_64 GNU/Linux

mesa 1:24.3.3-1

Jan 06 11:24:24 arch-pc syncthing[1825]: [4FNSN] INFO: Established secure connection to REZZLIU at 10.10.10.5:22000-10.10.10.30:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-60O5MKVCC0MJ28OCCCBKQC57BK
Jan 06 11:24:24 arch-pc syncthing[1825]: [4FNSN] INFO: Device REZZLIU client is "syncthing v1.27.3" named "Pixel 6a" at 10.10.10.5:22000-10.10.10.30:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-60O5MKVCC0MJ28OCCCBKQC57BK
Jan 06 11:28:19 arch-pc rtkit-daemon[1410]: Supervising 10 threads of 7 processes of 1 users.
Jan 06 11:28:19 arch-pc rtkit-daemon[1410]: Supervising 10 threads of 7 processes of 1 users.
Jan 06 11:28:21 arch-pc rtkit-daemon[1410]: Supervising 10 threads of 7 processes of 1 users.
Jan 06 11:28:21 arch-pc rtkit-daemon[1410]: Supervising 10 threads of 7 processes of 1 users.
Jan 06 11:29:58 arch-pc kernel: amdgpu 0000:03:00.0: [drm] *ERROR* [CRTC:79:crtc-0] flip_done timed out
Jan 06 11:31:55 arch-pc syncthing[1825]: [4FNSN] INFO: Lost primary connection to REZZLIU at 10.10.10.5:22000-10.10.10.30:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-60O5MKVCC0MJ28OCCCBKQC57BK: read timeout (0 remain)
Jan 06 11:31:55 arch-pc syncthing[1825]: [4FNSN] INFO: Connection to REZZLIU at 10.10.10.5:22000-10.10.10.30:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-60O5MKVCC0MJ28OCCCBKQC57BK closed: read timeout
Jan 06 11:31:57 arch-pc syncthing[1825]: [4FNSN] INFO: Established secure connection to REZZLIU at 10.10.10.5:22000-10.10.10.30:22000/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P20-60O5O9OOK7OAU5E8G37OS9DNBU
Jan 06 11:31:57 arch-pc syncthing[1825]: [4FNSN] INFO: Device REZZLIU client is "syncthing v1.27.3" named "Pixel 6a" at 10.10.10.5:22000-10.10.10.30:22000/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P20-60O5O9OOK7OAU5E8G37OS9DNBU
Jan 06 11:32:22 arch-pc syncthing[1825]: [4FNSN] INFO: Established secure connection to REZZLIU at 10.10.10.5:22000-10.10.10.30:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-60O5OCMCEI48QBG9FDKOAD4O6E
Jan 06 11:32:22 arch-pc syncthing[1825]: [4FNSN] INFO: Additional connection (+1) for device REZZLIU at 10.10.10.5:22000-10.10.10.30:22000/tcp-client/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P10-60O5OCMCEI48QBG9FDKOAD4O6E
Jan 06 11:32:22 arch-pc syncthing[1825]: [4FNSN] INFO: Lost primary connection to REZZLIU at 10.10.10.5:22000-10.10.10.30:22000/quic-server/TLS1.3-TLS_AES_128_GCM_SHA256/LAN-P20-60O5O9OOK7OAU5E8G37OS9DNBU: replacing connection (1 remain)
Jan 06 11:35:28 arch-pc kernel: amdgpu 0000:03:00.0: [drm] *ERROR* flip_done timed out
Jan 06 11:35:28 arch-pc kernel: amdgpu 0000:03:00.0: [drm] *ERROR* [CRTC:79:crtc-0] commit wait timed out
Jan 06 11:35:38 arch-pc kernel: amdgpu 0000:03:00.0: [drm] *ERROR* flip_done timed out
Jan 06 11:35:38 arch-pc kernel: amdgpu 0000:03:00.0: [drm] *ERROR* [PLANE:76:plane-6] commit wait timed out
Jan 06 11:35:38 arch-pc kernel: ------------[ cut here ]------------
Jan 06 11:35:38 arch-pc kernel: WARNING: CPU: 0 PID: 1179 at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:8622 amdgpu_dm_atomic_commit_tail+0x3b4f/0x3c30 [amdgpu]
Jan 06 11:35:38 arch-pc kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq amd_atl intel_rapl_msr intel_rapl_common amdgpu ext4 mbcache vfat jbd2 fat snd_hda_codec_hdmi mt7921e snd_hda_intel snd_intel_dspcfg mt7921_common amdxcp snd_intel_sdw_acpi btusb drm_exec snd_usb_audio mt792x_lib uvcvideo btrtl gpu_sched snd_hda_codec mt76_connac_lib snd_usbmidi_lib videobuf2_vmalloc drm_buddy kvm_amd btintel uvc snd_ump snd_hda_core mt76 btbcm videobuf2_memops i2c_algo_bit snd_rawmidi spd5118 drm_suballoc_helper videobuf2_v4l2 snd_hwdep snd_seq_device btmtk drm_ttm_helper kvm mac80211 atlantic ttm snd_pcm videobuf2_common bluetooth drm_display_helper snd_timer rapl macsec videodev libarc4 wmi_bmof pcspkr snd i2c_piix4 ptp cec k10temp i2c_smbus mc pl2303 soundcore crc16 pps_core cfg80211 mousedev gpio_amdpt joydev gpio_generic rfkill mac_hid loop nfnetlink zram 842_decompress 842_compress lz4hc_compress lz4_compress ip_tables x_tables dm_crypt cbc encrypted_keys trusted asn1_encoder tee crct10dif_pclmul crc32_pclmul polyval_clmulni
Jan 06 11:35:38 arch-pc kernel:  polyval_generic ghash_clmulni_intel hid_generic sha512_ssse3 sha256_ssse3 sha1_ssse3 aesni_intel gf128mul nvme crypto_simd cryptd ccp usbhid sp5100_tco nvme_core nvme_auth video wmi btrfs blake2b_generic libcrc32c crc32c_generic crc32c_intel xor raid6_pq dm_mod crypto_user
Jan 06 11:35:38 arch-pc kernel: CPU: 0 UID: 0 PID: 1179 Comm: systemd-logind Not tainted 6.12.8-arch1-1 #1 099de49ddaebb26408f097c48b36e50b2c8e21c9
Jan 06 11:35:38 arch-pc kernel: Hardware name: Micro-Star International Co., Ltd. MS-7D69/MEG X670E ACE (MS-7D69), BIOS 1.90 08/10/2023
Jan 06 11:35:38 arch-pc kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x3b4f/0x3c30 [amdgpu]
Jan 06 11:35:38 arch-pc kernel: Code: 7c e2 e9 dc fd ff ff 49 8d 87 50 31 04 00 c6 85 38 fe ff ff 00 48 89 85 48 fe ff ff e9 d8 cb ff ff 0f 0b e9 fc f2 ff ff 0f 0b <0f> 0b e9 12 f3 ff ff 0f 0b e9 11 cc ff ff 48 c7 85 28 fe ff ff 00
Jan 06 11:35:38 arch-pc kernel: RSP: 0018:ffffae86c23a75b0 EFLAGS: 00010086
Jan 06 11:35:38 arch-pc kernel: RAX: 0000000000000001 RBX: 0000000000000286 RCX: ffff8db801082118
Jan 06 11:35:38 arch-pc kernel: RDX: 0000000000000001 RSI: 0000000000000297 RDI: ffff8db842c80178
Jan 06 11:35:38 arch-pc kernel: RBP: ffffae86c23a7800 R08: ffffae86c23a749c R09: 0000000000000000
Jan 06 11:35:38 arch-pc kernel: R10: ffffae86c23a7508 R11: ffffae86c23a750c R12: ffffae86c23a7668
Jan 06 11:35:38 arch-pc kernel: R13: 0000000000000000 R14: ffff8dba3d761000 R15: ffff8db801082000
Jan 06 11:35:38 arch-pc kernel: FS:  00007cc05b0e2900(0000) GS:ffff8dc6d8200000(0000) knlGS:0000000000000000
Jan 06 11:35:38 arch-pc kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 06 11:35:38 arch-pc kernel: CR2: 0000714aae6c4400 CR3: 00000001407b8000 CR4: 0000000000f50ef0
Jan 06 11:35:38 arch-pc kernel: PKRU: 55555554
Jan 06 11:35:38 arch-pc kernel: Call Trace:
Jan 06 11:35:38 arch-pc kernel:  <TASK>
Jan 06 11:35:38 arch-pc kernel:  ? amdgpu_dm_atomic_commit_tail+0x3b4f/0x3c30 [amdgpu fb97feb5a7216969a6c4e39cc61cb53691cdacb2]
Jan 06 11:35:38 arch-pc kernel:  ? __warn.cold+0x93/0xf6
Jan 06 11:35:38 arch-pc kernel:  ? amdgpu_dm_atomic_commit_tail+0x3b4f/0x3c30 [amdgpu fb97feb5a7216969a6c4e39cc61cb53691cdacb2]
Jan 06 11:35:38 arch-pc kernel:  ? report_bug+0xff/0x140
Jan 06 11:35:38 arch-pc kernel:  ? handle_bug+0x58/0x90
Jan 06 11:35:38 arch-pc kernel:  ? exc_invalid_op+0x17/0x70
Jan 06 11:35:38 arch-pc kernel:  ? asm_exc_invalid_op+0x1a/0x20
Jan 06 11:35:38 arch-pc kernel:  ? amdgpu_dm_atomic_commit_tail+0x3b4f/0x3c30 [amdgpu fb97feb5a7216969a6c4e39cc61cb53691cdacb2]
Jan 06 11:35:38 arch-pc kernel:  commit_tail+0x91/0x130
Jan 06 11:35:38 arch-pc kernel:  drm_atomic_helper_commit+0x11a/0x140
Jan 06 11:35:38 arch-pc kernel:  drm_atomic_commit+0xa6/0xe0
Jan 06 11:35:38 arch-pc kernel:  ? __pfx___drm_printfn_info+0x10/0x10
Jan 06 11:35:38 arch-pc kernel:  drm_client_modeset_commit_atomic+0x203/0x250
Jan 06 11:35:38 arch-pc kernel:  drm_client_modeset_commit_locked+0x5a/0x160
Jan 06 11:35:38 arch-pc kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 06 11:35:38 arch-pc kernel:  __drm_fb_helper_restore_fbdev_mode_unlocked+0x5e/0xd0
Jan 06 11:35:38 arch-pc kernel:  drm_fb_helper_set_par+0x30/0x40
Jan 06 11:35:38 arch-pc kernel:  fb_set_var+0x25c/0x460
Jan 06 11:35:38 arch-pc kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 06 11:35:38 arch-pc kernel:  ? update_load_avg+0x7e/0x7b0
Jan 06 11:35:38 arch-pc kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 06 11:35:38 arch-pc kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 06 11:35:38 arch-pc kernel:  ? sched_clock_cpu+0xf/0x1d0
Jan 06 11:35:38 arch-pc kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 06 11:35:38 arch-pc kernel:  ? psi_group_change+0x13b/0x310
Jan 06 11:35:38 arch-pc kernel:  fbcon_blank+0x271/0x330
Jan 06 11:35:38 arch-pc kernel:  do_unblank_screen+0xad/0x150
Jan 06 11:35:38 arch-pc kernel:  complete_change_console+0x54/0x120
Jan 06 11:35:38 arch-pc kernel:  vt_ioctl+0xec3/0x12c0
Jan 06 11:35:38 arch-pc kernel:  tty_ioctl+0xe2/0x8a0
Jan 06 11:35:38 arch-pc kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 06 11:35:38 arch-pc kernel:  ? __seccomp_filter+0x303/0x520
Jan 06 11:35:38 arch-pc kernel:  __x64_sys_ioctl+0x91/0xd0
Jan 06 11:35:38 arch-pc kernel:  do_syscall_64+0x82/0x190
Jan 06 11:35:38 arch-pc kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 06 11:35:38 arch-pc kernel:  ? syscall_exit_to_user_mode+0x37/0x1c0
Jan 06 11:35:38 arch-pc kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 06 11:35:38 arch-pc kernel:  ? do_syscall_64+0x8e/0x190
Jan 06 11:35:38 arch-pc kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 06 11:35:38 arch-pc kernel:  ? evdev_ioctl+0x6f/0x90
Jan 06 11:35:38 arch-pc kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 06 11:35:38 arch-pc kernel:  ? syscall_exit_to_user_mode+0x37/0x1c0
Jan 06 11:35:38 arch-pc kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 06 11:35:38 arch-pc kernel:  ? do_syscall_64+0x8e/0x190
Jan 06 11:35:38 arch-pc kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 06 11:35:38 arch-pc kernel:  ? do_syscall_64+0x8e/0x190
Jan 06 11:35:38 arch-pc kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 06 11:35:38 arch-pc kernel:  ? do_syscall_64+0x8e/0x190
Jan 06 11:35:38 arch-pc kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 06 11:35:38 arch-pc kernel:  ? do_syscall_64+0x8e/0x190
Jan 06 11:35:38 arch-pc kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 06 11:35:38 arch-pc kernel:  ? do_syscall_64+0x8e/0x190
Jan 06 11:35:38 arch-pc kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Jan 06 11:35:38 arch-pc kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Jan 06 11:35:38 arch-pc kernel: RIP: 0033:0x7cc05ab23ced
Jan 06 11:35:38 arch-pc kernel: Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1a 48 8b 45 c8 64 48 2b 04 25 28 00 00 00
Jan 06 11:35:38 arch-pc kernel: RSP: 002b:00007ffe55f13050 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Jan 06 11:35:38 arch-pc kernel: RAX: ffffffffffffffda RBX: 000000000000001f RCX: 00007cc05ab23ced
Jan 06 11:35:38 arch-pc kernel: RDX: 0000000000000001 RSI: 0000000000005605 RDI: 000000000000001f
Jan 06 11:35:38 arch-pc kernel: RBP: 00007ffe55f130a0 R08: 00007ffe55f13030 R09: 00005ce766311ed0
Jan 06 11:35:38 arch-pc kernel: R10: 00007ffe55f13080 R11: 0000000000000246 R12: 0000000000000000
Jan 06 11:35:38 arch-pc kernel: R13: 00007ffe55f13130 R14: 00005ce766310be0 R15: 00005ce766313120
Jan 06 11:35:38 arch-pc kernel:  </TASK>
Jan 06 11:35:38 arch-pc kernel: ---[ end trace 0000000000000000 ]---
Jan 06 11:35:38 arch-pc kernel: rfkill: input handler enabled
Jan 06 11:35:38 arch-pc systemd-logind[1179]: New session 5 of user gdm.
Jan 06 11:35:38 arch-pc gsd-media-keys[2064]: Unable to get default source
Jan 06 11:35:38 arch-pc gsd-media-keys[2064]: Unable to get default sink
Jan 06 11:35:38 arch-pc systemd[1]: Created slice User Slice of UID 120.
Jan 06 11:35:38 arch-pc systemd[1]: Starting User Runtime Directory /run/user/120...
Jan 06 11:35:39 arch-pc systemd[1]: Finished User Runtime Directory /run/user/120.
Jan 06 11:35:39 arch-pc systemd[1]: Starting User Manager for UID 120...
Jan 06 11:35:39 arch-pc (systemd)[7755]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[gdm] ruser=[<unknown>] rhost=[<unknown>]
Jan 06 11:35:39 arch-pc (systemd)[7755]: pam_unix(systemd-user:session): session opened for user gdm(uid=120) by gdm(uid=0)
Jan 06 11:35:39 arch-pc systemd-logind[1179]: New session 6 of user gdm.
Jan 06 11:35:39 arch-pc systemd[7755]: Queued start job for default target Main User Target.
Jan 06 11:35:39 arch-pc systemd[7755]: Created slice User Application Slice.
Jan 06 11:35:39 arch-pc systemd[7755]: Reached target Paths.
Jan 06 11:35:39 arch-pc systemd[7755]: Reached target Timers.
Jan 06 11:35:39 arch-pc systemd[7755]: Starting D-Bus User Message Bus Socket...
Jan 06 11:35:39 arch-pc systemd[7755]: Listening on GnuPG network certificate management daemon.
Jan 06 11:35:39 arch-pc systemd[7755]: Starting GCR ssh-agent wrapper...
Jan 06 11:35:39 arch-pc systemd[7755]: Listening on GNOME Keyring daemon.
Jan 06 11:35:39 arch-pc systemd[7755]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jan 06 11:35:39 arch-pc systemd[7755]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Jan 06 11:35:39 arch-pc systemd[7755]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Jan 06 11:35:39 arch-pc systemd[7755]: Listening on GnuPG cryptographic agent and passphrase cache.
Jan 06 11:35:39 arch-pc systemd[7755]: Listening on GnuPG public key management service.
Jan 06 11:35:39 arch-pc systemd[7755]: Listening on p11-kit server.
Jan 06 11:35:39 arch-pc systemd[7755]: Listening on PipeWire PulseAudio.
Jan 06 11:35:39 arch-pc systemd[7755]: Listening on PipeWire Multimedia System Sockets.
Jan 06 11:35:39 arch-pc systemd[7755]: Listening on D-Bus User Message Bus Socket.
Jan 06 11:35:39 arch-pc systemd[7755]: Listening on GCR ssh-agent wrapper.
Jan 06 11:35:39 arch-pc systemd[7755]: Reached target Sockets.
Jan 06 11:35:39 arch-pc systemd[7755]: Reached target Basic System.
Jan 06 11:35:39 arch-pc systemd[1]: Started User Manager for UID 120.
Jan 06 11:35:39 arch-pc systemd[7755]: Starting Update XDG user dir configuration...
Jan 06 11:35:39 arch-pc systemd[1]: Started Session 5 of User gdm.
Jan 06 11:35:39 arch-pc systemd[7755]: Finished Update XDG user dir configuration.
Jan 06 11:35:39 arch-pc systemd[7755]: Reached target Main User Target.
Jan 06 11:35:39 arch-pc systemd[7755]: Startup finished in 158ms.
Jan 06 11:35:39 arch-pc systemd[7755]: Created slice User Core Session Slice.
Jan 06 11:35:39 arch-pc systemd[7755]: Starting D-Bus User Message Bus...
Jan 06 11:35:39 arch-pc dbus-broker-launch[7777]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +31: Eavesdropping is deprecated and ignored
Jan 06 11:35:39 arch-pc dbus-broker-launch[7777]: Policy to allow eavesdropping in /usr/share/dbus-1/session.conf +33: Eavesdropping is deprecated and ignored
Jan 06 11:35:39 arch-pc systemd[7755]: Started D-Bus User Message Bus.
Jan 06 11:35:39 arch-pc dbus-broker-launch[7777]: Ready
Jan 06 11:35:39 arch-pc /usr/lib/gdm-wayland-session[7781]: dbus-daemon[7781]: [session uid=120 pid=7781 pidfd=5] Activating service name='org.freedesktop.systemd1' requested by ':1.2' (uid=120 pid=7782 comm="/usr/lib/gnome-session-binary --autostart /usr/sha")
Jan 06 11:35:39 arch-pc /usr/lib/gdm-wayland-session[7781]: dbus-daemon[7781]: [session uid=120 pid=7781 pidfd=5] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Jan 06 11:35:39 arch-pc gnome-session[7782]: gnome-session-binary[7782]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
Jan 06 11:35:39 arch-pc gnome-session-binary[7782]: WARNING: Could not check if unit gnome-session-wayland@gnome-login.target is active: Error calling StartServiceByName for org.freedesktop.systemd1: Process org.freedesktop.systemd1 exited with status 1
Jan 06 11:35:39 arch-pc gnome-session[7782]: gnome-session-binary[7782]: WARNING: Desktop file /usr/share/gdm/greeter/autostart/orca-autostart.desktop for application orca-autostart.desktop could not be parsed or references a missing TryExec binary
Jan 06 11:35:39 arch-pc gnome-session-binary[7782]: WARNING: Desktop file /usr/share/gdm/greeter/autostart/orca-autostart.desktop for application orca-autostart.desktop could not be parsed or references a missing TryExec binary
Jan 06 11:35:39 arch-pc gnome-shell[7794]: Running GNOME Shell (using mutter 47.3) as a Wayland display server
Jan 06 11:35:39 arch-pc rtkit-daemon[1410]: Supervising 10 threads of 7 processes of 1 users.
Jan 06 11:35:39 arch-pc rtkit-daemon[1410]: Successfully made thread 7812 of process 7794 owned by '120' high priority at nice level -15.
Jan 06 11:35:39 arch-pc rtkit-daemon[1410]: Supervising 11 threads of 8 processes of 2 users.
Jan 06 11:35:39 arch-pc gnome-shell[7794]: Thread 'KMS thread' will be using high priority scheduling
Jan 06 11:35:39 arch-pc gnome-shell[7794]: Device '/dev/dri/card1' prefers shadow buffer
Jan 06 11:35:39 arch-pc gnome-shell[7794]: Added device '/dev/dri/card1' (amdgpu) using atomic mode setting.
Jan 06 11:35:39 arch-pc gnome-shell[7794]: Device '/dev/dri/card0' prefers shadow buffer
Jan 06 11:35:39 arch-pc gnome-shell[7794]: Added device '/dev/dri/card0' (amdgpu) using atomic mode setting.
Jan 06 11:35:39 arch-pc gnome-shell[7794]: Created gbm renderer for '/dev/dri/card1'
Jan 06 11:35:39 arch-pc gnome-shell[7794]: Created gbm renderer for '/dev/dri/card0'
Jan 06 11:35:39 arch-pc gnome-shell[7794]: Boot VGA GPU /dev/dri/card1 selected as primary
Jan 06 11:35:39 arch-pc gnome-shell[7794]: Obtained a high priority EGL context
Jan 06 11:35:39 arch-pc /usr/lib/gdm-wayland-session[7781]: dbus-daemon[7781]: [session uid=120 pid=7781 pidfd=5] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=120 pid=7794 comm="/usr/bin/gnome-shell")
Jan 06 11:35:39 arch-pc /usr/lib/gdm-wayland-session[7781]: dbus-daemon[7781]: [session uid=120 pid=7781 pidfd=5] Successfully activated service 'org.a11y.Bus'
Jan 06 11:35:39 arch-pc gnome-shell[7794]: Using public X11 display :1024, (using :1025 for managed services)
Jan 06 11:35:39 arch-pc gnome-shell[7794]: Using Wayland display name 'wayland-0'
Jan 06 11:35:39 arch-pc /usr/lib/gdm-wayland-session[7862]: dbus-daemon[7862]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=120 pid=7794 comm="/usr/bin/gnome-shell")
Jan 06 11:35:39 arch-pc /usr/lib/gdm-wayland-session[7862]: dbus-daemon[7862]: Successfully activated service 'org.a11y.atspi.Registry'
Jan 06 11:35:39 arch-pc /usr/lib/gdm-wayland-session[7865]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Jan 06 11:35:39 arch-pc gnome-shell[7794]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly.
Jan 06 11:35:39 arch-pc gnome-shell[7794]: Will monitor session 5
Jan 06 11:35:39 arch-pc systemd[1]: Starting Locale Service...
Jan 06 11:35:39 arch-pc /usr/lib/gdm-wayland-session[7781]: dbus-daemon[7781]: [session uid=120 pid=7781 pidfd=5] Activating service name='org.gnome.Shell.Screencast' requested by ':1.3' (uid=120 pid=7794 comm="/usr/bin/gnome-shell")
Jan 06 11:35:39 arch-pc /usr/lib/gdm-wayland-session[7781]: dbus-daemon[7781]: [session uid=120 pid=7781 pidfd=5] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=120 pid=7794 comm="/usr/bin/gnome-shell")
Jan 06 11:35:39 arch-pc /usr/lib/gdm-wayland-session[7781]: dbus-daemon[7781]: [session uid=120 pid=7781 pidfd=5] Successfully activated service 'org.freedesktop.impl.portal.PermissionStore'
Jan 06 11:35:39 arch-pc /usr/lib/gdm-wayland-session[7781]: dbus-daemon[7781]: [session uid=120 pid=7781 pidfd=5] Activating service name='org.gnome.Shell.Notifications' requested by ':1.3' (uid=120 pid=7794 comm="/usr/bin/gnome-shell")
Jan 06 11:35:39 arch-pc systemd[1]: Started Locale Service.
Jan 06 11:35:39 arch-pc org.gnome.Shell.desktop[7794]: Window manager warning: Failed to parse saved session file: Failed to open file “/var/lib/gdm/.config/mutter/sessions/10569fa8b512a31f8b173618853922793800000077820000.ms”: No such file or directory
Jan 06 11:35:39 arch-pc gnome-shell[7794]: Failed to launch ibus-daemon: Failed to execute child process “ibus-daemon” (No such file or directory)
Jan 06 11:35:39 arch-pc gnome-shell[7794]: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation
Jan 06 11:35:39 arch-pc systemd[1]: Starting Hostname Service...
Jan 06 11:35:39 arch-pc /usr/lib/gdm-wayland-session[7781]: dbus-daemon[7781]: [session uid=120 pid=7781 pidfd=5] Activating service name='org.freedesktop.systemd1' requested by ':1.20' (uid=120 pid=7981 comm="/usr/lib/gsd-sharing")
Jan 06 11:35:39 arch-pc /usr/lib/gdm-wayland-session[7781]: dbus-daemon[7781]: [session uid=120 pid=7781 pidfd=5] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1
Jan 06 11:35:39 arch-pc /usr/lib/gdm-wayland-session[7781]: dbus-daemon[7781]: [session uid=120 pid=7781 pidfd=5] Successfully activated service 'org.gnome.Shell.Notifications'
Jan 06 11:35:39 arch-pc gsd-sharing[7981]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Jan 06 11:35:39 arch-pc gsd-sharing[7981]: Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Jan 06 11:35:39 arch-pc gnome-shell[7794]: Failed to create color profile from colord profile: Error opening file /home/fred/.local/share/icc/edid-3677f87b350ebb514504413952b427ce.icc: Permission denied
Jan 06 11:35:39 arch-pc gnome-shell[7794]: No permission to control network connections: Polkit.Error: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: Action org.freedesktop.NetworkManager.network-control is not registered
Jan 06 11:35:39 arch-pc systemd[1]: Starting Location Lookup Service...
Jan 06 11:35:39 arch-pc systemd[7755]: Started PipeWire Multimedia Service.
Jan 06 11:35:39 arch-pc systemd[7755]: Started Multimedia Service Session Manager.
Jan 06 11:35:39 arch-pc systemd[7755]: Started PipeWire PulseAudio.

kclisp · 2025-01-06 23:50:57

@Lone_Wolf

mesa-test-git 25.0.0_devel.199748.72351afe24f-1 is broken.
mesa-test-git 24.2.8.193058.6552e32957b-1 seems fine.

I believe I've found a quick way to reproduce the issue. I use i3; I start two terminals in one workspace, and hold Super + Shift + Space on one of them, which rapidly alternates it between a floating window and a tiling window, producing a lot of graphical window resizing. This can produce a freeze on broken builds in a few seconds.

@beholder

See my previous comment; the AMD 7900 XTX issue should be different from this Raven Ridge issue.

Last edited by kclisp (2025-01-07 03:27:02)

Lone_Wolf · 2025-01-07 10:54:31

Nice find , kclisp .

Next is [bb8063e1f4ddaf24b40a27c102a720accdef536a] anv/generated_indirect_draws: Adjust xe2 simd32 sends_count_expectation

orbit-oc · 2025-01-07 12:23:49

Question
I don't want to hold up the process unnecessarily, but why is 24.2.0 (24.2.0_devel.192261.bb8063e1f4d-1) going below 24.2.8, which seem to be already identified as clean?
Shouldn't there now be a halving (bisection) between 24.2.8 and 25.0.0?

For the reason of completeness
mesa-test-git 24.2.8.193058.6552e32957b-1 has been running here in normal operation for about 11 hours.
Since we already seem to be one step further, I will switch back to the regular 24.2.7-1 shortly.

Lone_Wolf · 2025-01-07 13:01:53

Mesa devs create a new branch for every major release that are then developed separately.
This issue involves 3 branches : 24.2.x, 24.3.x , main .
Often commits from one branches are backported to older branches, sometimes the reverse also happens.

It also happens that later commits solve an issue without anyone realising it.
Combined, this makes bisecting over multiple branches tricky.

There's a good chance the cause is between the start of the 24.2 and start of 24.3 branches, but with bisecting a 'good chance' is merely an assumption.
If the assumption is wrong, we would be doing a lot of work with very little to show for.

If the 24.2.0 test version also works fine, we have tested both start and end of the 24.2 branch and can be certain the crash is not in the 24.2 branch.

Keep in mind that mesa doesn't have lts-versions and the 24.2 branch will soon be end of life and abandoned.
Unless this issue is bisected properly, it could stay present in every future mesa version.

kclisp · 2025-01-07 15:20:29

mesa-test-git 24.2.0_devel.192261.bb8063e1f4d-1 seems fine.

Lone_Wolf · 2025-01-07 15:58:23

Thx, 3745 revs left to check.

802c30beab3dbfe6ac306816680bde49d512f265]hk: use 0 pointer for 0-sized buffers .

kclisp · 2025-01-07 16:37:44

mesa-test-git 24.3.0_devel.196002.802c30beab3-1 is broken.

Lone_Wolf · 2025-01-07 17:10:09

1870 revisions left

wrong build, see 2 posts down

Last edited by Lone_Wolf (2025-01-07 18:03:36)

kclisp · 2025-01-07 17:22:49

It looks like you put the wrong link.

Lone_Wolf · 2025-01-07 18:02:59

Bad c/p of the commit hash, was building the wrong one.

83b74bfc6d787017f403410293d4c580503209d8] bin/gen_release_notes: adjust checksums section

kclisp · 2025-01-07 18:12:14

mesa-test-git 24.3.0_devel.194131.83b74bfc6d7-1 seems fine.

Lone_Wolf · 2025-01-07 18:24:31

Glad to see not everything in the 24.3 branch is broken.

935 revs left
[d9a71239b2aae14102d7ed1ebeb73b4421d69ff6] Use old en/decoding for vkQueueSignalReleaseImage

kclisp · 2025-01-07 18:56:35

Lone_Wolf wrote:

Glad to see not everything in the 24.3 branch is broken.

Yep, me as well.

mesa-test-git 24.3.0_devel.195066.d9a71239b2a-1 seems fine.

Lone_Wolf · 2025-01-07 19:20:18

467 revs left, we're getting closer

[9fab2072a3393ac61753fc0f139f0654f9df246c] radv/video: use the h264 defines for macroblock w/h

kclisp · 2025-01-07 19:24:14

mesa-test-git 24.3.0_devel.195534.9fab2072a33-1 is broken.

Lone_Wolf · 2025-01-07 19:52:13

233 revs left

[b01d76027d39a24709185b5b6b7377806ca9457c] blorp: assert that color depth is not 96 for Wa_16021021469

Arch Linux

#51 2025-01-05 19:49:49

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#52 2025-01-05 22:55:10

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#53 2025-01-06 01:14:36

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#54 2025-01-06 04:19:45

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#55 2025-01-06 10:32:11

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#56 2025-01-06 11:32:02

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#57 2025-01-06 13:30:44

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#58 2025-01-06 15:08:10

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#59 2025-01-06 18:56:09

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#60 2025-01-06 23:50:57

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#61 2025-01-07 10:54:31

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#62 2025-01-07 12:23:49

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#63 2025-01-07 13:01:53

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#64 2025-01-07 15:20:29

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#65 2025-01-07 15:58:23

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#66 2025-01-07 16:37:44

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#67 2025-01-07 17:10:09

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#68 2025-01-07 17:22:49

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#69 2025-01-07 18:02:59

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#70 2025-01-07 18:12:14

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#71 2025-01-07 18:24:31

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#72 2025-01-07 18:56:35

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#73 2025-01-07 19:20:18

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#74 2025-01-07 19:24:14

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

#75 2025-01-07 19:52:13

Re: Issues with Mesa 24.3.x and amdgpu Vega graphics

Board footer