Backport packages for 24.04.2 HWE stack

[Timo Aaltonen]

[Impact]
The graphics HWE stack from oracular needs to be backported for 24.04.2

libdrm
- build-dep of mesa

spirv-llvm-translator
- build-dep of llvm
- note that some symbols changed/added/dropped on certain archs due to older
  gcc/toolchain, so dh_makeshlibs was overridden to not care about those

llvm-toolchain-19
- new source in noble
- build-dep of mesa
- required for new AMD platforms
- needs two uploads:
  * 1st stage bootstrap build
  * 2nd stage after spirv-llvm-translator has built against 1st stage

mesa
- new major release, last of the series (24.2.8) so it has accumulated all
  the fixes upstream considered worthy for it
- new HW support, Lunar Lake, Battlemage..

meson-1.5
- needed by mesa
- Conflicts/Replaces meson, because otherwise all of the python lib should be
  renamed, along with the includes etc so it's not a trivial amount of work
- tests disabled because four irrelevant ones fail for some reason, doesn't
  affect the mesa backport

[Test case]
We want to cover at least 2-3 different, widely used and already previously supported GPU generations from both AMD and Intel which are supported by this release, as those are the ones that cover most bases; nouveau users tend to switch to the NVIDIA driver after installation. No need to test ancient GPU's supported by mesa-amber. And best to focus on the newer generations (~5y and newer) as the older ones are less likely to break at this point.
- AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*)
- Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/ADL/RKL/RPL/DG2)

Install the new packages and run some tests:
- check that the desktop is still using hw acceleration and hasn't fallen back to swrast/llvmpipe
- run freely available benchmarks that torture the GPU (Unigine Heaven/Valley/Superposition)
- run some games from Steam if possible

and in each case check that there is no gfx corruption happening or worse.

Note that upstream releases have already been tested for OpenGL and Vulkan conformance by their CI.

[Where things could go wrong]
This is a major update of Mesa, there could be regressions but we'll try to catch any with testing. And since it shares bugs with oracular, we'd already know if there are serious issues.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Chris Halse Rogers (raof)]

Hello Timo, or anyone else affected,

Accepted libdrm into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.122-1~ubuntu0.24.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted libdrm (2.4.122-1~ubuntu0.24.04.1) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

libcamera/unknown (ppc64el)
weston/unknown (ppc64el)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/noble/update_excuses.html#libdrm

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Chris Halse Rogers (raof)]

Hello Timo, or anyone else affected,

Accepted llvm-toolchain-19 into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/llvm-toolchain-19/1:19.1.1-1ubuntu1~24.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Chris Halse Rogers (raof)]

Re: meson-1.5 - is there a reason that it Conflicts/Replaces meson? Or, more specifically: how much effort would it be to make it provide a meson-1.5 binary (and associated files, I guess?) and for Mesa to use that?

Alternatively, I'd *also* feel better about it if we didn't disable the tests because of failures. The current state seems like meson-1.5 would be an attractive nuisance?

[Chris Halse Rogers (raof)]

To be clear: “It actually would be quite a lot of effort” is an acceptable answer; I just want to know that it's been considered.

[Chris Halse Rogers (raof)]

Hello Timo, or anyone else affected,

Accepted meson-1.5 into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/meson-1.5/1.5.1-2ubuntu1~24.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Timo Aaltonen (tjaalton)]

I've added a comment about meson conflicts.

thanks!

[Andreas Hasenack (ahasenack)]

NEW review for spirv-llvm-translator-19.

TL;DR I'm just not sure if the symbols overrides is necessary.

This is a backport from oracular. The diff is:

diff --git a/debian/control b/debian/control
index d6f07f3..b6a6be7 100644
--- a/debian/control
+++ b/debian/control
@@ -8,7 +8,7 @@ Uploaders:
 Build-Depends: debhelper-compat (= 13),
  dh-sequence-pkgkde-symbolshelper,
  cmake,
