Skip to content

mesa: update to 26.0.1#58664

Open
onlylunix wants to merge 1 commit intovoid-linux:masterfrom
onlylunix:mesa-update
Open

mesa: update to 26.0.1#58664
onlylunix wants to merge 1 commit intovoid-linux:masterfrom
onlylunix:mesa-update

Conversation

@onlylunix
Copy link
Contributor

Testing the changes

  • I tested the changes in this PR: YES

Local build testing

  • I built this PR locally for my native architecture, (x86_64-LIBC)

@onlylunix onlylunix marked this pull request as draft February 3, 2026 13:24
@onlylunix onlylunix marked this pull request as ready for review February 7, 2026 12:30
@onlylunix onlylunix changed the title mesa: update to 25.3.4 mesa: update to 25.3.4\5 Feb 7, 2026
@onlylunix onlylunix changed the title mesa: update to 25.3.4\5 mesa: update to 25.3.5 Feb 7, 2026
@emjomi
Copy link

emjomi commented Feb 7, 2026

Hey, thank you very much! I’m really looking forward to when this will be merged, because the problems with Vulkan on Intel iGPU are really annoying me

@onlylunix
Copy link
Contributor Author

onlylunix commented Feb 7, 2026

Unfortunately, Mesa 25.3.5 still contains Vulkan bugs for Intel iGPUs.
I just experienced this in WarThunder:

$ dmesg
...
[16308.490404] i915 0000:00:02.0: Using 39-bit DMA addresses
[16711.735723] i915 0000:00:02.0: [drm] Resetting rcs0 for CS error
[16711.735787] i915 0000:00:02.0: [drm] aces[8769] context reset due to GPU hang
[16712.508228] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:98968f5e, in aces [8769]
[16721.204740] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
[16721.204799] i915 0000:00:02.0: [drm] aces[8769] context reset due to GPU hang
[16721.388731] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:8ed8fff3, in aces [8769]
[16723.212455] i915 0000:00:02.0: [drm] Resetting rcs0 for CS error
[16723.212520] i915 0000:00:02.0: [drm] aces[8769] context reset due to GPU hang
[16723.490002] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:84dffffa, in aces [8769]

@emjomi
Rolling back to mesa 25.1.9 solves the problem.

@onlylunix onlylunix marked this pull request as draft February 12, 2026 12:22
@onlylunix
Copy link
Contributor Author

Mesa 26.0.0, iGPU Intel HD630, WarThunder, Vulkan

[ 3234.702248] i915 0000:00:02.0: [drm] Resetting rcs0 for CS error
[ 3234.702309] i915 0000:00:02.0: [drm] aces[2234] context reset due to GPU hang
[ 3235.617039] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:84dfbffc, in aces [2234]
[ 3255.368437] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
[ 3255.368509] i915 0000:00:02.0: [drm] aces[2234] context reset due to GPU hang
[ 3255.843385] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:84dfbffc, in aces [2234]
[ 3259.020771] i915 0000:00:02.0: [drm] Resetting rcs0 for CS error
[ 3259.020833] i915 0000:00:02.0: [drm] aces[2234] context reset due to GPU hang
[ 3259.428562] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dffffb, in aces [2234]

@onlylunix onlylunix marked this pull request as ready for review February 12, 2026 22:33
@onlylunix onlylunix changed the title mesa: update to 25.3.5 mesa: update to 26.0.0 Feb 12, 2026
@onlylunix
Copy link
Contributor Author

Mesa 25.3.6 is also buggy

[ 2552.253049] i915 0000:00:02.0: Using 39-bit DMA addresses
[ 3621.622782] Fence expiration time out i915-0000:00:02.0:aces[1704]:27524!
[ 3621.633725] Fence expiration time out i915-0000:00:02.0:aces[1704]:27526!
[ 3641.790828] Fence expiration time out i915-0000:00:02.0:aces[1704]:27584!
[ 3641.949814] i915 0000:00:02.0: [drm] Resetting rcs0 for CS error
[ 3641.949873] i915 0000:00:02.0: [drm] aces[1704] context reset due to GPU hang
[ 3642.703925] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dffffb, in aces [1704]
[ 3878.536338] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
[ 3878.536398] i915 0000:00:02.0: [drm] aces[1704] context reset due to GPU hang
[ 3879.101272] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:87f9ffff, in aces [1704]
[ 3900.516440] Fence expiration time out i915-0000:00:02.0:aces[1704]:10!
[ 3920.550599] Fence expiration time out i915-0000:00:02.0:aces[1704]:12!
[ 3941.414038] Fence expiration time out i915-0000:00:02.0:aces[1704]:3bc!
[ 3961.415682] Fence expiration time out i915-0000:00:02.0:aces[1704]:3be!
[ 3962.248969] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
[ 3962.249040] i915 0000:00:02.0: [drm] aces[1704] context reset due to GPU hang
[ 3962.616638] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dffffb, in aces [1704]
[ 3983.906479] Fence expiration time out i915-0000:00:02.0:aces[1704]:10!
[ 4003.952087] Fence expiration time out i915-0000:00:02.0:aces[1704]:12!
[ 4024.152938] Fence expiration time out i915-0000:00:02.0:aces[1704]:30!
[ 4024.800527] xfce4-terminal[1695]: segfault at 90 ip 00007f82061a6f56 sp 00007ffe3d918230 error 4 in libgdk-3.so.0.2418.32[86f56,7f820614e000+7c000] likely on CPU 0 (core 0, socket 0)
[ 4024.800539] Code: fb ff 48 89 df e8 1a f9 fa ff 4c 89 ff 48 89 c3 e8 af 82 fb ff 44 8b 5c 24 10 85 c0 74 07 49 89 9f 88 00 00 00 48 8b 5c 24 08 <49> 8b b4 24 90 00 00 00 44 89 5c 24 10 48 89 df e8 d5 8c fb ff 49
[ 4024.805925] xfdesktop[1555]: segfault at 90 ip 00007f39b107ff56 sp 00007ffe341268d0 error 4 in libgdk-3.so.0.2418.32[86f56,7f39b1027000+7c000] likely on CPU 1 (core 1, socket 0)
[ 4024.805935] Code: fb ff 48 89 df e8 1a f9 fa ff 4c 89 ff 48 89 c3 e8 af 82 fb ff 44 8b 5c 24 10 85 c0 74 07 49 89 9f 88 00 00 00 48 8b 5c 24 08 <49> 8b b4 24 90 00 00 00 44 89 5c 24 10 48 89 df e8 d5 8c fb ff 49

