This bug was fixed in the package edk2 - 2024.08-4
---
edk2 (2024.08-4) unstable; urgency=medium
* d/control, d/tests/control: Update relationships to use
qemu-system-riscv64 instead of qemu-system-misc. Thanks to
Michael Tokarev.
-- dann frazier Fri, 25 Oct 2024 11:46
** Changed in: edk2 (Ubuntu)
Status: New => 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.net/bugs/2
Unfortunately I've received no response from NVIDIA's networking team on
this matter. Since their validation was what I had planned to use to
verify this SRU, I suppose it is now time to mark this "Won't Fix". If
anyone wants to continue to push for this and has an alternate
validation plan, please
** Changed in: edk2 (Ubuntu)
Status: New => Fix Released
** Changed in: edk2 (Ubuntu Oracular)
Status: New => Fix Released
** Changed in: edk2 (Ubuntu Oracular)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: edk2 (Ubuntu)
Assignee: (unassigned
Yeah, I can confirm that this should just be sync'd.
** Summary changed:
- Merge edk2 from Debian unstable for plucky
+ Sync edk2 from Debian unstable for plucky
** Tags removed: needs-merge
** Tags added: needs-sync
--
You received this bug notification because you are a member of Ubuntu
Bugs
(1) thanks!
(1a) thanks!
(2) OK, should we split out a separate bug for that one then?
(3) I think the bigger issue is that the behavior of --gpgpu is undocumented:
https://github.com/canonical/ubuntu-drivers-common/pull/108
I feel --headless would be more self-explanatory, but I get that we nee
Public bug reported:
The intended behavior of `ubuntu-drivers` has always been mysterious to
me. Here are a few examples:
(1) It is not clear to me what --gpgpu is intended to do. The help
output simply says:
Options:
--gpgpu gpgpu drivers
According to https://ubuntu.com/server/d
** Changed in: dmidecode (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/2081611
Title:
Add processor support from SMBIOS 3.6.0 in Jammy and Noble
To manag
** Changed in: mstflint (Ubuntu)
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/2051571
Title:
jammy: 4.21.0-7 dropped mstlink binary
To manage notifications about this
Apologies for the delay - I took a few months off over the summer. I
agree that we should close this ticket if IPRoute2 is not to be
upgraded, but I do not see that this decision has been reached. It is
clear from #25 that we need to maintain `ubuntu-fan` support - so that
patchset would need to be
Quickly reproduces with:
stress-ng --aggressive --verify --timeout 7200 --metrics-brief --tz
--times --af-alg 0 --bsearch 0 --context 0 --cpu 0 --crypt 0 --hsearch 0
--longjmp 0 --lsearch 0 --matrix 0 --qsort 0 --str 0 --stream 0
--tsearch 0 --vecmath 0 --wcs 0
Using stress-ng 0.17.08-0~20240521
We're also seeing a similar crash w/ 5.15.0:
[24881.902027] [ cut here ]
[24881.902068] WARNING: CPU: 7 PID: 2196586 at crypto/algapi.c:472
crypto_unregister_alg+0xfc/0
x108
[24881.902119] Modules linked in: aes_ce_blk(+) chacha_generic chacha_neon
libchacha cfb xxhash
_g
Public bug reported:
Our ARM64 servers are tripping a BUG in the 5.4.0-182 kernel when
running cert regression testing:
bizzy login: [ 221.090860] kernel BUG at
/build/linux-hwe-5.4-OMohr6/linux-hwe-5.4-5.4.0/crypto/algapi.c:431!
[ 221.099468] Internal error: Oops - BUG: 0 [#1] SMP
[ 221.1042
I downloaded the deb from LP (that's why the verification starts w/ a
`dpkg -i`). Apologies that I did not call that out, I honestly thought I
had.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061182
ete => Fix Committed
** Changed in: iproute2 (Ubuntu Oracular)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: iproute2 (Ubuntu Oracular)
Milestone: ubuntu-24.04 => ubuntu-24.10-feature-freeze
** Changed in: iproute2 (Ubuntu Noble)
Status: New => Triaged
--
# Verification
## Installs cleanly in mantic and builds against the mantic kernel:
ubuntu@akis:~$ sudo dpkg -i *.deb
Selecting previously unselected package mstflint-dkms.
(Reading database ... 87552 files and directories currently installed.)
Preparing to unpack mstflint-dkms_4.26.0+1-1ubuntu0.1
# verification
ubuntu@hinyari:~$ ls -l /usr/bin/mstflint /usr/bin/mstreg
-rwxr-xr-x 1 root root 943848 Apr 12 20:33 /usr/bin/mstflint
-rwxr-xr-x 1 root root 447160 Apr 12 20:33 /usr/bin/mstreg
ubuntu@hinyari:~$ dpkg -l mstflint
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files
# jammy verification
ubuntu@hinyari:~$ uname -a
Linux hinyari 6.5.0-28-generic-64k #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri
Apr 5 16:55:05 UTC 2 aarch64 aarch64 aarch64 GNU/Linux
ubuntu@hinyari:~$ sudo dmesg -c > /dev/null
ubuntu@hinyari:~$ sudo mstflint -d 0006:01:00.0 q
Image type:
# mantic verification
ubuntu@akis:~$ uname -a
Linux akis 6.5.0-28-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 28 23:46:48
UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@akis:~$ sudo dmesg -c > /dev/null
ubuntu@akis:~$ sudo mstflint -d 35:00.0 q
Image type:FS4
FW Version:
# jammy verification
ubuntu@hinyari:~$ sudo apt install mstflint-dkms
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
libnuma1
Use 'sudo apt autoremove' to remove it.
The
# jammy verification
ubuntu@hinyari:/usr/src/mstflint-4.26.0+1-1ubuntu0.1~22.04.1$ head -32 *.c *.h
==> mst_main.c <==
/*
* Copyright (c) 2021 NVIDIA CORPORATION & AFFILIATES. ALL RIGHTS RESERVED.
*
* This software is available to you under a choice of one of two
* licenses. You may choose to
# mantic verification
Licenses are now consistent. SPDX-License-Identifier is gone, and the
boilerplate all says GPLv2 or OpenIB.org BSD:
ubuntu@akis:/usr/src/mstflint-4.26.0+1-1ubuntu0.1$ head -32 *.c *.h
==> mst_main.c <==
/*
* Copyright (c) 2021 NVIDIA CORPORATION & AFFILIATES. ALL RIGHTS RES
# mantic verification
Setting up mstflint-dkms (4.26.0+1-1ubuntu0.1) ...
Loading new mstflint-4.26.0+1-1ubuntu0.1 DKMS files...
Building for 6.5.0-28-generic
Building initial module for 6.5.0-28-generic
Secure Boot not enabled on this system.
Done.
mstflint_access.ko.zst:
Running module version s
Public bug reported:
I happened to notice that the bump from 23.0.4 to 23.2.1 in jammy
included a change that dropped a number of transitional packages:
mesa (23.1.4-1) unstable; urgency=medium
[ Diederik de Haas ]
* Drop transitional libegl1-mesa package (Closes: #1032712)
* Drop transiti
Hi Andrea - since this is now a stable release update, I *think* the
next steps should be:
1) Edit this bug to use the SRU Template
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
(now done)
Since your team owns this package, please review that and let me know if you
have any conc
** 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 - some
** Summary changed:
- [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from
testing/unstable (main)
+ Backport iproute2 6.8.0 to noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/205167
** Description changed:
[Impact]
Users trying to build software that links w/ jammy's libjsoncpp library will
hit a build failure if that software uses cmake and another library that also
requires libjsoncpp because libjsoncpp's cmake config does not protect against
duplicate imports. This
** Description changed:
[Impact]
Users trying to build software that links w/ jammy's libjsoncpp library will
hit a build failure if that software uses cmake and another library that also
requires libjsoncpp because libjsoncpp's cmake config does not protect against
duplicate imports. This
** Description changed:
[Impact]
- Users trying to build software that links w/ jammy's libjsoncpp library will
hit a build failure if that software uses cmake and another library that also
requires libjsoncpp. This can be reproduced by building a a new version of
cmake itself (reproduced w/
ded
Status: Fix Released
** Affects: libjsoncpp (Ubuntu Jammy)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: libjsoncpp (Ubuntu Mantic)
Importance: Undecided
Status: Fix Released
** Affects: libjsoncpp (Ubuntu Noble)
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 policy:
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 convincing
*** 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 testi
** 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 a
** 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 - some
censing 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
antic)
Status: 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 i
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
he
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
** Changed
** 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?
+ iprou
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 Ubuntu
** 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.
https://bugs.launchpad.net/bug
** 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.
https://bugs.launchpad.net/bug
** 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.
https://bugs.launchpad.net/bug
** 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.
https://bugs.launchpad.net/bug
** 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.
https://bugs.launchpad.net/bug
** 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.
https://bugs.launchpad.net/bug
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 w
** 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.
https://bugs.launchpad.net/bug
** 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 subscrib
*** 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 member
** 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 Ubu
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 t
** 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
https://lkml.iu.edu/hypermail/linux/kernel/2401.3/02766.htm
= 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
ubuntu@ubuntu:~/autotest-client-tests/ubuntu
** 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)
Status
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 mstlin
: 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 =&g
** 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 pro
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 rather
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 d
@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] a
** 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 domai
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 y
** 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 update
** 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 cpuset_sched_doma
** 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.
https://bugs.lau
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:
ubuntu_ltp_contro
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
> locat
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:
ubuntu_ltp_controlle
> 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
---
tus: In Progress => 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 (
** 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
T
** 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 man
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 panic
** 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 load
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 of
. I assume (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 a
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 ker
1 - 100 of 1307 matches
Mail list logo