- gcc (>= 4:14),
+ gcc (>= 4:13),
  pkgconf,
  spirv-headers (>= 1.6.1+1.3.275.0),
  spirv-tools,
diff --git a/debian/rules b/debian/rules
index b561e76..8f5dc67 100755
--- a/debian/rules
+++ b/debian/rules
@@ -21,6 +21,9 @@ override_dh_auto_configure:
 execute_after_dh_auto_install:
        mv debian/tmp/usr/bin/llvm-spirv debian/tmp/usr/bin/llvm-spirv-$(LLVM_VERSION)

+override_dh_makeshlibs:
+ dh_makeshlibs -- -c0
+
 # skip tests on big-endian architectures, uses excessive amount (> 40GB) of disk space
 ignore_test_failures = $(if $(filter $(DEB_HOST_ARCH),amd64),,-)
 override_dh_auto_test:

a) d/rules: ok

b) symbols overrides
I tried the build without it, and it also succeeded, and produced the same "noise". Why do we want "-c0", aka, "never fail"?

Quick build log diff between -c1 (default) and -c0:

@@ -328,10 +328,12 @@
    dh_strip -a -O--builddir=build/
 5a5f2cd7171a95fe8c33ac5dde26dcee8c4b8af0
 3138cce2a32f2c8211d163a77b20b0a2bdf2b5c3
- dh_makeshlibs -a -O--builddir=build/
+ debian/rules override_dh_makeshlibs
+make[1]: Entering directory '/home/ubuntu/git/packages/spirv-llvm-translator-19/spirv-llvm-tra+dh_makeshlibs -- -c0
 dpkg-gensymbols: warning: debian/libllvmspirvlib19.1/DEBIAN/symbols doesn't match completely d --- debian/libllvmspirvlib19.1.symbols (libllvmspirvlib19.1_19.1.0-1~ubuntu0.24.04.1_amd64)
-+++ dpkg-gensymbolsVmaWe_ 2024-12-12 19:53:44.982660011 +0000
++++ dpkg-gensymbolsWQmle_ 2024-12-12 19:46:22.107293376 +0000
 @@ -39,7 +39,7 @@
   _ZN4llvm39initializeSPIRVLowerConstExprLegacyPassERNS_12PassRegistryE@Base 13
   _ZN4llvm39initializeSPIRVLowerOCLBlocksLegacyPassERNS_12PassRegistryE@Base 13
@@ -702,6 +704,7 @@
   (optional=templinst)_ZZNKSt7__cxx1112regex_traitsIcE16lookup_classnameIPKcEENS1_10_RegexMask
   (optional=templinst)_ZZNKSt7__cxx1112regex_traitsIcE18lookup_collatenameIPKcEENS_12basic_str
   (optional=templinst)_ZZNKSt8__detail11_AnyMatcherINSt7__cxx1112regex_traitsIcEELb0ELb0ELb0EE
+make[1]: Leaving directory '/home/ubuntu/git/packages/spirv-llvm-translator-19/spirv-llvm-tran
    dh_shlibdeps -a -O--builddir=build/
 dpkg-shlibdeps: warning: diversions involved - output may be incorrect
  diversion by libc6 from: /lib64/ld-linux-x86-64.so.2

c) d/control is missing the maintainer update, since we now have an ubuntu suffix.

d) lintian is clean enough
W: spirv-llvm-translator-19 source: newer-standards-version 4.7.0 (current is 4.6.2)
W: llvm-spirv-19: no-manual-page [usr/bin/llvm-spirv-19]
I: spirv-llvm-translator-19 source: adopted-extended-field (in section for source) XSBC-Original-Maintainer [debian/control:5]

[Andreas Hasenack (ahasenack)]

(b) is ok, I saw the error on our favorite arch (armhf) :)

(c) is minor, as LP will build it just fine, so up to you if you want to fix it.

+1 from me

[Andreas Hasenack (ahasenack)]

Hello Timo, or anyone else affected,

Accepted llvm-toolchain-19 into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/llvm-toolchain-19/1:19.1.1-1ubuntu1~24.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Andreas Hasenack (ahasenack)]

