Hi xypron,
thanks for your suggestion. I have this already staged and tested with
other fixes for zfs-linux on Focal, so there's little effort involved in
it.
On a more broader scope, the patch enabling this only toggles build
flags and has no changes to the ZFS source (module and user space).
Thank you for taking the time to fix this one, Tom!
The debdiff you submitted is quite big. If I'm understanding correctly, your
intention was to submit a new upstream microrelease into the Ubuntu repos.
While the SRU policy does foresee the case of a bugfix-only microrelease, I'm
not fully
** Changed in: 389-ds-base (Ubuntu)
Status: New => Fix Released
** Changed in: 389-ds-base (Ubuntu Jammy)
Status: New => In Progress
** Changed in: 389-ds-base (Ubuntu Jammy)
Assignee: (unassigned) => Tom Moyer (tom-tom)
** Changed in: 389-ds-base (Ubuntu)
Assignee: Tom
VMcore extraction tool
** Affects: makedumpfile (Ubuntu)
Importance: Medium
Assignee: Heitor Alves de Siqueira (halves)
Status: In Progress
** Changed in: makedumpfile (Ubuntu)
Status: Confirmed => In Progress
** Changed in: makedumpfile (Ubuntu)
Importa
Thanks, gpiccoli!
This is fixed in kdump-tools 1.10, so I'm marking it as Fix Released
(Noble and Oracular already ship with version 1.10.3ubuntu2). I'm also
marking makedumpfile as Invalid, since kdump-tools was split from that
source package.
** Changed in: makedumpfile (Ubuntu)
Status:
Thanks for the confirmation on Focal, @pponnuvel!
I've tested your debdiff, and it seems to work correctly. Patch is also
a straightforward cherry-pick from Debian.
Sponsored for Jammy, with the update-maintainer changes.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: nagios4 (Ubuntu Noble)
Status: Incomplete => In Progress
** Changed in: nagios4 (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: In Progress => 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/1919154
Title:
Enable CONFIG_NO_HZ_FULL on supported architectures
To manage
Marking as verified according to comment #21
** Tags removed: verification-needed verification-needed-mantic
** Tags added: verification-done verification-done-mantic
** Changed in: software-properties (Ubuntu)
Status: Confirmed => Invalid
** Changed in: software-properties (Ubuntu
Bionic is EoL, if RISC-V support is needed there we'll need to target
Pro 18.04.
** Tags removed: patch se-sponsor-halves
** Description changed:
- Building zfs-linux for riscv64 fails on Ubuntu 18.04. There is a single
- patch missing:
-
** Changed in: zfs-linux (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/1987052
Title:
Running MySQL8 in Docker on ZFS only works if you have ZFS 2.1.5.
signee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided =&g
Thanks for the debdiff, Jorge! A few comments:
Even though the fix is the same for J/M/N, we'll need separate debdiffs and
versions for each. We'll need to keep the upgrade path working between each
release, so I'd suggest something like below (according to [0]):
- 4.4.6-4ubuntu0.22.04.1 for
Hi Pon,
thanks for the revised debdiff! This seems to be a non-quilt package, so
your approach of directly patching the ucf/ucfr scripts is correct. The
only thing missing is running the update-maintainer script, as the
ubuntu1 version requires having an ubuntu.com address on the maintainers
Marking Ubuntu as "Fix Released" according to parent description, as fix
was introduced upstream in v5.16.
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed => In Progress
--
You received this bug
** Changed in: linux (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/2061986
Title:
Mount CIFS fails with Permission denied
To manage notifications about
** Changed in: ubuntu-pro/18.04
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2038453
Title:
[SRU] apt snapshot integration backport
To manage notifications
# VERIFICATION FOCAL
Validation performed on a 6-core VM with 8Gb or RAM. The following stress-ng
command was running throughout the test from the description:
# stress-ng --class memory --class vm --all 1 --timeout 96h
Afterwards, the udevadm test loop was executed as below:
# date; while
Thanks, Robie! Our users reported that issues usually appear within one
or two hours, but that's likely tied to machine-specific workloads.
I've been able to force this issue to occur in a VM when running the
test script from the description together with stress-ng memory/vm
stressors. The
Thanks for the revised debdiff, Matthew! And nice work on the extensive
sanity check for the version laddering.
The new debdiff looks good, I've sponsored it for Focal. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Matthew,
thanks for the quick follow-up on the regression! Being the sponsor for
the original patch in bug 2049262, I wanted to give this one some deeper
attention. Version parsing seems to have been a difficult area upstream,
with several follow-up fixes indeed, so thank you for detailing the
** Changed in: zfs-linux (Ubuntu Focal)
Importance: Medium => Low
** Changed in: zfs-linux (Ubuntu Focal)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: zfs-linux (Ubuntu Focal)
Status: Incomplete => In Progress
--
You received this bug not
** Changed in: timeshift (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: timeshift (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: timeshift (Ubuntu Jammy)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member
We've had users report this bug under Focal, and the usbguard pkg there
does seem to be missing this fix. I've updated the bug with the SRU
template, and tested the patches (builds available at [0]). Users also
reported that this patched version resolved this issue, so I've pushed
it to the Focal
** Description changed:
- With 0.7.4+ds-1 from 19.10, usbguard may stop responding to events when
- recvmsg fails with ENOBUFS. To reproduce:
+ [Impact]
+ usbguard-daemon will no longer process device events until restarted
+
+ [Test Plan]
+ 1. Spin up a Focal VM with usbguard enabled
+ 2. Run
signee: (unassigned) => Heitor Alves de Siqueira (halves)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855189
Title:
usbguard stops responding when recvmsg receives ENOBUFS
To manage notifications about
Hi Ghadi,
thanks for the debdiff! I've considered trimming down the new version to
0.2.8+bzr63-0ubuntu1.1 according to [0], but ultimately think your
approach is correct (otherwise it'll be hard to update ppa-purge in
Jammy if we ever need to!).
Tested and sponsored for Mantic.
[0]
*** This bug is a duplicate of bug 1855189 ***
https://bugs.launchpad.net/bugs/1855189
This seems to be a duplicate of bug 1855189. Feel free to drop a comment
if this isn't the case, and we can investigate further. Thanks!
** This bug has been marked a duplicate of bug 1855189
usbguard
Thank you for the bug, Heather! I'm marking Bionic as "Won't Fix", as it's EOL.
If needed, please re-target against Pro 18.04. Thanks!
** Changed in: systemd (Ubuntu Bionic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Uploaded to the stable series. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968805
Title:
Hibernation fails when an additional swapfile is added due to priority
mismatch
To manage
** Tags removed: sts-sponsor
** Tags added: sts-sponsor-halves
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968805
Title:
Hibernation fails when an additional swapfile is added due to priority
** Tags added: sts sts-sponsor-halves
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972029
Title:
dhclient overriding stub-resolv.conf file on Jammy
To manage notifications about this bug go to:
Uploaded to stable releases, thanks!
I had to adjust some minor things (package versions) due to the new kinetic
upload, but the patches themselves were good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Validated glibc from focal-proposed according to test case from
description:
halves@glibc-zen:~$ ./test_memcpy64 32
32 MB = 1.222535 ms
-Compare match (should be zero): 0
halves@glibc-zen:~$ dpkg -l | grep libc-bin
ii libc-bin 2.31-0ubuntu9.9amd64
Sponsored for Bionic. Thanks for the contribution, @jorge-merlino!
** Changed in: open-iscsi (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872813
** Description changed:
[Impact]
* Specific NVMe devices fail to probe and become unusable after boot
* Caused by an ACPI regression that doesn't correctly handle power states
* Upstream regression commit:
7e4fdeafa61f ACPI: power: Turn off unused power resources unconditionally
*
** Summary changed:
- NVME "can't change power state from D3Cold to D0 (config space inaccessible)"
+ NVMe devices fail to probe due to ACPI power state change
** Description changed:
+ [Impact]
+ * Specific NVMe devices fail to probe and become unusable after boot
+ * Caused by an ACPI
In addition to my own validations above, impacted users that have 40G
NICs have also confirmed the patch behaves as expected without major
regressions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Validated for Ubuntu Impish with the current kernel from impish-proposed.
Tested on a 10G NIC that's affected by this patch (device ID 0x0903). iperf3
shows that we're able to almost saturate the NIC successfully in both standard
and reverse sender mode:
[ ID] Interval Transfer
Validated for Ubuntu Bionic with the current HWE kernel from bionic-proposed.
Tested on a 10G NIC that's affected by this patch (device ID 0x0903). iperf3
shows that we're able to almost saturate the NIC successfully in both standard
and reverse sender mode:
[ ID] Interval Transfer
Validated for Ubuntu Focal with the current kernel from focal-proposed.
Tested on a 10G NIC that's affected by this patch (device ID 0x0903). iperf3
shows that we're able to almost saturate the NIC successfully in both standard
and reverse sender mode:
[ ID] Interval Transfer
** Tags added: sts-sponsor-halves
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872813
Title:
cloud-init fails to detect iSCSI root on focal Oracle instances
To manage notifications about this
** Tags removed: sts-sponsor
** Tags added: sts-sponsor-halves
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965325
Title:
upstream patch from opendev - double encoding-decoding
To manage
Hi all,
This seems to be related to a regression introduced by the following commit:
* 7e4fdeafa61f ACPI: power: Turn off unused power resources unconditionally
The fix seems to indeed be the commit @sclarkson mentioned:
* bc2836859643 ACPI: PM: Do not turn off power resources in unknown state
** Changed in: linux (Ubuntu Impish)
Status: Confirmed => In Progress
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: linux-oem-5.14 (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are
buntu Impish)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status:
** Patch added: "lp1964992-focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964992/+attachment/5571326/+files/lp1964992-focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This doesn't seem to be reproducible in Bionic, marking it as fixed
accordingly.
** Changed in: zfs-linux (Ubuntu Bionic)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Fix Released
** Affects: zfs-linux (Ubuntu Bionic)
Importance: Medium
Assignee: Heitor Alves de Siqueira (halves)
Status: Confirmed
** Affects: zfs-linux (Ubuntu Focal)
Importance: Medium
Assignee: Heitor Alves de Siqueira (halves)
Status: Confirmed
**
** Changed in: linux (Ubuntu Impish)
Importance: Undecided => High
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux (Ubuntu Impish)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: linux (Ubuntu Focal)
s possible to see increased calls to alloc_pages if ring sizes
aren't being set correctly
* We should look out for excessive memory usage in the sfc driver due to
the increased ring sizes
** Affects: linux (Ubuntu)
Importance: High
Assignee: Heitor Alves de Siqueira (halves)
s could have existing automation in place to
+ correct the issue manually. We'd expect the fix to have little impact on
+ such scenarios, and the patches have been tested for these cases.
** Changed in: command-not-found (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: comman
** Tags added: sts
** Changed in: command-not-found (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: command-not-found (Ubuntu Impish)
Importance: Undecided => Medium
** Changed in: command-not-found (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this
Validated according to test case from description:
root@bionic-ssh:~# python3 test_bug_1863930.py localhost
Server is patched
root@bionic-ssh:~# dpkg -l | grep openssh
ii openssh-client 1:7.6p1-4ubuntu0.6 amd64
secure shell (SSH) client, for secure
** Tags removed: sts-sponsor
** Tags added: sts-sponsor-halves
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953610
Title:
cnf-update-db creates unreadable database if wrong umask
To manage
** Changed in: openssh (Ubuntu Bionic)
Status: Incomplete => In Progress
** Tags added: sts sts-sponsor-halves
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863930
Title:
SSH 1.99 clients
** Changed in: openssh (Ubuntu Bionic)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: openssh (Ubuntu Bionic)
Importance: Low => High
** Changed in: openssh (Ubuntu Bionic)
Importance: High => Medium
--
You received this bug notification be
@dgatwood would you be able to upload kernel logs and lsusb output from
the -44 kernel? From what you're describing it seems like a possible
issue with host controllers, but it's hard to tell without looking at
what is going in the kernel.
You can use `apport-collect 1956849` to upload relevant
@joalif thank you for the debdiff! There are some minor nitpicks about
the patch file that I'd like to confirm with you:
- The 'Origin:' tag in your patch file seems to be missing the patch
identifier. From the commit id, would it be appropriate to point it towards [0]?
- I've seen you added a
** Tags added: sts-sponsor-halves
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955129
Title:
trace-cmd report buffer overflow detected
To manage notifications about this bug go to:
Validated glibc from -proposed according to test case from description:
halves@focal-proposed:~$ grep -m1 "model name" /proc/cpuinfo
model name : AMD Ryzen 7 3700X 8-Core Processor
halves@focal-proposed:~$ ./test_memcpy64 32
32 MB = 1.340379 ms
-Compare match (should be zero): 0
Validated package from -proposed according to test case from
description. Tab completion works correctly, and the bash completion
script is found under the correct location:
$ dpkg -l | grep nvme-cli
ii nvme-cli 1.5-1ubuntu1.2 amd64
userspace
It's been some time since the original benchmarks, so I'm repeating the
test from the description. I haven't used hyperfine for the comparisons
below, so they won't have the same statistical reliability but should
nevertheless be sufficient for validation.
Binaries have been compiled as below:
$
** Tags removed: sts-sponsor-volunteer
** Tags added: sts-sponsor-halves
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800544
Title:
nvme-cli drops bash completion file in wrong location
To
** Changed in: nvme-cli (Ubuntu Bionic)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: nvme-cli (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verified for Focal according to test case from description. A standard
multipass VM with 8 vCPUs configured was able to capture a kernel dump
without errors.
Additionally, since the 5.4 kernel doesn't hit the MMU/reset bug
directly, I've done some additional testing to ensure we didn't
introduce
For future reference, this bug has been reported in Ubuntu KVM hosts
outside of the specific kdump test scenario (i.e. when running actual
VMs in production-like setups). The "kdump with multiple CPUs" case was
discovered as an alternative that hits the same MMU context bug, without
needing
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1948862
Title:
lso affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) =&g
** Description changed:
[Impact]
When kexec'ing into a crash kernel with ncpus > 1, VMs can raise a KVM
emulation failure. This will cause the VM to go into the "paused" state, and
prevents it from being restored without a full VM restart.
This happens only when there are multiple
** Description changed:
[Impact]
- When kexec'ing into a crash kernel with `ncpus` > 1, VMs can raise a KVM
- emulation failure. This will cause the VM to go into the "paused" state, and
- prevents it from being restored without a full VM restart.
+ When kexec'ing into a crash kernel with ncpus
~119
v5.15-rc1~65^2~120
** Affects: linux (Ubuntu)
Importance: High
Assignee: Heitor Alves de Siqueira (halves)
Status: New
** Tags: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Validated with ZFS from focal-proposed, according to test case from description:
ubuntu@z-rotomvm34:~$ dpkg -l | grep zfsutils
ii zfsutils-linux 0.8.3-1ubuntu12.12
amd64command-line tools to manage OpenZFS filesystems
ubuntu@z-rotomvm34:~$ zfs
Verified Hirsute according to test case from description:
root@h-sos:~# dpkg -l | grep sos
ii sosreport 4.1-1ubuntu1.2
amd64Set of tools to gather troubleshooting
data from a system
root@h-sos:~# lsmod | grep
Verified Focal according to test case from description:
root@f-sos:~# dpkg -l | grep sosreport
ii sosreport 4.1-1ubuntu0.20.04.3 amd64
Set of tools to gather troubleshooting data from a system
root@f-sos:~# lsmod | grep -i devlink
root@f-sos:~# sos
Verified Bionic according to test case from description:
root@b-sos:~# dpkg -l | grep sosreport
ii sosreport4.1-1ubuntu0.18.04.3
amd64Set of tools to gather troubleshooting data from a system
root@b-sos:~# lsmod | grep -i devlink
** Description changed:
[Impact]
Encrypted swap partitions may not load correctly with ZFS root, due to
ordering cycle on zfs-mount.service.
[Test Plan]
1. Install Ubuntu 20.04 using ZFS-on-root
2. Add encrypted partition to /etc/crypttab:
-swap/dev/nvme0n1p1 /dev/urandom
** Patch added: "lp1923661-h.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/sosreport/+bug/1923661/+attachment/5510566/+files/lp1923661-h.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1923661-g.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/sosreport/+bug/1923661/+attachment/5510565/+files/lp1923661-g.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1923661-f.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/sosreport/+bug/1923661/+attachment/5510564/+files/lp1923661-f.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1923661-b.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/sosreport/+bug/1923661/+attachment/5510563/+files/lp1923661-b.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+ Encrypted swap partitions may not load correctly with ZFS root, due to
ordering cycle on zfs-mount.service.
+
+ [Test Plan]
+ 1. Install Ubuntu 20.04 using ZFS-on-root
+ 2. Add encrypted partition to /etc/crypttab:
+swap/dev/nvme0n1p1 /dev/urandom
** Changed in: zfs-linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: zfs-linux (Ubuntu Focal)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We've determined this to be due to using disks with mixed sector sizes
(i.e. different physical and logical sector sizes). The mentioned patch
[0] enables lvmlockd to create shared leases in mixed sector sized
disks, but additional support is needed in sanlock for these to work
correctly.
The
Since we don't have a reliable test procedure for triggering the KVM
emulation failures, I did basic smoke tests on VMs using seabios from
mitaka-proposed. Things look good, and general NMI functionality seems
to be working correctly.
I've also confirmed with affected users that this version has
There's currently a pending SRU for glibc on Groovy, which I based my
debdiff on. Although that SRU has already cleared the 7 day grace
period, there are still a few pending bugs for verification which we
would need to clear before being able to upload a fix for this one.
Since Groovy is going
** Description changed:
[Impact]
sos's networking plugin may trigger the devlink kernel module to load.
We don't want sos to modify/change/alter the state of a machine
whatsoever, especially during troubleshooting. But it may be the case
for the networking plugin, depending on the
** Description changed:
[Impact]
On AMD Zen systems, memcpy() calls see a heavy performance regression in
Focal and Groovy, due to the way __x86_non_temporal_threshold is calculated.
Before 'glibc-2.33~455', cache values were calculated taking into
consideration the number of hardware
** Changed in: sosreport (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: sosreport (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: sosreport (Ubuntu Hirsute)
Importance: Undecided => Medium
** Changed in: sosreport (Ubuntu Focal)
Importance: Undecided
** Changed in: sosreport (Ubuntu Bionic)
Assignee: Eric Desrochers (slashd) => Heitor Alves de Siqueira (halves)
** Changed in: sosreport (Ubuntu Focal)
Assignee: Eric Desrochers (slashd) => Heitor Alves de Siqueira (halves)
** Changed in: sosreport (Ubuntu Groovy)
Assignee
** Patch added: "lp1928508-groovy-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1928508/+attachment/5503158/+files/lp1928508-groovy-v2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch removed: "lp1928508-focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1928508/+attachment/5502960/+files/lp1928508-focal.debdiff
** Patch removed: "lp1928508-groovy.debdiff"
** Patch added: "lp1928508-groovy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1928508/+attachment/5502961/+files/lp1928508-groovy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "lp1928508-focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1928508/+attachment/5502960/+files/lp1928508-focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've ran the same test on an Intel system, to ensure we aren't
introducing any regressions there. Besides basic smoke tests, the
benchmarks from the description showed that the performance on Intel is
not significantly affected by this patch.
halves@rotom:~$ head -n5 /proc/cpuinfo
processor
Below is the same benchmark from the case description, validating the
performance regression on Groovy. Patched glibc builds for both Focal
and Groovy amd64/i386 are available at ppa:halves/lp1928508-test [0].
$ hyperfine -n groovy-2.32-0ubuntu3 'lxc exec groovy ./test_memcpy64 32' -n
** Changed in: lvm2 (Ubuntu)
Assignee: (unassigned) => Heitor Alves de Siqueira (halves)
** Changed in: lvm2 (Ubuntu)
Importance: Undecided => High
** Changed in: lvm2 (Ubuntu)
Status: New => Fix Released
** Also affects: lvm2 (Ubuntu Focal)
Importance: Undecided
** Description changed:
[Impact]
On AMD Zen systems, memcpy() calls see a heavy performance regression in
Focal and Groovy, due to the way __x86_non_temporal_threshold is calculated.
- Before 'glibc-2.33~455', cache values were calculated taking into
consideration the number of hardware
** Attachment added: "test_memcpy.c"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1928508/+attachment/5497631/+files/test_memcpy.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928508
| source
Affected releases include Ubuntu Focal and Groovy. Bionic is not
affected, and releases starting with Hirsute already ship the upstream
patch to fix this regression.
** Affects: glibc (Ubuntu)
Importance: High
Assignee: Heitor Alves de Siqueira (halves)
Status: Fix Release
1 - 100 of 259 matches
Mail list logo
