Opened 8 months ago

Closed 4 months ago

Last modified 4 months ago

#22812 closed enhancement (fixed)

mesa-26.0.7

Reported by: Bruce Dubbs Owned by: zeckma
Priority: normal Milestone: 13.1
Component: BOOK Version: git
Severity: medium Keywords:
Cc:

Description

New major version.

Change History (20)

comment:1 by zeckma, 8 months ago

Owner: changed from blfs-book to zeckma
Status: new → assigned
Summary: mesa-26.0.0 → mesa-26.0.0 (wait for a stable release)

comment:2 by Xi Ruoyao, 7 months ago

Summary: mesa-26.0.0 (wait for a stable release) → mesa-26.0.1

Now 26.0.1. We can only try it after 13.0 anyway.

comment:3 by zeckma, 7 months ago

Changes

New Features

  • VK_KHR_relaxed_block_layout on pvr
  • VK_KHR_storage_buffer_storage_class on pvr
  • VK_EXT_external_memory_acquire_unmodified on panvk
  • VK_EXT_discard_rectangles on NVK
  • VK_KHR_present_id on HoneyKrisp
  • VK_KHR_present_id2 on HoneyKrisp
  • VK_KHR_present_wait on HoneyKrisp
  • VK_KHR_present_wait2 on HoneyKrisp
  • VK_KHR_maintenance10 on ANV, NVK, RADV
  • VK_EXT_shader_uniform_buffer_unsized_array on ANV, HK, NVK, RADV
  • VK_EXT_device_memory_report on panvk
  • VK_VALVE_video_encode_rgb_conversion on radv
  • VK_EXT_custom_resolve on RADV
  • GL_EXT_shader_pixel_local_storage on Panfrost v6+
  • VK_EXT_image_drm_format_modifier on panvk/v7
  • VK_KHR_sampler_ycbcr_conversion on panvk/v7
  • sparseResidencyImage2D on panvk v10+
  • sparseResidencyStandard2DBlockShape on panvk v10+
  • VK_KHR_surface_maintenance1 promotion everywhere EXT is exposed
  • VK_KHR_swapchain_maintenance1 promotion everywhere EXT is exposed
  • VK_KHR_dynamic_rendering on PowerVR
  • VK_EXT_multisampled_render_to_single_sampled on panvk
  • VK_KHR_pipeline_binary on HoneyKrisp
  • VK_KHR_incremental_present on pvr
  • VK_KHR_xcb_surface on pvr
  • VK_KHR_xlib_surface on pvr
  • VK_KHR_robustness2 on panvk v10+
  • VK_KHR_robustness2 on HoneyKrisp
  • VK_KHR_robustness2 on hasvk
  • VK_KHR_robustness2 on NVK
  • VK_KHR_robustness2 on Turnip
  • VK_KHR_robustness2 on lavapipe

Bugfixes

25.3 -> 26.0

​https://gitlab.freedesktop.org/mesa/mesa/-/blob/26.0/docs/relnotes/26.0.0.rst

26.0.0 -> 26.0.1

  • Missing Haswell case after a097a3d214eda7fb7b9ff63176754b7260e09e03 leads to bogus assert in intel_perf_mdapi.c
  • Question: Does building Lavapipe on Windows require building "microsoft-experimental" as well?
  • [ANV]: Regression in dxvk Greedfall
  • [ANV][BMG] Building Mesa with Clang causes Missing Skin Textures in UE games - Tekken 8
  • [ANV][DG2][Regression]: Flickering water "boxes" in Civilization VII
  • [RADV] Killer7 has a blue tint with RDNA3/4
  • [bisected] Xe3 regression with piglit tess/barrier-patch.shader_test after cmod prop change
  • [radeonsi] Regression: GL_FEEDBACK returns 0.0 for X-coordinates (Legacy GL)
  • anv, bisected: Genshin Impact wrong shadows, flickering grass
  • turnip: llama.cpp: Running test-backend-ops results in segmentation fault
  • venus crashes in vn_CreateDevice() with latest mesa/main [bisected]

The radeonsi regression fix is notable since we use Legacy GL.

comment:4 by zeckma, 7 months ago

Resolution: → fixed
Status: assigned → closed

comment:5 by Bruce Dubbs, 7 months ago

Resolution: fixed
Status: closed → reopened

Now version 26.0.2.

comment:6 by Xi Ruoyao, 7 months ago

Summary: mesa-26.0.1 → mesa-26.0.2 (wait for final 26.0.x, or 26.1.1, or something important)

comment:7 by Xi Ruoyao, 7 months ago

Milestone: 13.1 → 99-Waiting

comment:8 by zeckma, 7 months ago

Summary: mesa-26.0.2 (wait for final 26.0.x, or 26.1.1, or something important) → mesa-26.0.3 (wait for final 26.0.x, or 26.1.1, or something important)

Now 26.0.3.

comment:9 by zeckma, 6 months ago

Summary: mesa-26.0.3 (wait for final 26.0.x, or 26.1.1, or something important) → mesa-26.0.4 (wait for final 26.0.x, or 26.1.1, or something important)

Now 26.0.4.

comment:10 by Xi Ruoyao, 6 months ago

Just FYI with 26.0.{1,2,3} Zink caused frequent crash of GNOME shell on my system so I've switched back to the direct GL implementation (iris). Not checked 26.0.4 yet.

comment:11 by zeckma, 6 months ago

Summary: mesa-26.0.4 (wait for final 26.0.x, or 26.1.1, or something important) → mesa-26.0.5 (wait for final 26.0.x, or 26.1.1, or something important)