Hello Timo, or anyone else affected,

Accepted mesa into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/24.2.8-1ubuntu1~24.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[AaronMa (mapengyu)]

Hi @ahasenack and @Timo

The 24.2.8-1ubuntu1~24.04.1 is failed to build.

log:
ERROR: libclc shader missing. Consider installing the libclc package

Could you help to fix it please?

Thanks.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted llvm-toolchain-19 (1:19.1.1-1ubuntu1~24.04.2) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

dolfin/2019.2.0~legacy20240219.1c52e83-1ubuntu4 (ppc64el)
rustc-1.79/1.79.0+dfsg1ubuntu1-0ubuntu0.24.04 (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/noble/update_excuses.html#llvm-toolchain-19

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[AaronMa (mapengyu)]

Install: mesa-libgallium:amd64 (24.2.8-1ubuntu1~24.04.1), libllvm19:amd64 (1:19.1.1-1ubuntu1~24.04.2, automatic)
Upgrade: libglx-mesa0:amd64 (24.0.9-0ubuntu0.3, 24.2.8-1ubuntu1~24.04.1), libgbm1:amd64 (24.0.9-0ubuntu0.3, 24.2.8-1ubuntu1~24.04.1), libgl1-mesa-dri:amd64 (24.0.9-0ubuntu0.3, 24.2.8-1ubuntu1~24.04.1), libdrm-common:amd64 (2.4.120-2build1, 2.4.122-1~ubuntu0.24.04.1), libglapi-mesa:amd64 (24.0.9-0ubuntu0.3, 24.2.8-1ubuntu1~24.04.1), libdrm-amdgpu1:amd64 (2.4.120-2build1, 2.4.122-1~ubuntu0.24.04.1), libdrm-radeon1:amd64 (2.4.120-2build1, 2.4.122-1~ubuntu0.24.04.1), libdrm2:amd64 (2.4.120-2build1, 2.4.122-1~ubuntu0.24.04.1), libegl-mesa0:amd64 (24.0.9-0ubuntu0.3, 24.2.8-1ubuntu1~24.04.1), libdrm-intel1:amd64 (2.4.120-2build1, 2.4.122-1~ubuntu0.24.04.1)

mesa-24.2.8-1ubuntu1~24.04.1 works fine on lunarlake.
glxgears show the fps is the same as screen refresh rate as 60.

[Ubuntu SRU Bot (ubuntu-sru-bot)]

All autopkgtests for the newly accepted mesa (24.2.8-1ubuntu1~24.04.1) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

gtk4/4.14.2+ds-1ubuntu1 (amd64)
gtk4/unknown (ppc64el)
libsdl2/unknown (amd64, ppc64el)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/noble/update_excuses.html#mesa

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

[Valentyna (valia0906)]

Updating to mesa after reboot breaks my system, instead of login screen appears white screen with message system breaks, system error

[Timo Aaltonen (tjaalton)]

file a new bug describing everything you did, and then run 'apport-collect <# of the bugreport>'

[Timo Aaltonen (tjaalton)]

@aaronma as the test case says, this needs to be tested on a wider base of hardware than just LNL

[AaronMa (mapengyu)]

sudo apt install libglx-mesa0=24.2.8-1ubuntu1~24.04.1 mesa-libgallium=24.2.8-1ubuntu1~24.04.1 libdrm2=2.4.122-1~ubuntu0.24.04.1 libdrm-common=2.4.122-1~ubuntu0.24.04.1 libegl-mesa0=24.2.8-1ubuntu1~24.04.1 libdrm-amdgpu1=2.4.122-1~ubuntu0.24.04.1 libdrm-intel1=2.4.122-1~ubuntu0.24.04.1 libdrm-intel1=2.4.122-1~ubuntu0.24.04.1 libdrm-radeon1=2.4.122-1~ubuntu0.24.04.1 libgbm1=24.2.8-1ubuntu1~24.04.1 libglapi-mesa=24.2.8-1ubuntu1~24.04.1 libgl1-mesa-dri=24.2.8-1ubuntu1~24.04.1

Tested on:

AMD Ryzen AI 7 PRO 360 w/ Radeon 880M
c4:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 150e (rev d2)

Intel ARL-S:
00:02.0 VGA compatible controller: Intel Corporation Arrow Lake-U [Intel Graphics] (rev 03)

Intel ADL-U:
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] (rev 0c)
01:00.0 VGA compatible controller: NVIDIA Corporation GA103M [GeForce RTX 3080 Ti Mobile] (rev a1)

