This is the last bug on my todo list relating to ROCm in Ubuntu Noble.
If a rebuild doesn't get in until after release, users can set the
environment variable HSA_OVERRIDE_GFX_VERSION=10.3.0 as a workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
There are fixes in rocprim 5.7.1-2 for gfx1031, gfx1032, gfx1033,
gfx1034, gfx1035 and gfx1036 (i.e., all RDNA 2 GPU hardware except for
Navi 21). In rocsparse, the rocprim bug manifests as failures in the
prune_dense2csr_by_percentage tests [1]. The rocprim library is
Thanks Graham!
For posterity, here are the test logs.
** Attachment added: "rocblas-5.5.1+dfsg-5-test.txt.gz"
https://bugs.launchpad.net/ubuntu/+source/rocblas/+bug/2063017/+attachment/5768898/+files/rocblas-5.5.1+dfsg-5-test.txt.gz
--
You received this bug notification because you are a
Public bug reported:
Please sync hipfft 5.7.1-1 (universe) from Debian unstable (main)
The goal of this update is to get as much of the ROCm stack as possible onto
version 5.7.1. While the update of hipfft from 5.5.0 to 5.7.1 is an upstream
version change, this is just matching the same upstream
Public bug reported:
Please sync rocfft 5.7.1-1 (universe) from Debian unstable (main)
The goal of this update is to get as much of the ROCm stack as possible onto
version 5.7.1. While the update of rocfft from 5.5.0 to 5.7.1 is an upstream
version change, this is just matching the same upstream
Public bug reported:
Please sync hipsparse 5.7.1-1 (universe) from Debian unstable (main)
The goal of this update is to get as much of the ROCm stack as possible onto
version 5.7.1. While the update of hipsparse from 5.5.1 to 5.7.1 is technically
a upstream version change, this is just matching
Public bug reported:
Please sync hipblas 5.5.1-4 (universe) from Debian unstable (main)
Changelog entries since current noble version 5.5.1-3build1:
hipblas (5.5.1-4) unstable; urgency=medium
* d/p/0007-hipsolver-compatibility.patch: add guard for hipblasOperation_t,
which had been
Public bug reported:
Please sync hipcub 5.7.1-3 (universe) from Debian unstable (main)
This package update builds the tests for Navi 31, Navi 32 and Navi 33
hardware, as well as fixing errors on Navi 22, Navi 23, Navi 24 and
Rembrandt hardware (if built against rocprim 5.7.1-2 or later; the
Public bug reported:
Please sync rccl 5.4.3-3 (universe) from Debian unstable (main)
This package update adds tests and documentation, as well as enabling
support for Navi 31, Navi 32 and Navi 33 hardware.
Changelog entries since current noble version 5.4.3-1:
rccl (5.4.3-3) unstable;
Public bug reported:
Please sync rocsparse 5.7.1-3 (universe) from Debian unstable (main)
This version builds the library for Navi 31, Navi 32 and Navi 33 GPUs.
There are a collection of other minor fixes.
# d/changelog since 5.7.1-2
rocsparse (5.7.1-3) unstable; urgency=medium
[ Christian
Public bug reported:
Please sync rocblas 5.5.1+dfsg-5 (universe) from Debian unstable (main)
This version builds the library for Navi 31, Navi 32 and Navi 33 GPUs.
I will follow up with a build and test log.
# d/changelog since rocblas 5.5.1+dfsg-4
rocblas (5.5.1+dfsg-5) unstable;
** Attachment added: "rocsolver-5.5.1-5-install.txt"
https://bugs.launchpad.net/ubuntu/+source/rocsolver/+bug/2063016/+attachment/5768702/+files/rocsolver-5.5.1-5-install.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Please sync rocsolver 5.5.1-5 (universe) from Debian unstable (main)
This version builds with -DOPTIMAL=ON, which significantly increases
performance at the cost of increased build time and binary size. It also
builds the library for Navi 31, Navi 32 and Navi 33 GPUs. There
** Description changed:
Please sync rocprim 5.7.1-2 (universe) from Debian unstable (main)
- This sync requires a FeatureFreeze exception. This package version
- requires rocm-hipamd 5.7.1, which is being tracked in
- https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2058606.
+ This
Thank you very much. The ROCm stack is in much better shape now that
rocm-hipamd 5.7.1-3 has migrated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061048
Title:
Please RM arm64 binaries
To
rocrand 5.7.1-4 has been published
** Changed in: rocrand (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060424
Title:
Sync rocrand 5.7.1-4 (universe)
The stdgpu source package no longer produces the libstdgpu-hip-dev and
libstdgpu-hip0d binary packages on arm64 as of
1.3.0+git20220507.32e0517-5ubuntu1. There is a FTBFS bug affecting
stdgpu on amd64 and ppc64el on both noble and noble-proposed, so this
version won't migrate immediately.
To summarize the current state of this ticket, I still request removal
of:
hipcc 5.2.3-12 noble arm64
libamdhip64-5 5.2.3-12 noble arm64
libamdhip64-dev 5.2.3-12 noble arm64
libhiprtc-builtins5 5.2.3-12 noble arm64
libstdgpu-hip-dev 1.3.0+git20220507.32e0517-5 noble arm64
libstdgpu-hip0d
> It is straightforward to drop libamdhip64-dev from the stdgpu build
depends on arm64, so the leftover openmp variants should not block any
future fixes to this package. I will prepare a merge request doing that.
The merge request:
Hi Steve,
I believe the rocm-hipamd request is complete. Here is a listing of the
reasoning for every reverse-depends of rocm-hipamd:
Reverse-Depends
===
* libhiprand-dev (for libamdhip64-dev) - removed in in this request
* libhiprand1 (for libamdhip64-5) - removed in in this
** Patch added: "rm-rocm-arm64-2061253.debdiff"
https://bugs.launchpad.net/ubuntu/+source/stdgpu/+bug/2061253/+attachment/5764916/+files/rm-rocm-arm64-2061253.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
rocm-hipamd FTBFS on arm64 in noble due to
https://bugs.launchpad.net/ubuntu/+source/mumax3/+bug/2032624. It seems
unlikely that a fix for glibc can be merged in time for noble. I have
requested for the arm64 binaries for rocm-hipamd be removed from the
archive so that fixes
Considering stdgpu further, it would be sufficient to only remove:
libstdgpu-hip-dev 1.3.0+git20220507.32e0517-5 noble arm64
libstdgpu-hip0d 1.3.0+git20220507.32e0517-5 noble arm64
It is straightforward to drop libamdhip64-dev from the stdgpu build
depends on arm64, so the leftover openmp
While the build dependency on librocthrust-dev is not an issue, the
build dependency on libamdhip64-dev is.
** Changed in: stdgpu (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The header-only libraries are librocprim-dev, librocthrust-dev and
libhipcub-dev. Those are not arm64 binaries and should not be removed.
My apologies for including them in this list.
However, the arm64 binaries for stdgpu should still be removed. Not
because they depend on librocthrust-dev, but
Oof. You're right. Thank you for catching that error .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061048
Title:
Please RM arm64 binaries
To manage notifications about this bug go to:
** Description changed:
The rocm-hipamd package has been FTBFS on arm64 in noble since the
update to glibc 2.38 last year, as per
https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2032624. In
fact, all libraries written in the HIP language have been FTBFS on arm64
since then.
** Description changed:
The rocm-hipamd package has been FTBFS on arm64 in noble since the
update to glibc 2.38 last year, as per
https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2032624. In
fact, all libraries written in the HIP language have been FTBFS on arm64
since then.
** Description changed:
The rocm-hipamd package has been FTBFS on arm64 in noble since the
update to glibc 2.38 last year, as per
https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2032624. In
fact, all libraries written in the HIP language have been FTBFS on arm64
- since then.
** Also affects: rocrand (Ubuntu)
Importance: Undecided
Status: New
** Also affects: rocprim (Ubuntu)
Importance: Undecided
Status: New
** Also affects: rocthrust (Ubuntu)
Importance: Undecided
Status: New
** Also affects: rocfft (Ubuntu)
Importance: Undecided
Public bug reported:
The rocm-hipamd package has been FTBFS on arm64 in noble since the
update to glibc 2.38 last year, as per
https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2032624. In
fact, all libraries written in the HIP language have been FTBFS on arm64
since then. This is
I had to fight a bit to figure out how to build ucx due to the
"debian.upstream" directory, but I've completed an arm64 build. I can
confirm that when autoconf fails to find libamdhip64-dev, it will just
disable ROCm support.
I must admit, I didn't restart my arm64 build after fixing the
I realized that I should update the maintainer in d/control when
creating an ubuntu revision, so I deleted the original patch and have
reattached it with that change included.
** Patch removed: "rm-rocm-arm64-2060999.debdiff"
I've attached a debdiff for a new version including the necessary
package changes.
** Patch added: "rm-rocm-arm64-2060999.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ucx/+bug/2060999/+attachment/5763926/+files/rm-rocm-arm64-2060999.debdiff
--
You received this bug notification
** Merge proposal linked:
https://code.launchpad.net/~slavik81/ubuntu/+source/ucx/+git/ucx/+merge/464136
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060999
Title:
Please drop libamdhip64-5
** Description changed:
rocm-hipamd FTBFS on arm64 in noble due to
https://bugs.launchpad.net/ubuntu/+source/mumax3/+bug/2032624. It seems
- unlikely that a fix for glibc can be merged for noble. I will be
+ unlikely that a fix for glibc can be merged in time for noble. I will be
requesting
Public bug reported:
rocm-hipamd FTBFS on arm64 in noble due to
https://bugs.launchpad.net/ubuntu/+source/mumax3/+bug/2032624. It seems
unlikely that a fix for glibc can be merged for noble. I will be
requesting that the arm64 binaries for rocm-hipamd be removed from the
archive so that fixes for
All HIP language libraries have been FTBFS on arm64 since the vector
types were added, so this issue has been blocking the libraries from
syncing for several months. The only ones that have been able to update
have been the ones that had always been broken on arm64 for other
reasons.
I've opened
** Merge proposal linked:
https://code.launchpad.net/~slavik81/ubuntu/+source/glibc/+git/glibc/+merge/464058
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2032624
Title:
mumax3 test suite fails
** Patch added: "rocthrust-changelog.diff"
https://bugs.launchpad.net/ubuntu/+source/rocthrust/+bug/2060585/+attachment/5762300/+files/rocthrust-changelog.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "rocthrust-5.7.1-2-install.txt"
https://bugs.launchpad.net/ubuntu/+source/rocthrust/+bug/2060585/+attachment/5762299/+files/rocthrust-5.7.1-2-install.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
# d/changelog since 5.3.3-4
rocthrust (5.7.1-2) unstable; urgency=medium
* Migrate to unstable
* d/rules: use rocprim arch conversion to ensure that the rocthrust tests
behave the same on all RDNA 2 hardware
-- Cordell Bloor Tue, 26 Mar 2024 11:40:24 -0600
rocthrust (5.7.1-2~exp1)
Public bug reported:
Please sync rocthrust 5.7.1-2 (universe) from Debian unstable (main)
This sync requires a FeatureFreeze exception. This package version
requires rocm-hipamd 5.7.1 and would benefit from rocprim 5.7.1, which
are being tracked in https://bugs.launchpad.net/ubuntu/+source/rocm-
# d/changelog since 5.5.1-1
rocprim (5.7.1-2) unstable; urgency=medium
* Migrate to unstable
* Add d/p/test-warp-sort-ppc64el.patch to drop test_warp_sort from
librocprim-tests on ppc64el due to FTBFS when compiling with clang-17.
This is a workaround for bug #1065206
* Add
** Patch added: "changelog.diff"
https://bugs.launchpad.net/ubuntu/+source/rocprim/+bug/2060565/+attachment/5762210/+files/changelog.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060565
** Attachment added: "rocprim-5.7.1-2-install.txt"
https://bugs.launchpad.net/ubuntu/+source/rocprim/+bug/2060565/+attachment/5762209/+files/rocprim-5.7.1-2-install.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Please sync rocprim 5.7.1-2 (universe) from Debian unstable (main)
This sync requires a FeatureFreeze exception. This package version
requires rocm-hipamd 5.7.1, which is being tracked in
https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2058606.
# Why a new
** Patch added: "changelog.diff"
https://bugs.launchpad.net/ubuntu/+source/rocrand/+bug/2060424/+attachment/5762044/+files/changelog.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060424
# d/changelog since 5.3.3-6
rocrand (5.7.1-4) unstable; urgency=medium
* d/rules: use CMAKE_SKIP_INSTALL_RPATH to enable rpath in build tests
-- Cordell Bloor Sun, 07 Apr 2024 20:59:16 -0600
rocrand (5.7.1-3) unstable; urgency=medium
* Add d/p/0005-rocrand-public-hip-host.patch to fix
Public bug reported:
Please sync rocrand 5.7.1-4 (universe) from Debian unstable (main)
This sync requires a FeatureFreeze exception. This package version
requires rocm-hipamd 5.7.1, which is being tracked in
https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2058606.
# Why a new
** Attachment added: "rocrand-5.7.1-4-install.txt"
https://bugs.launchpad.net/ubuntu/+source/rocrand/+bug/2060424/+attachment/5762043/+files/rocrand-5.7.1-4-install.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For comparison, I've uploaded a test log of the rdepends using rocm-
hipamd 5.2.3-12 on the same system. Note that is that the two failures
are identical to the previous log for the rdepends using the rocm-hipamd
5.7.1-3 package.
** Attachment added: "test log for rdepends with rocm-hipamd
** Description changed:
Please sync rocm-hipamd 5.7.1-3 (universe) from Debian unstable (main)
This sync requires a FeatureFreeze exception
# Why a new upstream version is necessary
The Ubuntu Noble FeatureFreeze occurred while the ROCm stack on Debian
was transitioning from
The rdepends for rocm-hipamd are nearly all FTBFS due to the addition of
'cf-protection=return' and 'cf-protection=branch' to the CXXFLAGS. This
is not a problem introduced by rocm-hipamd 5.7.1, but occurs with the
current rocm-hipamd 5.2.3 as well. As such, this update has no effect on
whether
I've pushed the change to salsa, so future versions of rocr-runtime will
be restricted to 64-bit architectures [1]. However, I'm not sure it's
worth uploading a new version of the package just for that. I'll wait
and see for a couple weeks if there are any more bugs reported before
making another
Note that no version of rocr-runtime has ever built successfully for
armhf. rocr-runtime should probably be limited to amd64, arm64 and
ppc64el (as those are the only architectures that have driver support
from AMDGPU KFD).
I've been cautious about dropping architectures that successfully built
It's perhaps worth noting that every version of rocr-runtime has failed
to build on armhf. The failure was not introduced by this update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058594
Title:
** Attachment added: "test log (run prebuilt rocrand tests; build rocprim and
run tests)"
https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2058606/+attachment/5757790/+files/noble_rocm-hipamd_5.7.1-2_tests.log
--
You received this bug notification because you are a member of
** Attachment added: "install log"
https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2058606/+attachment/5757740/+files/noble_rocm-hipamd_5.7.1-2_install.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "build log"
https://bugs.launchpad.net/ubuntu/+source/rocm-hipamd/+bug/2058606/+attachment/5757739/+files/noble_rocm-hipamd_5.7.1-2_build.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Please sync rocm-hipamd 5.7.1-2 (universe) from Debian unstable (main)
This sync requires a FeatureFreeze exception
# Why a new upstream version is necessary
The Ubuntu Noble FeatureFreeze occurred while the ROCm stack on Debian
was transitioning from ROCm 5.2 with
Public bug reported:
Please sync rocr-runtime 5.7.1-2 (universe) from Debian unstable (main)
The 5.7.1-2 version of the package should allow rccl to build
successfully on arm64 and ppc64el. It should also fix HIP on Rembrandt
APUs (gfx1035), which was completely broken in 5.7.1-1 (as illustrated
At least on Ubuntu 18.04, I found that the version from the apt package
starts up much faster than the snap version. I ended up swapping them
using `sudo snap remove gnome-calculator && sudo apt install gnome-
calculator`
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
A couple hours ago, Firefox crashed on me for seemingly no reason. A
flashplugin-installer error dialog popped up, which I dismissed without
reading. I'd seen a similar dialog that said "flashplugin-installer
failure to download extra data files" a few times before and had
This appears to have been fixed at some point. I can no longer
reproduce.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1589753
Title:
Layout breaks after doing things in other tabs
To manage
Scratch that. Still a bug. This problem only occurs if you have zoomed
in a few notches, but it happens regardless of whether the zooming in
was done by an add-on or done through View -> Zoom -> Zoom In.
The trigger for this seems to specifically be the inspector. I don't see
the problem when
Opps. This appears to be a bug in the NoSquint add-on. I see that
NoSquint is no longer maintained as of April. So, that's that. :(
I guess this bug can be closed.
** Changed in: firefox (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
** Attachment added: "the fixed layout after moving the tab into a new window"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1589753/+attachment/4678513/+files/fixed.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I'm pretty sure this wasn't happening a couple months ago, so this seems
to be a recently introduced.
Steps to Reproduce:
1. Visit https://mmistakes.github.io/hpstr-jekyll-theme/
2. Click 3-lined Menu icon.
3. Click 'About'.
4. Right-click the author image and open the
This is still broken in Ubuntu 14.04 (1-2ubuntu2). Was that an
oversight?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1313311
Title:
Broken libscrypt.so symlink
To manage notifications about
70 matches
Mail list logo
