stable

mesa-24.1.2-7.fc40

FEDORA-2024-337ebae0a7 created by jexposit 5 months ago for Fedora 40

How to install

Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:

sudo dnf upgrade --refresh --advisory=FEDORA-2024-337ebae0a7

This update has been submitted for testing by jexposit.

5 months ago

This update's test gating status has been changed to 'waiting'.

5 months ago

This update's test gating status has been changed to 'waiting'.

5 months ago

This update has obsoleted mesa-24.1.2-3.fc40, and has inherited its bugs and notes.

5 months ago

jexposit edited this update.

5 months ago

jexposit edited this update.

5 months ago

jexposit edited this update.

5 months ago

This update's test gating status has been changed to 'failed'.

5 months ago

This update's test gating status has been changed to 'waiting'.

5 months ago
User Icon imabug provided feedback 5 months ago
karma
User Icon alexpl commented & provided feedback 5 months ago
karma

No regressions noted

BZ#2294628 Colors changed
BZ#2294651 mesa 24.1.2-3 messing laptop colors

This update's test gating status has been changed to 'passed'.

5 months ago

This update has been pushed to testing.

5 months ago

This update can be pushed to stable now if the maintainer wishes

5 months ago
User Icon bojan commented & provided feedback 5 months ago
karma

Works.

This update has been submitted for stable by bodhi.

5 months ago
User Icon nixuser commented & provided feedback 5 months ago
karma

Working fine.

Note I'm having the problems in cs9 with mesa 24.1.0 currently, previous version works.

User Icon jexposit commented & provided feedback 5 months ago

@nixuser thanks for testing! I submitted this same version of mesa to CentOS Stream 9. I should be available in a few days. If you have problems with it, please open a bug report and I'll look into it.

User Icon pawef9 provided feedback 5 months ago
karma
BZ#2294628 Colors changed
BZ#2294651 mesa 24.1.2-3 messing laptop colors
User Icon ersen commented & provided feedback 5 months ago
karma

works

This update has been pushed to stable.

5 months ago
User Icon eifr0980 provided feedback 5 months ago
karma
User Icon ndim commented & provided feedback 5 months ago
karma

24.1.2-7 works with my R7 370, while 24.1.2-2 Gnome-Wayland sessions could not launch any app. Hooray!

BZ#2292321 gnome shell wayland sessions crash when any app is launched
User Icon veilink commented & provided feedback 4 months ago
karma

    sacredsin@CtrlAltReboot ~ [SIGABRT]> spectacle
    libva info: VA-API version 1.21.0
    libva info: Trying to open /usr/lib64/dri-nonfree/radeonsi_drv_video.so
    libva info: Trying to open /usr/lib64/dri-freeworld/radeonsi_drv_video.so
    libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
    libva info: Found init function __vaDriverInit_1_21
    libva info: va_openDriver() returns 0
    kpipewire_vaapi_logging: VAAPI: Mesa Gallium driver 24.1.2 for AMD Radeon RX 6600 XT (radeonsi, navi23, LLVM 18.1.6, DRM 3.57, 6.8.12-201.fsync.fc40.x86_64) in use for device "/dev/dri/renderD128"
    LLVM failed to compile a shader correctly: SGPR:VGPR usage is 32:8, but the hw limit is 16:2048
    LLVM failed to compile a shader correctly: SGPR:VGPR usage is 88:12, but the hw limit is 16:2048
    LLVM failed to compile a shader correctly: SGPR:VGPR usage is 32:16, but the hw limit is 16:2048
    fish: Job 1, 'spectacle' terminated by signal SIGABRT (Abort)

Breaks LLVM shader compilation in a few apps. Here is the relevant log from Spectacle.

User Icon dm-zharov commented & provided feedback 4 months ago

I'm getting the same issues related to LLVM shader compilation in "Steam" after update to this MESA package when trying to establish "Remote Play" session.

Jul 01 01:15:04 cloud steam[2668]: LLVM failed to compile a shader correctly: SGPR:VGPR usage is 80:24, but the hw limit is 16:2048
Jul 01 01:15:04 cloud steam-gamescope-session[2496]: pipewire: warning: out of buffers
Jul 01 01:15:04 cloud steam-gamescope-session[2496]: pipewire: warning: out of buffers
Jul 01 01:15:04 cloud steam-gamescope-session[2496]: pipewire: warning: out of buffers
Jul 01 01:15:04 cloud steam[2668]: LLVM failed to compile a shader correctly: SGPR:VGPR usage is 32:16, but the hw limit is 16:2048
Jul 01 01:15:04 cloud steam[2668]: LLVM failed to compile a shader correctly: SGPR:VGPR usage is 48:8, but the hw limit is 16:2048
Jul 01 01:15:04 cloud steam[2668]: LLVM failed to compile a shader correctly: SGPR:VGPR usage is 88:12, but the hw limit is 16:2048
Jul 01 01:15:04 cloud steam[2668]: LLVM failed to compile a shader correctly: SGPR:VGPR usage is 48:16, but the hw limit is 16:2048
Jul 01 01:15:04 cloud steam[2668]: LLVM failed to compile a shader correctly: SGPR:VGPR usage is 32:16, but the hw limit is 16:2048
Jul 01 01:15:04 cloud steam[2668]: LLVM failed to compile a shader correctly: SGPR:VGPR usage is 32:8, but the hw limit is 16:2048
Jul 01 01:15:04 cloud steam[2668]: LLVM failed to compile a shader correctly: SGPR:VGPR usage is 24:8, but the hw limit is 16:2048
Jul 01 01:15:04 cloud steam[2668]: LLVM failed to compile a shader correctly: SGPR:VGPR usage is 32:8, but the hw limit is 16:2048

AMD Radeon RX 6650M (RADV NAVI23)

User Icon jexposit commented & provided feedback 4 months ago

@veilink @dm-zharov I think it is the same issue as: https://gitlab.freedesktop.org/mesa/mesa/-/issues/10927

The commit that is described as the culprit ("ac, radeonsi: remove has_syncobj, has_fence_to_handle") is already addressed in this mesa release, so as mentioned in the last comment, there might be another error: https://gitlab.freedesktop.org/mesa/mesa/-/issues/10927#note_2439112

If you could comment on that bug report or open a new one it'd be helpful.

It looks like an AMD-only issue. I tested it on Intel and the problem is not present.

User Icon jexposit commented & provided feedback 4 months ago

I think it is related to the backport this version of mesa includes from: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29876

As a workaround, you can downgrade mesa to the previous version (mesa-24.1.2-2.fc40 if I remember correctly).

User Icon veilink commented & provided feedback 4 months ago

Yes, I have downgraded to 24.1.2-2.fc40 and everything works as intended.

User Icon veilink commented & provided feedback 4 months ago

It looks like you have already mentioned the issue in the related issue pages and MRs. I will chime in there when there is more development on the issue. Thanks

User Icon veilink commented & provided feedback 4 months ago

@jexposit one thing i forgot to mention is that this issue doesn't happen for me on mesa-git. For posterity this is the mesa-git build i used that had no issues.

P.S. The log I shared is actually someone from the Nobara community and not mine. However, I can also reproduce it with my integrated AMD graphics (Radeon 660M from a Ryzen 5 6600HS)

User Icon jexposit commented & provided feedback 4 months ago

@veilink I think it is caused by the patch backported from: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29876

Adding a comment in that issue clarifying the problem. If you could test mesa-git + that MR it'd be super useful.

I only backported 1 patch from the MR and it'd be good to know if the other patches fix the issue or the MR will introduce a regression.

User Icon veilink commented & provided feedback 4 months ago

