PS: the Jammy verification done in comment 31 used version
2.37.2-4ubuntu3.1 (staged in this bug), and that in comment 39 used
(newer) version 2.37.2-4ubuntu3.2 (also staged, in bug 2048092) -- both
have positive results.
BTW, since the newer upload is still planned for staging, not removing
the
Jammy verification done in comments 31 (with tag flip) and 39.
Lunar is now Won't Fix (2024-01-17), thus removing lunar tags.
** Tags removed: block-proposed-lunar verification-done-lunar
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Verified on 22.04 using util-linux=2.37.2-4ubuntu3.2
$ apt policy util-linux
util-linux:
Installed: 2.37.2-4ubuntu3.2
Candidate: 2.37.2-4ubuntu3.2
Version table:
*** 2.37.2-4ubuntu3.2 500
500 http://ports.ubuntu.com/ubuntu-ports jammy-proposed/main arm64
Packages
100
** Changed in: util-linux (Ubuntu Lunar)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2019856
Title:
Add missing ARM-cores
All autopkgtests have now passed (lunar/jammy).
https://ubuntu-archive-team.ubuntu.com/proposed-migration/lunar/update_excuses.html#util-linux
https://ubuntu-archive-team.ubuntu.com/proposed-migration/jammy/update_excuses.html#util-linux
--
You received this bug notification because you are a
The autopkgtests failures in lunar seem to be a kernel issue during the
initialization of the virtio rng driver, when the mutex for
(generic/core) hw rng is acquired (apparently something else is holding
it indefinitely, thus the blocked task warnings show up, and it seems
the VM doesn't proceed
The autopkgtests failures in jammy seem to be of various sorts, but are
not expected to be related to this code change at all. I've skimmed
through them, and some seemed worth of retries (timeouts, network
issues, etc).
--
You received this bug notification because you are a member of Ubuntu
Thanks, I will mark these SRUs as block-proposed-$release and accept
them now.
> It'd be interesting to set a time frame - if we don't have any of those
> happening in, let's say, 6 months, would it be fair to re-consider the SRU?
In my view this would still not be an SRU that should be released
The approach to take would be to add a block-proposed-jammy tag and then
the SRU can be processed and it will just say in proposed until another
SRU gets along that replaces (and includes) it, but at least it's built
and reviewed and visible to everyone.
--
You received this bug notification
Steve / #17,
Sorry, this was discussed internally at the time, but for some reason
the answers didn't make it here back then.
If we get another bug (e.g., another simple change from existing util-
linux bugs, that still makes sense to be SRUed) that can be combined
with this SRU, would that be
Steve,
We got the okay from the user to hold this until we have another high-
impact change. It'd be interesting to set a time frame - if we don't
have any of those happening in, let's say, 6 months, would it be fair to
re-consider the SRU?
Thanks
--
You received this bug notification because
Mauricio, this SRU is still waiting for an answer to
https://bugs.launchpad.net/ubuntu/+source/util-
linux/+bug/2019856/comments/17
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
I was about to ask *why* Ubuntu users need this change before I read
Steve's comment. It might be helpful to expand on that, because without
a full explanation, we (SRU team) are only really _speculating_ on the
actual user impact.
--
You received this bug notification because you are a member
This looks low risk, but also low impact (how important is it to have
the correct model name output in lscpu?) in a core package installed on
all users' systems. I'm fine with the idea of such a change being
included in an SRU, but I think we wouldn't normally push an SRU *just*
for a change such
Uploaded to Lunar and Jammy, but not Kinetic (Won't Fix).
$ ubuntu-distro-info --series=kinetic --days=eol
45
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
This bug was fixed in the package util-linux - 2.38.1-5ubuntu2
---
util-linux (2.38.1-5ubuntu2) mantic; urgency=medium
* d/p/ubuntu/lp-2019856-add-missing-arm-cores.patch:
Add missing ARM cores for NVIDIA Grace (LP: #2019856)
-- Mauricio Faria de Oliveira Tue, 23 May 2023
Uploaded for Mantic, thanks!
** Changed in: util-linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2019856
** Changed in: util-linux (Ubuntu Mantic)
Assignee: Mauricio Faria de Oliveira (mfo) => Dan Bungert (dbungert)
** Changed in: util-linux (Ubuntu Mantic)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
The attachment "lp-2019856-add-missing-arm-cores-jammy.debdiff" seems to
be a debdiff. The ubuntu-sponsors team has been subscribed to the bug
report so that they can review and hopefully sponsor the debdiff. If
the attachment isn't a patch, please remove the "patch" flag from the
attachment,
util-linux 2.38.1-5ubuntu1 finally migrated from mantic-proposed to mantic
(its autopkgtests were very slow/cycling last week, apparently).
I'll check for potential sponsors to the debdiff in comment #10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
For Mantic, this indeed requires a patch, not a merge/sync, as Debian
doesn't have the commit yet either.
$ git remote get-url origin
git://git.kernel.org/pub/scm/utils/util-linux/util-linux.git
$ git describe --contains 6857cccbb4157d5da34ca98f77a0ac9d68e1e740
v2.39-rc1~126^2~4
$ git show
Debdiff on top of mantic-proposed (2.38.1-5ubuntu1), which should
migrate soon (all good on update-excuses [1] / pending autopkgtests).
https://people.canonical.com/~ubuntu-archive/proposed-
migration/update_excuses.html#util-linux
** Patch added: "lp2019856-mantic-util-linux.debdiff"
Test packages in ppa:mfo/lp2019856, verified with GDB
(to fake CPU IDs) on Google Cloud ARM-based instances.
No differences in `lscpu` output for non-affected CPU.
Expected output for both affected CPUs (0xd15, 0xd4f).
Tested on LXD containers for Mantic, Lunar, and Jammy
(not on Kinetic as it
Hey Heather, thanks for the updated debdiffs!
I've looked at them, and did minor fixes to DEP3
(moved them out of the original commit message,
after `---`, and added Origin: fields), and just
a cosmetic adjustment to the changelog.
It turns out this patch isn't present in Mantic.
I already
** Description changed:
[Impact]
- When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't
report a model name:
+
+ When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't
+ report a model name:
Vendor ID: ARM
Model: 0
[Fix]
- Adding the additional
** Also affects: util-linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: util-linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: util-linux (Ubuntu Kinetic)
Status: New => Won't Fix
** Changed in: util-linux (Ubuntu Mantic)
v2 fixed lunar header patch
** Patch added: "lp-2019856-lunar-v2-fix-missing-arm-core-support.debdiff"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+attachment/5674703/+files/lp-2019856-lunar-v2-fix-missing-arm-core-support.debdiff
** Tags added:
fixed header for patch
** Patch added: "lp-2019856v3-jammy-add-arm-core-support.debdiff"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+attachment/5674198/+files/lp-2019856v3-jammy-add-arm-core-support.debdiff
--
You received this bug notification because you are a
Heather mentioned some changes she has for the debdiffs, I also noted
some changes to DEP3 headers, and debdiffs v2 are in progress. Thanks,
Heather!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
The attachment "lp-2019856-add-missing-arm-cores-jammy.debdiff" seems to
be a debdiff. The ubuntu-sponsors team has been subscribed to the bug
report so that they can review and hopefully sponsor the debdiff. If
the attachment isn't a patch, please remove the "patch" flag from the
attachment,
adds lunar debdiff
** Patch added: "lp-2019856-add-arm-core-lunar.debdiff"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+attachment/5673899/+files/lp-2019856-add-arm-core-lunar.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Tags added: se-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2019856
Title:
Add missing ARM-cores to support Grace-based systems
Status in util-linux
adds jammy debdiff
** Patch added: "lp-2019856-add-missing-arm-cores-jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+attachment/5673887/+files/lp-2019856-add-missing-arm-cores-jammy.debdiff
** Changed in: util-linux (Ubuntu Jammy)
Status: New => In
creating testing ppa https://launchpad.net/~hypothetical-
lemon/+archive/ubuntu/lp2019856-util-linux
** Changed in: util-linux (Ubuntu Jammy)
Assignee: (unassigned) => Heather Lemon (hypothetical-lemon)
** Changed in: util-linux (Ubuntu Lunar)
Assignee: (unassigned) => Heather Lemon
** Also affects: util-linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: util-linux (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
35 matches
Mail list logo