Now 26.0.5. 26.1.0-rc1 has been released as well.

in reply to:  10 comment:12 by zeckma, 6 months ago

Replying to Xi Ruoyao:

Just FYI with 26.0.{1,2,3} Zink caused frequent crash of GNOME shell on my system so I've switched back to the direct GL implementation (iris). Not checked 26.0.4 yet.

Zink for me on my Intel system led to worse performance than the OpenGL driver. It didn't feel worth it at all to use it on that system.

comment:13 by zeckma, 5 months ago

Summary: mesa-26.0.5 (wait for final 26.0.x, or 26.1.1, or something important) → mesa-26.0.6 (wait for final 26.0.x, or 26.1.1, or something important)

Now 26.0.6, and 26.1.0-rc3 has been released as well. We'll probably see 26.1.0 in two weeks.

comment:14 by zeckma, 5 months ago

26.1.0 has been released. The plan is to update to 26.0.7 when it has been released, if it will be released. If not, then wait until 26.1.1.

comment:15 by Xi Ruoyao, 5 months ago

Summary: mesa-26.0.6 (wait for final 26.0.x, or 26.1.1, or something important) → mesa-26.1.0 (wait for final 26.0.x or 26.1.1)

comment:16 by zeckma, 5 months ago

Milestone: 99-Waiting → 13.1
Summary: mesa-26.1.0 (wait for final 26.0.x or 26.1.1) → mesa-26.0.7 (wait for final 26.0.x or 26.1.1)

Now 26.0.7.

comment:17 by zeckma, 5 months ago

Summary: mesa-26.0.7 (wait for final 26.0.x or 26.1.1) → mesa-26.0.7

comment:18 by zeckma, 4 months ago

26.1.1 has been released, but I'm thinking we should hold off on that, until this comes in.

In the mean time, I think I have a better scheme for handling Mesa updates.

Right now, the scheme is: 26.0.1 -> 26.0.7 -> 26.1.1 -> 26.1.<last>

The idea behind this was that the first bugfix release will give us a somewhat stable but good idea of what bugs are in the newest major/minor release.

I think we could still aim for that while creating a better user experience.

I think going for a scheme like 26.0.<middle> -> 26.0.<last> -> 26.1.<middle> -> 26.1.<last> is more stable, less chaotic, and still moderately gets us that idea I mentioned, of finding bugs.

Granted, all-in-all, it's up to the user what version they want to use. I'm mostly speaking about this since things can be a bit hectic from the last point release to the next major/minor and its bugfix, before going radio silent until the very last bugfix release.

comment:19 by zeckma, 4 months ago

Resolution: → fixed
Status: reopened → closed

comment:20 by zeckma, 4 months ago

Bugfixes from 26.0.2->26.0.7 (inclusive):

  • 26.0.1 fails to build: create_context.c: error: 'struct glx_screen' has no member named 'frontend_screen'
  • A770: Counter-Strike 2 visual glitches (regression)
  • Bisected regression: Assertion texObj->pt == view->texture failed.
  • Kodi regression with panthor >= 1.7 after updating to Linux 7.0-rc1
  • MDK2 HD (opengl) has most elements rendered as black
  • Mesa 25.3 amdgpu memory issue
  • OpenGL 4.1 VRAM Memory Leak with setting uniform variables
  • Panfrost Bifrost compiler assertion failure: wrong vectorization in bi_alu_src_index (Mesa 26.0.0)
  • RADV: RDNA4 visual corruption in DX11 (DXVK) – Mafia III character model glitches, AMDVLK renders correctly (9070XT)
  • [radeonsi] Regression: GL_FEEDBACK returns 0.0 for X-coordinates (Legacy GL)
  • glsl: spec@glsl-es-1.00@linker@glsl-mismatched-uniform-precision-unused broken
  • ir3: ir3_get_predicate() vs &ctx->build
  • r300 , regression , bisected : Glitches with Sauerbraten
  • r300: HiZ related dEQP failures
  • Portal hard locks the machine on rv350.
  • Turnip crash with lazy depth textures: GPUMEM_BIND_RANGES failed (Not a typewriter)
  • [regression] Left 4 Dead 2 crashing when joining or starting survival with "Official Dedicated" servers
  • lavapipe: crash in caselist
  • zink: mesh shaders broken
  • Accumulation of black squares with OpenGL applications at high resolutions (hiz-related)
  • RADV: Invalid hitAttributeEXT value when using function-call RT pipelines
  • Segmentation fault in gm200_validate_sample_locations with Firefox on GTX 1070 Ti (nouveau)
  • Vulkan CTS regression bisected to 5d2c17a5fdce ("vtn: skip make-available/visible for shared")
  • [anv] Intel ARC B390 | Horizon Forbidden West | DX12 | Flashing effects
  • [radeonsi] Missing ground texture in Lethis Path of the Progress
  • amdgpu reset/crash when simulating stereo camera
  • building mesa_clc on ubutu-26.04 with gcc-16 fails link
  • util: Build regression with MSYS2 MinGW-W64 x64 clang 21 on 26.0.0-rc3
  • wsi: assert(chain->dxgi); may failed under venus for win32
  • Is maxFragmentCombinedOutputResources=16 in Honeykrisp reflects an actual HW limit?
  • Mesa LLVMpipe Memory Leak
  • glcpp: incorrect macro expansion in token pasting
  • nir: possible exactness bug in reassociate

There's a couple of memory leaks and memory management, but I'm not marking them as security issues since they seem to be moreso regressions than security issues. Users would still face them at run time, though.

Note: See TracTickets for help on using tickets.