Backport packages for 22.04.2 HWE stack

Bug #1991761 reported by Timo Aaltonen
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
directx-headers (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Fix Released
Undecided
Unassigned
libdrm (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Fix Released
Undecided
Unassigned
llvm-toolchain-15 (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Fix Released
Undecided
Unassigned
mesa (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Fix Released
Undecided
Unassigned
spirv-headers (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Fix Released
Undecided
Unassigned
spirv-llvm-translator-14 (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Fix Released
Undecided
Unassigned
spirv-llvm-translator-15 (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Fix Released
Undecided
Unassigned

Bug Description

[Impact
The graphics HWE stack from kinetic needs to be backported for 22.04.2

directx-headers
- build-dep of the new Mesa

libdrm
- build-dep of the new Mesa

llvm-15
- new package in jammy
- build-dep of the new Mesa

mesa
- new major release (22.2.x)
- new HW support, like AMD RDNA3, Intel DG2

spirv-headers
- needed by s-l-t-15

spirv-llvm-translator-14
- needed to bootstrap libclc from llvm

spirv-llvm-translator-15
- needed for the actual libclc-15 after initial bootstrap

Bootstrapping plan:
- s-l-t-14 built from NEW
- llvm-15 built with s-l-t-14
- s-l-t-15 built against llvm-15
- llvm-15 built again with s-l-t-15
-> mesa ready for building

[Test case]
Install the new mesa on various hw, see that everything still works like before or better.

spirv-headers:
- test reverse-build-deps that they still build
Reverse-Build-Depends
* glslang
* intel-graphics-compiler
* spirv-llvm-translator-14
* spirv-llvm-translator-15
* spirv-tools
* vkbasalt
* vkd3d
* vulkan-validationlayers

[Where things could go wrong]
This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 22.2.x in order to minimize the chance for those.

Timo Aaltonen (tjaalton)
description: updated
Changed in directx-headers (Ubuntu):
status: New → Invalid
Changed in libdrm (Ubuntu):
status: New → Invalid
Changed in llvm-toolchain-15 (Ubuntu):
status: New → Invalid
Changed in mesa (Ubuntu):
status: New → Invalid
Simon Chopin (schopin)
tags: added: foundations-triage-discuss
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

needs also spirv-llvm-translator-14 to build libclc-15, or s-l-t-15 plus spirv-headers backported

Changed in directx-headers (Ubuntu Jammy):
status: New → In Progress
Changed in libdrm (Ubuntu Jammy):
status: New → In Progress
Changed in llvm-toolchain-15 (Ubuntu Jammy):
status: New → In Progress
Changed in mesa (Ubuntu Jammy):
status: New → In Progress
Changed in spirv-llvm-translator-14 (Ubuntu):
status: New → Invalid
Changed in spirv-llvm-translator-14 (Ubuntu Jammy):
status: New → In Progress
Timo Aaltonen (tjaalton)
description: updated
Timo Aaltonen (tjaalton)
description: updated
Timo Aaltonen (tjaalton)
description: updated
Timo Aaltonen (tjaalton)
Changed in spirv-llvm-translator-15 (Ubuntu):
status: New → Invalid
Changed in spirv-llvm-translator-15 (Ubuntu Jammy):
status: New → In Progress
Timo Aaltonen (tjaalton)
Changed in spirv-headers (Ubuntu):
status: New → Invalid
description: updated
Revision history for this message
Chris Halse Rogers (raof) wrote : Please test proposed package

Hello Timo, or anyone else affected,

Accepted directx-headers into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/directx-headers/1.606.4-1~ubuntu0.22.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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

Changed in directx-headers (Ubuntu Jammy):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-jammy
Revision history for this message
Chris Halse Rogers (raof) wrote :

I know it doesn't have any rdepends in the archive, but this includes a libdrm-tegra0 ABI break without bumping SONAME; what sort of consumers of libdrm-tegra0 are likely to exist? What risk mitigations could we implement?

Revision history for this message
Chris Halse Rogers (raof) wrote :

Hello Timo, or anyone else affected,

Accepted spirv-headers into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/spirv-headers/1.6.1+1.3.216.0-1~ubuntu0.22.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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

Changed in spirv-headers (Ubuntu Jammy):
status: New → Fix Committed
Revision history for this message
Chris Halse Rogers (raof) wrote :

spirv-headers is build-depended on by several packages; could we do test-rebuilds of those as a part of verification, please.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

raof: if you mean removing the ioctl thing, they're apparently unused:

commit bec2a28e98f430f4a82b085b4d1c69a98988359f
Author: Thierry Reding <email address hidden>
Date: Fri Jul 9 19:53:52 2021 +0200

    tegra: Remove unused IOCTL implementations

    The DRM_TEGRA_GEM_{GET,SET}_FLAGS and DRM_TEGRA_GEM_{GET,SET}_TILING
    IOCTLs were badly designed and have since been obsoleted by framebuffer
    modifiers. Remove these implementations to make it clear their usage is
    discouraged.

--- a/tegra/tegra-symbols.txt
+++ b/tegra/tegra-symbols.txt
@@ -1,11 +1,7 @@
-drm_tegra_bo_get_flags
 drm_tegra_bo_get_handle
-drm_tegra_bo_get_tiling
 drm_tegra_bo_map
 drm_tegra_bo_new
 drm_tegra_bo_ref
-drm_tegra_bo_set_flags
-drm_tegra_bo_set_tiling
 drm_tegra_bo_unmap
 drm_tegra_bo_unref
 drm_tegra_bo_wrap

I don't see other breakage, just additions

description: updated
Revision history for this message
Chris Halse Rogers (raof) wrote :

Right, but as far as the archive is concerned, libdrm-tegra0 itself is unused :)

What code *does* use libdrm-tegra0, and how sure are we that it doesn't use those symbols (even accidentally)?

Revision history for this message
Chris Halse Rogers (raof) wrote :

llvm-toolchain-15 will presumably need to be promoted to main in jammy-proposed/-updates, yes? I'm not familiar with the process of backporting NEW packages into main; presumably because it's in main in lunar that'll be ok, but I'd like to check with the MIR team that my assumption is correct.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

re: tegra, I have no idea, mesa surely doesn't use any of this

llvm: looking at focal, it seems libllvmNN is in main, the rest is in universe

Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Hello Timo, or anyone else affected,

Accepted spirv-llvm-translator-15 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/spirv-llvm-translator-15/15.0.0-1~ubuntu0.22.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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

Changed in spirv-llvm-translator-15 (Ubuntu Jammy):
status: In Progress → Fix Committed
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Hello Timo, or anyone else affected,

Accepted libdrm into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.113-2~ubuntu0.22.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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

Changed in libdrm (Ubuntu Jammy):
status: In Progress → Fix Committed
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Accepted the new libdrm, thanks! But I see there that libkms got removed in this version, but I assume it's not something we care about?

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

right, libkms got removed upstream so kms-steal-crtc and kms-universal-planes got removed from the package

commit 2b997bb4bb688be00620887c8646ff24ccb9396b
Author: Daniel Stone <email address hidden>
Date: Tue Mar 29 13:59:57 2022 +0100

    libkms: Remove libkms completely

    libkms was a very early attempt at a KMS management library, that only
    got as far as handling requests to create buffers. It has since been
    superseded by GBM in doing this, which everyone uses, unlike libkms
    which no-one uses.

    Remove it from the tree to avoid any confusion.

Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (libdrm/2.4.113-2~ubuntu0.22.04.1)

All autopkgtests for the newly accepted libdrm (2.4.113-2~ubuntu0.22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

mutter/42.5-0ubuntu1 (amd64)

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/jammy/update_excuses.html#libdrm

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

Thank you!

Revision history for this message
Łukasz Zemczak (sil2100) wrote : Please test proposed package

Hello Timo, or anyone else affected,

Accepted llvm-toolchain-15 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/llvm-toolchain-15/1:15.0.6-3~ubuntu0.22.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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

Changed in llvm-toolchain-15 (Ubuntu Jammy):
status: In Progress → Fix Committed
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Hello Timo, or anyone else affected,

Accepted mesa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/22.2.5-0ubuntu0.1~22.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-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. 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.

Changed in mesa (Ubuntu Jammy):
status: In Progress → Fix Committed
Timo Aaltonen (tjaalton)
Changed in spirv-llvm-translator-14 (Ubuntu Jammy):
status: In Progress → Fix Committed
Revision history for this message
Mario Limonciello (superm1) wrote (last edit ):

At least from AMD's tests, backported mesa stack is working properly with RDNA3. Adjusting tag accordingly.

tags: added: verification-done verification-done-jammy
removed: verification-needed verification-needed-jammy
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package directx-headers - 1.606.4-1~ubuntu0.22.04.1

---------------
directx-headers (1.606.4-1~ubuntu0.22.04.1) jammy; urgency=medium

  * Backport to jammy. (LP: #1991761)

 -- Timo Aaltonen <email address hidden> Wed, 05 Oct 2022 11:33:25 +0300

Changed in directx-headers (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libdrm - 2.4.113-2~ubuntu0.22.04.1

---------------
libdrm (2.4.113-2~ubuntu0.22.04.1) jammy; urgency=medium

  * Backport to jammy. (LP: #1991761)
  * patches, symbols: Revert dropping unused tegra IOCTL.

 -- Timo Aaltonen <email address hidden> Tue, 06 Dec 2022 09:19:45 +0200

Changed in libdrm (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package llvm-toolchain-15 - 1:15.0.6-3~ubuntu0.22.04.2

---------------
llvm-toolchain-15 (1:15.0.6-3~ubuntu0.22.04.2) jammy; urgency=medium

  * Bootstrap build #2, bump to build with llvm-spirv-15. (LP: #1991761)

 -- Timo Aaltonen <email address hidden> Thu, 15 Dec 2022 16:25:28 +0200

Changed in llvm-toolchain-15 (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mesa - 22.2.5-0ubuntu0.1~22.04.1

---------------
mesa (22.2.5-0ubuntu0.1~22.04.1) jammy; urgency=medium

  * Backport to jammy. (LP: #1991761)

 -- Timo Aaltonen <email address hidden> Thu, 15 Dec 2022 16:35:13 +0200

Changed in mesa (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package spirv-headers - 1.6.1+1.3.216.0-1~ubuntu0.22.04.1

---------------
spirv-headers (1.6.1+1.3.216.0-1~ubuntu0.22.04.1) jammy; urgency=medium

  * Backport to jammy. (LP: #1991761)

 -- Timo Aaltonen <email address hidden> Thu, 13 Oct 2022 19:13:10 +0300

Changed in spirv-headers (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package spirv-llvm-translator-14 - 14.0.0-3~ubuntu0.22.04.1

---------------
spirv-llvm-translator-14 (14.0.0-3~ubuntu0.22.04.1) jammy; urgency=medium

  * Backport to jammy. (LP: #1991761)
    - Drop support for symbols, needs newer pkg-kde-tools

 -- Timo Aaltonen <email address hidden> Fri, 07 Oct 2022 20:14:03 +0300

Changed in spirv-llvm-translator-14 (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package spirv-llvm-translator-15 - 15.0.0-1~ubuntu0.22.04.1

---------------
spirv-llvm-translator-15 (15.0.0-1~ubuntu0.22.04.1) jammy; urgency=medium

  * Backport to jammy. (LP: #1991761)
    - drop support for symbols, needs newer pkg-kde-tools

 -- Timo Aaltonen <email address hidden> Thu, 13 Oct 2022 15:56:38 +0300

Changed in spirv-llvm-translator-15 (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for directx-headers 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.

Revision history for this message
Sebastian Castro (sebas-a-castro) wrote (last edit ):
Download full text (3.8 KiB)

We found a breaking change with this when running an application that relies on ogre 1.9 for rendering inside a Docker container based on the ubuntu:jammy image.

We could confirm that the upgrade causing this was as follows, because the issue goes away when downgrading versions:

[UPGRADE] libegl-mesa0:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1
[UPGRADE] libgbm-dev:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1
[UPGRADE] libgbm1:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1
[UPGRADE] libgl1-mesa-dri:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1
[UPGRADE] libglapi-mesa:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1
[UPGRADE] libglx-mesa0:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1

For completeness, the full stack trace is:

Stack trace (most recent call last) in thread 18237:
#25 Object "[0xffffffffffffffff]", at 0xffffffffffffffff, in
#24 Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f2ba75089ff, in
#23 Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f2ba7476b42, in
#22 Object "/lib/x86_64-linux-gnu/libstdc++.so.6", at 0x7f2ba3a4d2b2, in
#21 Object "/usr/lib/x86_64-linux-gnu/ign-gazebo-6/plugins/libignition-gazebo-sensors-system.so", at 0x7f2b6456b2bf, in ignition::gazebo::v6::systems::SensorsPrivate::RenderThread()
#20 Object "/usr/lib/x86_64-linux-gnu/ign-gazebo-6/plugins/libignition-gazebo-sensors-system.so", at 0x7f2b6456aba6, in ignition::gazebo::v6::systems::SensorsPrivate::RunOnce()
#19 Object "/opt/underlay_ws/install/lib/libignition-sensors6.so.6", at 0x7f2b76db113e, in ignition::sensors::v6::Manager::RunOnce(std::chrono::duration<long, std::ratio<1l, 1000000000l> > const&, bool)
#18 Object "/opt/underlay_ws/install/lib/libignition-sensors6.so.6", at 0x7f2b76db95b5, in ignition::sensors::v6::Sensor::Update(std::chrono::duration<long, std::ratio<1l, 1000000000l> > const&, bool)
#17 Object "/opt/underlay_ws/install/lib/libignition-sensors6-rgbd_camera.so.6", at 0x7f2b6436a020, in ignition::sensors::v6::RgbdCameraSensor::Update(std::chrono::duration<long, std::ratio<1l, 1000000000l> > const&)
#16 Object "/opt/underlay_ws/install/lib/libignition-sensors6-rendering.so.6", at 0x7f2b64282a6d, in ignition::sensors::v6::RenderingSensor::Render()
#15 Object "/usr/lib/x86_64-linux-gnu/ign-rendering-6/engine-plugins/libignition-rendering-ogre.so", at 0x7f2b5c6adc85, in ignition::rendering::v6::OgreDepthCamera::PostRender()
#14 Object "/usr/lib/x86_64-linux-gnu/ign-rendering-6/engine-plugins/libignition-rendering-ogre.so", at 0x7f2b5c71d743, in ignition::rendering::v6::OgreRenderTexture::Buffer(float*)
#13 Object "/lib/x86_64-linux-gnu/libOgreMain.so.1.9.0", at 0x7f2b5c32c90a, in Ogre::RenderTexture::copyContentsToMemory(Ogre::PixelBox const&, Ogre::RenderTarget::FrameBuffer)
#12 Object "/usr/lib/x86_64-linux-gnu/OGRE-1.9.0/RenderSystem_GL.so", at 0x7f2aeac67a85, in Ogre::GLTextureBuffer::download(Ogre::PixelBox const&)
#11 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b26225cdd, in
#10 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b262246ae, in
#9 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b262244b0, in
#8 Object "/usr/l...

Read more...

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

thanks, but file a new bug please

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

ah, see this is 2004649 now

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.