Ubuntu GUI works fine.
glxgears tests fine.
glmark2 tests fine.

[Timo Aaltonen (tjaalton)]

valentyna, did you file a bug?

[Timo Aaltonen (tjaalton)]

No reply, resetting the verification to done here.

If you only install libgl1-mesa-dri from -proposed it won't pull for instance libgbm1 (which is a bug, fixed in git) meaning that things will be broken.

[Mario Limonciello (superm1)]

So could this release to updates now then?

[Timo Aaltonen (tjaalton)]

The verification of the Stable Release Update for meson-1.5 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package libdrm - 2.4.122-1~ubuntu0.24.04.1

---------------
libdrm (2.4.122-1~ubuntu0.24.04.1) noble; urgency=medium

  * Backport to noble. (LP: #2083020)

 -- Timo Aaltonen <email address hidden> Fri, 02 Aug 2024 15:33:15 +0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package llvm-toolchain-19 - 1:19.1.1-1ubuntu1~24.04.2

---------------
llvm-toolchain-19 (1:19.1.1-1ubuntu1~24.04.2) noble; urgency=medium

  * Backport to noble, stage two. (LP: #2083020)
    - re-enable llvm-spirv-19 build-depends

llvm-toolchain-19 (1:19.1.1-1ubuntu1~24.04.1) noble; urgency=medium

  * Backport to noble, stage one. (LP: #2083020)
    - drop llvm-spirv-19 from build-depends from stage1 (ftbfs)

 -- Timo Aaltonen <email address hidden> Thu, 05 Dec 2024 10:55:29 +0200

[Launchpad Janitor (janitor)]

This bug was fixed in the package spirv-llvm-translator-19 - 19.1.0-1~ubuntu0.24.04.1

---------------
spirv-llvm-translator-19 (19.1.0-1~ubuntu0.24.04.1) noble; urgency=medium

  * Backport to noble. (LP: #2083020)
    - relax gcc dependency, and don't fail if symbols don't match 100%

 -- Timo Aaltonen <email address hidden> Wed, 16 Oct 2024 11:05:49 +0300

[Launchpad Janitor (janitor)]

This bug was fixed in the package meson-1.5 - 1.5.1-2ubuntu1~24.04.1

---------------
meson-1.5 (1.5.1-2ubuntu1~24.04.1) noble; urgency=medium

  * Backport to noble as meson-1.5. (LP: #2083020)
    - disable tests, as four fail but are not critical for the mesa
      build

 -- Timo Aaltonen <email address hidden> Tue, 15 Oct 2024 10:01:54 +0300

[Timo Aaltonen (tjaalton)]

mesa update SRU landed in oracular yesterday, so I'll wait a bit until releasing to noble

[Launchpad Janitor (janitor)]

This bug was fixed in the package mesa - 24.2.8-1ubuntu1~24.04.1

---------------
mesa (24.2.8-1ubuntu1~24.04.1) noble; urgency=medium

  * Backport to noble. (LP: #2083020)
    - build with meson-1.5
    - lower librust-syn-dev dependency

 -- Timo Aaltonen <email address hidden> Mon, 16 Dec 2024 12:17:11 +0200

[Rolf Leggewie (r0lf)]

Apparently, this just hit ports.ubuntu.com for the armhf platform.

I'd consider this SRU to be close to a regression. It adds 140 MB in my case on a headless machine through the dependency on libllvm19. And what is the reason? HWE?! I'm not getting it and I'm not buying it.