** 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
** 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 Kernel
Packages, which is subscribed to linux in 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 Kernel
Packages, which is subscribed to linux in 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
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1951289
Title:
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1952933
Title:
impish kernel crashes on hp m400 in
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1966194
Title:
[Jammy, mlx5, ConnectX-7] add CX7 support for
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967754
Title:
ubuntu 22.04 jammy, mlx5, can't change flow
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967562
Title:
jammy beta (220330) arm iso pxe
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967562
Title:
jammy beta (220330) arm iso pxe boot kernel panic
** Merge proposal linked:
https://code.launchpad.net/~xypron/grub/+git/grub/+merge/419407
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967562
Title:
jammy beta (220330) arm iso
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1918427
Title:
curtin: install flash-kernel in arm64
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 Kernel
Packages, wh
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https
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 Kernel
Packages, which is subscribed to linux in 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
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 Kernel
Packages, which is
@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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967562
Title:
jammy beta (220330) arm iso kernel panic during pxe boot
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
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 Kernel
Packages, which is subscribed to linux in
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
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 Kernel
Packages, which is subscribed to linux in 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 Kernel
Packages, which is subscribed to linux in Ubuntu.
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 Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1963926
** 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:
= focal verification =
ubuntu@client:~$ cat /proc/version_signature
Ubuntu 5.4.0-102.115-generic 5.4.174
ubuntu@client:~$ ./elbencho/bin/elbencho -t 40 -r -n 10 -N 5000 -s 128k -b 128k
/mnt/nfs/ubuntu
OPERATION RESULT TYPEFIRST DONE LAST DONE
= ==
kernel change submitted:
https://lists.ubuntu.com/archives/kernel-team/2022-February/128309.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1962185
Title:
Add ConnectX7 support
ntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1962185
Title:
Add
Here's a decoded backtrace of the 5.0-rc5+ crash (commit 41ceb5e8 w/ the
fix from commit 620a6dc4075 applied), which looks quite plausible.
static void __free_domain_allocs(struct s_data *d, enum s_alloc what,
const struct cpumask *cpu_map)
{
[...]
1196case
I came back to this and found that I now can get a failure w/ error
messages when applying the fix (see comment #4) to bionic - see crash
log below. So, I figured I could just bisect between v4.15 and v5.11
upstream w/ the fix applied and and figure out what other change(s) are
required to avoid
I've identified the problem(s) and reported it upstream:
https://lore.kernel.org/linux-
pci/Yf2wTLjmcRj+AbDv@xps13.dannf/T/#m4d8283082c3fded15050e03a9ad8aef53ad07394
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
On a DGX A100:
ubuntu@blanka:~$ cat /proc/version
Linux version 5.4.0-99-generic (buildd@lgw01-amd64-007) (gcc version 9.3.0
(Ubuntu 9.3.0-17ubuntu1~20.04)) #112-Ubuntu SMP Thu Feb 3 13:50:55 UTC 2022
ubuntu@blanka:~$ dpkg -l linux-modules-nvidia-470-server-5.4.0-99-generic
** Changed in: maas-images
Status: New => In Progress
** Changed in: maas-images
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
ernel (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954692
Title:
Reconsider compressed kernels on arm64
Status in maas-imag
** Also affects: flash-kernel (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954692
Title:
Reconsider compressed kernels on arm64
It appears that the reason verification-needed-focal is applied here is
because these patches were included in the linux-intel flavor, whose
description says "A kernel image for Intel IOTG devices." I'm not sure
what the expectations are for verifying bugs with that flavor - should
they all be
Forwarded upstream: https://www.spinics.net/lists/dri-
devel/msg330115.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1958583
Title:
entering gnome lockscreen causes astfb displays
On Thu, Jan 20, 2022 at 7:30 PM Daniel van Vugt
<1958...@bugs.launchpad.net> wrote:
>
> While waiting for a kernel fix, this workaround might avoid it:
>
> MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
>
> in /etc/environment
Thanks Daniel! Strangely though, that causes gdm to only show a
background, so I'm
** Attachment added: "sosreport-starbuck-2022-01-20-ziauesz.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1958583/+attachment/972/+files/sosreport-starbuck-2022-01-20-ziauesz.tar.xz
--
You received this bug notification because you are a member of Kernel
Packages,
I found that this issue also impacts upstream kernels, so I bisected and
found that the problem was introduced in this commit:
commit d6ddbd5c97d1b9156646ac5c42b8851edd664ee2
Author: Thomas Zimmermann
Date: Thu May 7 11:06:40 2020 +0200
drm/ast: Don't check new mode if CRTC is being
Public bug reported:
When I install ubuntu-desktop on servers with an AMI BMC, I find a
remote desktop running on the BMC's virtual KVM display hangs when I
transition to the lock screen. The screen either goes blank and fails to
wake up on keyboard/mouse input - or the lock screen appears but
** Attachment added: "nfstest_delegation-5.4.0-95-generic+fix.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957986/+attachment/254/+files/nfstest_delegation-5.4.0-95-generic+fix.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Description changed:
[Impact]
An NFSv4 client that does a lot of opens/closes can overwhelm and NFSv4
server, causing a significant drop in performance. In my testing, I've seen
performance drop from ~700MiB/s down to < 10MiB/s. The same workload using
NFSv3 does not have this problem.
ntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Imp
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Verification:
ubuntu@d06-4:~$ cat /proc/version
Linux version 4.15.0-167-generic (buildd@bos02-arm64-067) (gcc version 7.5.0
(Ubuntu/Linaro 7.5.0-3ubuntu1~18.04)) #175-Ubuntu SMP Wed Jan 5 01:58:16 UTC
2022
ubuntu@d06-4:~$ lsmod | grep hisi_sas
hisi_sas_v3_hw 40960 2
hisi_sas_main
So it looks like the proposal here is to backport the impish version of
crash back through focal, which means an upstream version bump.
Resolving the issue in this way normally requires a documented special
case to the SRU process[*], and I don't see one that includes the crash
package.
I'd be
** Changed in: kunpeng920/ubuntu-18.04
Status: In Progress => Fix Committed
** Changed in: kunpeng920
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Confirmed => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Hirsute)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux (Ubuntu Impish)
Assignee: (unassigned) => dann frazie
Public bug reported:
[Impact]
rx performance is sub-optimal with EVB-LAN7430 NICs.
[Test Case]
Use iperf3 to submit TCP or UDP traffic to a host w/ a EVB-LAN7430 NIC.
[Fix]
Cherry-pick the following upstream commit:
a1f1627540cde net: ethernet: microchip: lan743x: Increase rx ring size
to
The fix above also cherry-picks back to bionic, but strangely it causes
the bionic kernel to fail to boot. I don't see any kernel messages after
the EFI stub. I tried adding "earlycon" to get more debug info, but that
somehow avoids the problem and boots fine w/ the fix. With earlycon, I
can
: kunpeng920
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: kunpeng920/ubuntu-18.04
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix
= hirsute verification =
ubuntu@blanka:~/nvidia-dgx-2/tests$ cat /proc/version
Linux version 5.11.0-42-generic (buildd@lgw01-amd64-041) (gcc (Ubuntu
10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #46-Ubuntu
SMP Fri Nov 26 12:04:17 UTC 2021
ubuntu@blanka:~/nvidia-dgx-2/tests$
** Changed in: linux (Ubuntu Focal)
Assignee: dann frazier (dannf) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1923104
Title:
Include Infiniband Peer Mem
** Changed in: linux (Ubuntu Impish)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
During MAAS deployment:
[ 107.768146] Unable to handle kernel read from unreadable memory at
virtual address
domain : maas[ 107.943413]
Mem abort info:
rootserver: 10.229.32.21 rootpath:
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance:
** Changed in: makedumpfile (Ubuntu)
Status: New => In Progress
** Changed in: makedumpfile (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
** Merge proposal unlinked:
https://code.launchpad.net/~dannf/+git/maas-preseeds/+merge/411293
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-base in Ubuntu.
https://bugs.launchpad.net/bugs/1926985
Title:
linux-version sort:
** Tags added: verification-done verification-done-bionic verification-
done-focal verification-done-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-base in Ubuntu.
https://bugs.launchpad.net/bugs/1926985
Title:
The above test failures all seemed to pass upon re-run.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-base in Ubuntu.
https://bugs.launchpad.net/bugs/1926985
Title:
linux-version sort: argv and stdin behaviors differ
Status in
problems (hangs, crashes, corruption)
with such workloads.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: In Progress
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Assignee: dann frazier (dannf)
Status
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: linux-restricted-modules (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
patch https://lists.ubuntu.com/archives/kernel-
team/2021-October/124751.html
** Changed in: linux-restricted-modules (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: linux-restricted-modules (Ubuntu)
Status: New => In Progress
--
You received th
Public bug reported:
$ apt showsrc linux-restricted-modules | grep -e ^Version: -e server
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
Version: 5.13.0-16.16
Version: 5.13.0-19.19
** Affects: linux-restricted-modules (Ubuntu)
Importance: High
Also good in focal:
ubuntu@doerfel:~$ cat /proc/version
Linux version 5.13.0-17-generic (buildd@bos02-arm64-034) (gcc (Ubuntu
9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34)
#17~20.04.1-Ubuntu SMP Tue Sep 28 14:05:10 UTC 2021
--
You received this bug notification because
Verified:
ubuntu@doerfel:~$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.13.0-18-generic
root=UUID=36113164-ebf4-4fed-9d98-4b0b859bf98e ro acpi=force
ubuntu@doerfel:~$ cat /proc/version
Linux version 5.13.0-18-generic (buildd@bos02-arm64-027) (gcc (Ubuntu
11.2.0-7ubuntu2) 11.2.0, GNU ld (GNU
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1942633
Title:
Can not boot impish in Cavium ThunderX
Status in
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1940860
Title:
Mellanox NIC interface names change
And here's some proposed text. I assume this would be applicable to the
release notes from 20.04->22.04
= Known Issues =
== Network Interface Names ==
Ubuntu generates [predictable interface
names](https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/)
by default.
The patch was merged into 5.13.0-17.17, which is currently in impish-proposed.
At some point it should promulgate to the release pocket. You can view the
status here:
https://launchpad.net/ubuntu/+source/linux
I don't know how long after that it will before it appears in images. As
a
Understood, thanks for considering the issue. Perhaps this just needs to
be release noted, warning users it may happen and how to avoid it (i.e.
implement their own set-name config)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
A patch has been merged into the arm64 tree and is tagged for stable
5.13+
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1942633
Title:
Can not boot impish in Cavium ThunderX
Status
Patch submitted:
https://www.spinics.net/lists/arm-kernel/msg922152.html
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Root caused and reported upstream:
https://www.spinics.net/lists/arm-kernel/msg921821.html
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
= verification =
root@dannf-lp1935855:~# wget
https://launchpad.net/ubuntu/+archive/primary/+files/linux-image-4.15.0-1100-kvm-dbgsym_4.15.0-1100.102_amd64.ddeb
--2021-09-21 17:13:41--
Update: The issue does not follow toolchain, which is good. Rather I did
find that upstream v5.13-rc1 is stable - with the patch in comment #15
reverted - while upstream v5.13 is not. I bisected v5.13-rc1..v5.13,
reverting the comment #15 patch at each test. A "bad" kernel wouldn't
always fail the
hm.. you're right. I was tracking down a different issue which had the
following backtrace:
[ 10.701967] Call trace:
[ 10.704415] ata_host_activate+0x160/0x170
[ 10.708518] ahci_host_activate+0x170/0x1e0
[ 10.712711] ahci_init_one+0x898/0xd74 [ahci]
[ 10.717116]
First bad commit:
commit 9ec37efb87832b578d7972fc80b04d94f5d2bbe3 (HEAD, refs/bisect/bad)
Author: Marc Zyngier
Date: Tue Mar 30 16:11:42 2021 +0100
PCI/MSI: Make pci_host_common_probe() declare its reliance on MSI domains
The generic PCI host driver relies on MSI domains for MSIs
For the CRB1S systems, the following is the firmware string that
matters, and it shows that phanpy is running the latest (and very likely
final) version:
BIOS Date: 06/14/2018 14:42:48 Ver: 0ACGA022
Note that this is also reproducible on our Gigabyte R120 systems which
use acpi=force by default,
I can attempt a bisect - let me know if someone else is already doing
that :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1942633
Title:
Can not boot impish in Cavium ThunderX
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => Triaged
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => dann frazier (dannf)
--
You received this bug notification becau
@ddstreet I agree that systemd is behaving as designed. But I'm not sure
what the proper fix for this is, and therefore where changes would be
required.
My initial thought is that perhaps subiquity installs should do what
MAAS installs do and configure netplan to always use the install-time
Public bug reported:
I noticed on a couple of systems that my network interface names change
when upgrading from the focal LTS (5.4) kernel to the focal HWE (both
5.8 & 5.11) kernels. Both systems have Mellanox Connect-X 5 NICs.
dannf@bizzy:~$ uname -a
Linux bizzy 5.4.0-81-generic #91-Ubuntu SMP
Upstream has been working with me to try to determine what is going on
here. The conclusion is that we believe that firmware is piggy-backing
on the ARM_SMCCC_ARCH_WORKAROUND calls, and is clobbering some of the
registers in the x4-x17 range. The patch series mentioned in Comment #9
happens to
101 - 200 of 1621 matches
Mail list logo