The entire 25.3 branch contains errors for Intel iGPUs.

@onlylunix onlylunix marked this pull request as draft February 22, 2026 04:10
@onlylunix onlylunix marked this pull request as ready for review February 25, 2026 21:16
@onlylunix onlylunix changed the title mesa: update to 26.0.0 mesa: update to 26.0.1 Feb 25, 2026
@onlylunix
Copy link
Contributor Author

onlylunix commented Feb 25, 2026

Mesa 26.0.1, iGPU Intel HD630, WarThunder, Vulkan

[ 2198.885028] i915 0000:00:02.0: [drm] Resetting rcs0 for CS error
[ 2198.885092] i915 0000:00:02.0: [drm] aces[2533] context reset due to GPU hang
[ 2199.575945] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:87cabbf2, in aces [2533]
[ 2200.883985] i915 0000:00:02.0: Using 39-bit DMA addresses
[ 2304.713061] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
[ 2304.713132] i915 0000:00:02.0: [drm] aces[2533] context reset due to GPU hang
[ 2305.156326] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dffffb, in aces [2533]
[ 2313.865088] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
[ 2313.865159] i915 0000:00:02.0: [drm] aces[2533] context reset due to GPU hang
[ 2314.187844] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:87d79ffe, in aces [2533]
[ 2317.896996] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out
[ 2317.897055] i915 0000:00:02.0: [drm] aces[2533] context reset due to GPU hang
[ 2318.167580] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:87f9ffff, in aces [2533]

upd: The error appears after 5-45 minutes of play.

Rolling back to mesa 25.1.9 solves the problem.

@onlylunix
Copy link
Contributor Author

@dogknowsnx
something broke

@dkwo
Copy link
Contributor

dkwo commented Feb 26, 2026

@onlylunix Did you rebase? Also, from the release 26.0.1 announcement:

This release and 25.3.6 (already out) contain a security fix preventing
out-of-bounds memory access in WebGPU.
They should be deployed to users as quickly as possible.

@dogknowsnx
Copy link
Contributor

dogknowsnx commented Feb 26, 2026

@dogknowsnx something broke

Haven't tried building mesa in a while. What dkwo said.

EDIT: Fwiw, no issues so far running v26.0.1 (minimal build) on Intel HD 620 and Iris Xe

@dkwo
Copy link
Contributor

dkwo commented Feb 26, 2026

For me, the current version failed to build, but it builds and works fine on aarch64 if I disable _have_nv=yes and _have_amd=yes.

@onlylunix
Copy link
Contributor Author

@dogknowsnx
You misunderstood me.
Everything builds fine on the local computer.
The problem is this: https://github.com/void-linux/void-packages/actions/runs/22415897358/job/64901314718?pr=58664#step:3:190
@classabbyamp @Duncaen
who is in charge of this?

@classabbyamp
Copy link
Member

just rerun it, that's a transient networking issue

@onlylunix
Copy link
Contributor Author

onlylunix commented Feb 26, 2026

just rerun it, that's a transient networking issue

@classabbyamp
I can't find the corresponding control in my browser.
I probably don't have permission.

@classabbyamp
Copy link
Member

force-push

@onlylunix
Copy link
Contributor Author

onlylunix commented Feb 26, 2026

@classabbyamp

0 $ git push -f
Everything up-to-date
0 $ 

:)

@classabbyamp
Copy link
Member

amend so the commit hash changes

please stop pinging me in every comment, I'm subscribed to the thread

@onlylunix
Copy link
Contributor Author

Сan force-push changes like this until you're blue in the face:
https://github.com/void-linux/void-packages/actions/runs/22451787121/job/65022009877?pr=58664#step:7:199

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants