On Mon, Apr 22, 2024 at 11:07:54AM -, Matthieu Baerts wrote:
> > I don't think we can justify dropping FAN support in an SRU, so let's
> add that port back in.
>
> Even if it will not be used in Ubuntu 24.04,
I'm happy to drop it if the stable release team would accept it.
Here's the
Thank Utkarsh. Yeah, we just dropped the ball on not getting this done
sooner. I'd like to see if we can make the case for SRU'ing 6.8 in, so
let's convert the bug to that.
I don't think we can justify dropping FAN support in an SRU, so let's
add that port back in.
We'll need to make a
*** This bug is a duplicate of bug 2051672 ***
https://bugs.launchpad.net/bugs/2051672
Amir - we're working on this in bug 2051672, and I subscribed you to it.
I have prepared a build of iproute2 6.8 for noble in a PPA:
https://launchpad.net/~dannf/+archive/ubuntu/test
If there is some
** Description changed:
- Both jammy's previous 4.17.0+1-1build2 and noble's recent 4.26.0+1-2
- include it, and 4.21.0-7 itself continues to ship its manpage.
+ [Impact]
+ The mstlink and mstreg binaries have regressed in the last jammy update. This
is because a new upstream landed in jammy as
** Description changed:
[Impact]
A bug in the kernel module source can cause error messages to show up in the
kernel when an application closes the device when UBSAN is active.
+
+ From an NVIDIA DGX 1 system:
+ $ sudo mstflint -d 84:00.0 q
+ $ dmesg
+ [ 304.400217]
** Description changed:
iproute2 upstream produces releases coinciding with upstream kernel
releases to support the latest kernel features. Noble's iproute2 is
still back at v6.1 even though it will use the v6.8 kernel. This means
we provide no userspace interface for newer features -
ng correct - updating comments only.
** Affects: mstflint (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: mstflint (Ubuntu Jammy)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: mstflint (Ubuntu Mantic)
Could Go Wrong]
A severe bug in the fix could cause the problem to escalate to an oops or panic.
** Affects: mstflint (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: mstflint (Ubuntu Jammy)
Importance: Undecided
Assignee: dann frazier (dannf)
Status
** Also affects: mstflint (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: mstflint (Ubuntu Mantic)
Status: New => In Progress
** Changed in: mstflint (Ubuntu Mantic)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notifi
: New => In Progress
** Changed in: mstflint (Ubuntu Mantic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: mstflint (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Public bug reported:
[Impact]
Users upgrading from jammy to mantic will not have an mstflint-dkms package.
This will leave the mstflint-dkms package from jammy installed, which is
incompatible with the 6.5 kernel.
The reason we ended up here was due to a bypass of the SRU process, described
I found that the mstflint command has dropped some command line
parameters in 4.26.0 (--private-key-label, --public-key-label, --hsm),
so that has more regression potential. For now, I'm moving to Won't Fix.
** Changed in: mstflint (Ubuntu Jammy)
Status: In Progress => Won't Fix
**
** Description changed:
- A few versions have been released and Ubuntu Noble still has the 6.1
- version (6.1.0-1ubuntu2) from one year ago. Could it be possible to
- import the latest version from Debian unstable fixing a bunch of issues
- and supporting features from more recent kernels?
+
Thanks Matthieu. I spoke to the kernel team and I think they will handle
the update. I'm just trying to help unblock them by getting this
reviewed/agreed by our release team ahead of time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "Upstream 6.7 changelog"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763789/+files/6.7-changes.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Upstream 6.8 changelog"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763790/+files/6.8-changes.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Upstream 6.4 changelog"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763786/+files/6.4-changes.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Upstream 6.6 changelog"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763788/+files/6.6-changes.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Upstream 6.5 changelog"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763787/+files/6.5-changes.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Upstream 6.3 changelog"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763785/+files/6.3-changes.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It seems like this bug should now be a FFe (see
https://wiki.ubuntu.com/FreezeExceptionProcess) - so converting...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051672
Title:
[FFe] Merge iproute2
** Attachment added: "Upstream 6.2 changelog"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763784/+files/6.2-changes.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable
(main)
+ [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
testing/unstable (main)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 2051672 ***
https://bugs.launchpad.net/bugs/2051672
** This bug has been marked a duplicate of bug 2051672
Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable
(main)
--
You received this bug notification because you are a
** Changed in: linux (Ubuntu)
Assignee: Jose Ogando Justo (joseogando) => Mitchell Augustin
(mitchellaugustin)
** Changed in: linux (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
to the new version.
[ ] Mellanox has executed their mstflint test plan, and results are uploaded to
this bug for each series.
** Affects: mstflint (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: mstflint (Ubuntu Jammy)
Importance: Undecided
Assignee: dann frazier
** Changed in: mstflint (Ubuntu Jammy)
Status: New => In Progress
** Changed in: mstflint (Ubuntu Jammy)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mstflint (Ubuntu Jammy)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2043098
Title:
mstflint-dkms FTBS with linux 6.5 on ja
I've build-tested on all architectures in this PPA:
https://launchpad.net/~dannf/+archive/ubuntu/mthp/+packages
I manually tested on a few systems, timing a full kernel build w/ the
Ubuntu config in a tmpfs (both to stress the system, and look for
performance differences).
- ppc64el / Power9 -
** Changed in: linux (Ubuntu)
Status: New => 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/2059316
Title:
backport arm64 THP improvements from 6.9
To manage notifications about
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059316
Title:
backport arm64 THP improvements from 6.9
To man
Public bug reported:
Initial support for multi-size THP landed upstream in v6.8. In the 6.9
merge window, 2 other series have landed that show significant
performance improvements on arm64
mm/memory: optimize fork() with PTE-mapped THP
= Verification =
$ cat /proc/version
Linux version 6.5.0-27-generic (buildd@lcy02-amd64-059)
(x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0, GNU ld (GNU Binutils
for Ubuntu) 2.41) #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024
** Changed in: shim-signed (Ubuntu Cosmic)
Status: Triaged => Won't Fix
** Changed in: shim-signed (Ubuntu Bionic)
Status: Triaged => Fix Released
** Changed in: linux-signed (Ubuntu Cosmic)
Status: Triaged => Won't Fix
** Changed in: linux-meta (Ubuntu Cosmic)
I've add mstflint-dkms to mstflint/noble:
https://launchpad.net/ubuntu/+source/mstflint/4.26.0+1-2ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051571
Title:
jammy: 4.21.0-7 dropped
: Undecided
Status: Won't Fix
** Affects: linux (Ubuntu Mantic)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Wo
** Changed in: edk2 (Ubuntu)
Status: Triaged => In Progress
** Changed in: edk2 (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Yeah, I don't think an autopkgtest is a requirement. Having the test
live within the package itself would make it more accessible, and
autopkgtest was my first thought as to how to do that. But I don't see a
"disable by default" flag, and I agree that huge downloads on every test
run could be a
Patches are now queued for all applicable stable trees (linux-4.14.y+)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973153
Title:
kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15
Thanks everyone for trying to tackle this long-standing issue. fwiw,
here's my $0.02 no how we could proceed:
Someone should draft a special case page for makedumpfile:
https://wiki.ubuntu.com/StableReleaseUpdates#Documentation_for_Special_Cases
I'm happy to review/provide feedback, but I'd
A fix for this is currently queued in linux-next:
commit 1bbc21785b7336619fb6a67f1fff5afdaf229acc
Author: Lorenzo Pieralisi
Date: Thu Apr 7 11:51:20 2022 +0100
ACPI: sysfs: Fix BERT error region memory mapping
My plan is to propose this for stable after it lands during the merge
window.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
= bionic verification =
ubuntu@d06-4:~$ cat /proc/version
Linux version 4.15.0-179-generic (buildd@bos02-arm64-025) (gcc version 7.5.0
(Ubuntu/Linaro 7.5.0-3ubuntu1~18.04)) #188-Ubuntu SMP Tue May 10 20:51:17 UTC
2022
ubuntu@d06-4:~$ grep domain2 /proc/schedstat | wc -l
128
ubuntu@d06-4:~$ grep
@kernel when we've already tested a kernel in its GA release, do we also
now need to retest the HWE backport?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966194
Title:
[Jammy, mlx5, ConnectX-7]
** Description changed:
[Impact]
The LTP cpuset_sched_domains test, authored by Miao Xie, fails on a Kunpeng920
server that has 4 NUMA nodes:
- https://launchpad.net/bugs/1951289
+ https://launchpad.net/bugs/1951289
This does appear to be a real bug. /proc/schedstat displays 4
It's not a question of if it *could* be backported - it's a question of
whether or not we can demonstrate that such a backport has a negligible
risk of regression to existing 20.04 users. See
https://wiki.ubuntu.com/StableReleaseUpdates for details.
--
You received this bug notification because
** Description changed:
[Impact]
- We have Hisilicon PMU modules built-in and they can not be unloaded. There is
no way to replace with a updated module unless we build it as module.
+ We have Hisilicon PMU modules built-in and they can not be unloaded. There is
no way to replace with a
** Description changed:
- On scobee-kernel(arm64) with hirsute:linux(5.11.0-41.45) for
- sru-20211108 there are several reports about the sched domain not
- covering the full range. The same does not happen on kuzzle. But 32 is a
- bit of a suspicious number.
+ [Impact]
+ The LTP
** Changed in: kunpeng920/ubuntu-20.04
Status: In Progress => Fix Committed
** Changed in: kunpeng920/ubuntu-18.04-hwe
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
5.4.183 has now been merged into focal
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951289
Title:
We decided the best approach was to revert the break patch which is now
done in 5.15.y upstream:
commit f1607e13ed715f3b6433361f8ea5d4aa79f03b94
Author: dann frazier
Date: Thu Apr 7 14:16:42 2022 -0600
Revert "net/mlx5: Accept devlink user input after driver
initialization com
On Wed, Apr 27, 2022 at 2:25 PM Jeff Lane <1946...@bugs.launchpad.net> wrote:
> Given that, I'm now curious about how this was set up on the Ampere
> server too, and if anyone tried what I did by putting Desktop on a local
> machine and mounting the ISO from there, rather than from a remote
>
2.31-0ubuntu9.7 vs 2.31-0ubuntu9.9
= X-Gene =
length | before (MiB/s) | after (MiB/s) |delta
--|||--
32768 | 122.27 | 122.26 | -0.00%
65536 | 216.55 | 215.81 | -0.34%
131072 | 321.97 |
Released upstream in 5.4.183. The inclusion of the changes from that
stable release is being tracked in bug 1969239.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951289
Title:
> Point is, I don't think the issue you're seeing is actually related to
this bug at this point.
The error appears to be the same in the screenshot @zhouling12 provided
- so it seems like we are still seeing this issue w/ high-latency media.
Or do you have reason to believe the cause is different
I wonder if there is some scope creep in this bug. The bug I filed has
this symptom:
-
Ubuntu 21.10 ubuntu-server ttyAMA0
connecting...
waiting for cloud-init...
An error occurred. Press enter to start a shell
Won't Fix
** Changed in: linux (Ubuntu Jammy)
Assignee: dann frazier (dannf) => (unassigned)
** Changed in: linux (Ubuntu Impish)
Assignee: dann frazier (dannf) => (unassigned)
** Changed in: linux (Ubuntu Hirsute)
Assignee: dann frazier (dannf) => (unassigned)
**
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952933
Title:
impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966194
Title:
[Jammy, mlx5, ConnectX-7] add CX7 support for software steering
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967754
Title:
ubuntu 22.04 jammy, mlx5, can't change flow steering mode
To
reported upstream: https://lists.gnu.org/archive/html/grub-
devel/2022-04/msg00055.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967562
Title:
jammy beta (220330) arm iso pxe boot kernel
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967562
Title:
jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt.
** Merge proposal linked:
https://code.launchpad.net/~xypron/grub/+git/grub/+merge/419407
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967562
Title:
jammy beta (220330) arm iso pxe boot kernel
Well spotted Heinrich. I'd hypothesized that something was shutting down
the network stack, but didn't yet no where to look, and overlooked
grub_net_fini_hw() message! With that hint, I went ahead and tried
commenting out[*] the registration of that callback, and voila, the
ReadFile2 initramfs
Any objection to dropping flash-kernel from ARM cloud images starting w/
jammy+1?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918427
Title:
curtin: install flash-kernel in arm64 UEFI unexpected
Thanks Amir. If the test results are the same w/ and w/o these patches,
then I assume those tests are regression tests. Are you able to also
confirm that the new functionality (CX7 software steering support) is
working as expected?
--
You received this bug notification because you are a member
(didn't check the code) that LoadFile2 initramfs is
disabled there.
** Changed in: grub2-unsigned (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: dann frazier (dannf) => (unassigned)
--
You received this bug notification because you are a member of
Removing efi-implement-grub_efi_run_image.patch didn't avoid the
problem, nor did removing both that and efi-implemented-
LoadFile2-initrd-loading-protocol-fo.patch, but that appears to just be
because the arm64 code gets migrated to the efi loader code later in the
series, basically reintroducing
I turned on grub debugging (set debug=all in grub.cfg), and this seems
interesting. The "error: couldn't send network packet." message may
actually be telling us something is wrong with downloading the initrd.
Full log attached, here's a filtered version:
[...]
loader/efi/linux.c:80: UEFI stub
GRUB is responsible for loading the initrd into memory, so it is possible that
this is a GRUB regression. Also, this message is new to me:
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
So maybe this is related to a new GRUB initrd loading method?
To test that, I grabbed
The iso-booted-kernel has no problem unpacking the initramfs:
[ 15.282839] Trying to unpack rootfs image as initramfs...
[...]
[ 15.935483] Freeing initrd memory: 103248K
But that's interesting, the freed initrd memory size reported is
different here. When PXE-booted, it was 103244K. 103248K
/+attachment/5578333/+files/howzit-pxe-console.log
** Changed in: subiquity (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Now fixed in upstream release v5.15.33.
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Just tested w/ a jammy image, and yeah - toram works, though it looks
like it took about 50 minutes from boot to load the ISO over this
interface.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946773
I've now updated the PPA w/ a kernel that reverts the patch that caused
bug 1967754. Same package name, just version 5.15.0-25.25.25+lp1966194.2
now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Impish)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19
I've refreshed the above ppa to include the guys for bug 1967754, can
you verify this build?
sudo apt-add-repository ppa:dannf/lp1966194
sudo apt install linux-modules-extra-5.15.0-25.25-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
@Amir: if that fixes the problem for you, would you mind submitting it
to sta...@vger.kernel.org? I've verified that stable 5.15.y is impacted,
which is where Ubuntu inherited it from. I also tested upstream 5.15.y
w/ cf530217408e applied, and it does seem to fix this issue.
** Changed in: linux
** Changed in: subiquity (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967562
Title:
jammy beta (220330) arm iso kernel panic during pxe boot
To manage
Yeah, it's not a MAAS deploy issue, but a subiquity PXE install issue
(MAAS deploys this system fine).
@Tai this bit looks weird to me:
[0.00] Kernel command line: BOOT_IMAGE=/casper/vmlinuz debug
root=/dev/ram0 ramdisk_size=150 ip=dhcp
** Bug watch added: github.com/mate-desktop/mate-terminal/issues #350
https://github.com/mate-desktop/mate-terminal/issues/350
** Also affects: mate-desktop via
https://github.com/mate-desktop/mate-terminal/issues/350
Importance: Unknown
Status: Unknown
--
You received this bug
Amir, I've prepared a test build with that additional commit added. Can
you run it through your test suite and report back? The kernel team will
take that testing into account to determine whether or not a kernel
feature freeze exception can be granted.
sudo apt-add-repository ppa:dannf/lp1966194
@Amir: After preparing a backport of these changes to jammy, I've a few
comments/questions:
I dropped the following patches because they are listed as dependencies, but I
didn't have any problem cherry-picking/building without them:
c228dce262225 net/mlx5: DR, Fix code indentation in dr_ste_v1
fyi, I do recall trying what I suggested in Comment #3, trying to debug
under GDB. However, I didn't find a way to trap writes to that region,
and didn't have any other good ideas.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
= impish verification =
Setting up systemtap-sdt-dev (4.4-2ubuntu0.1) ...
Processing triggers for man-db (2.9.4-2) ...
ubuntu@dannf-lp1962785-impish:~/foo$ make -j2
dtrace -o ../foo/foo.out -G -s /dev/null
dtrace -o foo.out -G -s /dev/null
= focal verification =
Setting up systemtap-sdt-dev
** Description changed:
[Impact]
dtrace generates .c code in a predictable temporary file which makes it
susceptible to crashes. I've seen this happen in practice when rebuilding
libvirt/focal on a system with 48 cores. The race window is wide enough that
the crash is nearly 100%
(Ubuntu Impish)
Status: New => In Progress
** Changed in: systemtap (Ubuntu Focal)
Status: New => In Progress
** Changed in: systemtap (Ubuntu Focal)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: systemtap (Ubuntu Impish)
Assignee: (unassigned
The fix is now in jammy-proposed, in the 5.15.0-23.23 kernel. @Amir mind
giving that a test and confirming that it works as you expect?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962185
Title:
ntu Focal)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: kunpeng920
Status: New => In Prog
** Changed in: rdma-core (Ubuntu Jammy)
Status: New => Fix Released
** Changed in: rdma-core (Ubuntu Impish)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: rdma-core (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Results for the 2.31-0ubuntu9.8~ppa3 build:
= X-Gene =
length | before (MiB/s) | after (MiB/s) |delta
--|||--
32768 | 122.23 | 122.24 |0.01%
65536 | 215.55 | 215.23 | -0.15%
131072 |
Results for the 2.31-0ubuntu9.8~ppa2 build:
= X-Gene =
length | before (MiB/s) | after (MiB/s) |delta
--|||--
32768 | 122.20 | 122.20 |0.00%
65536 | 215.42 | 213.49 | -0.89%
131072 |
= ThunderX2 =
length | before (MiB/s) | after (MiB/s) |delta
--|||--
32768 | 126.67 | 115.21 | -9.05%
65536 | 267.91 | 244.92 | -8.58%
131072 | 510.48 | 473.60 | -7.22%
Ah, thanks Frank - and I see the follow-up fix 7cf95304f8e9 as well.
Since 22.04 is nearing release, I think I'll upload the bare minimum
0de9020c970b, as it is sufficient to fix the problem we're seeing. Once
22.10 opens up for devel let's reconsider applying the others (or go
back to syncing
After some debugging, I realized the above is the same issue that this
commit fixed upstream:
commit 71e5f6644fb2f3304fcb310145ded234a37e7cc1
Author: Dietmar Eggemann
Date: Mon Feb 1 10:53:53 2021 +0100
sched/topology: Fix sched_domain_topology_level alloc in
sched_init_numa()
I've
** Changed in: linux (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux (Ubuntu Impish)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1963926
Title:
** Also affects: rdma-core (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: Invalid
** Also affects: rdma-core (Ubuntu Jammy)
Importance:
; urgency=medium
* d/p/Updated-initramfs-tools-to-work-on-18.04-and-20.04-a.patch:
Add retry support and compatibility with older cryptsetup versions.
-- dann frazier Mon, 13 Apr 2020 10:06:12 -0600
** Also affects: clevis (Ubuntu Focal)
Importance: Undecided
Status: New
** Bug watch added: Debian Bug tracker #1006703
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006703
** Also affects: systemtap (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006703
Importance: Unknown
Status: Unknown
--
You received this bug notification
1 - 100 of 3498 matches
Mail list logo