@jexposit The build is fine actually. The error happens because I assume that mesa-va-drivers-freeworld from RPMFusion doesn't carry the patch and there is a mismatch between how the two handle stuff. If I uninstall mesa-va-drivers-freeworld or use mesa-va-drivers from Fedora's repos. I can open Spectacle fine but with no VAAPI.

User Icon veilink commented & provided feedback 4 months ago

As there has been an official reply from mesa dev too, I assume that the patches aren't getting pulled from here. I will proceed to create a bugzilla in RPMFusion to prompt a rebuild with these patches.

User Icon veilink commented & provided feedback 4 months ago
karma

Giving good karma now since its already fixed on RPMFusion's end. I have installed the freeworld va driver packages locally and am using this build of mesa. We just need to wait for those freeworld packages to propagate to all mirrors. Thanks again Jose!

User Icon corsepiu commented & provided feedback 4 months ago

@veilink: Where do you see a fix?

I am observing the error, you decribed above when running vlc with mesa-va-drivers-freeworld-24.1.2-1.fc40.x86_64 mesa-vdpau-drivers-freeworld-24.1.2-1.fc40.x86_64 and mesa-*-24.1.2-7.fc40.x86_64 on both my radeon machines.

Downgrading to mesa-*-24.1.2-3.fc40.x86_64 helped.

User Icon veilink commented & provided feedback 4 months ago

@corsepiu https://download1.rpmfusion.org/free/fedora/updates/40/x86_64/repoview/mesa-va-drivers-freeworld.html Download the new builds manually from here or wait for it to reach your local mirrors.

User Icon dm-zharov commented & provided feedback 4 months ago
karma

@veilink It's all right now. Thanks for great work!

User Icon corsepiu commented & provided feedback 4 months ago

These package do NOT work for me:

vlc foo.mp4

VLC media player 3.0.21 Vetinari (revision 3.0.21-0-gdd8bfdbabe8) [0000560c3a5d06a0] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. libva info: VA-API version 1.21.0 libva info: Trying to open /usr/lib64/dri-nonfree/radeonsi_drv_video.so libva info: Trying to open /usr/lib64/dri-freeworld/radeonsi_drv_video.so libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_1_21 libva info: va_openDriver() returns 0 amdgpu: The CS has cancelled because the context is lost. This context is innocent. Aborted (core dumped)

User Icon corsepiu commented & provided feedback 4 months ago

Apologies, scratch my previous comment - I was looking at the wrong machine.

The mesafreeworld-24.1.2-2.fc40.x86_64 packages seem to work.

User Icon injiniero commented & provided feedback 4 months ago

HP EliteBook 745 here with radeon R6 gpu

This update fixes gnome-shell crashes in wayland when any app is launched, but browsing with firefox or opening gnome settings the screen goes black and unresponsive in both wayland and xorg sessions (almost random). The only option is to force poweroff. And the logs doesn't show any core dump. Downgrading mesa-* to 24.0.5-1 is my workaround.

User Icon jexposit commented & provided feedback 4 months ago

@injiniero I'd recommend to comment in the upstream issue: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11352

Or open a new one if you don't consider that they are similar. Hopefully the developers would be able to point into the right direction.


Please login to add feedback.

Metadata
Type
unspecified
Karma
10
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
3
Stable by Time
14 days
Dates
submitted
5 months ago
in testing
5 months ago
in stable
5 months ago
modified
5 months ago
approved
5 months ago
BZ#2292321 gnome shell wayland sessions crash when any app is launched
0
1
BZ#2292734 Black screen with mesa 24.1.1-5
0
0
BZ#2293470 no graphics after updating mesa from 24.0 to 24.1 on iMac 17,1
0
0
BZ#2293846 [AMD] kwin-wayland immediately crashed after an update
0
0
BZ#2294628 Colors changed
0
2
BZ#2294651 mesa 24.1.2-3 messing laptop colors
0
2

Automated Test Results