** Summary changed:
- sometimes cold boot hangs on unmatched board
+ cold boot panics on unmatched board, soft reboot is fine
** Attachment added: "screenlog.0"
https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1920916/+attachment/5480079/+files/screenlog.0
** Description changed:
Public bug reported:
[ 16.319808] pci :04:00.0: enabling device ( -> 0002)
[ 16.325596] Kernel panic - not syncing: L2CACHE: DirFail @
0x.0001CB00
[ 16.325665] L2CACHE: No. of Banks in the cache: 4
[ 16.332152] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.11.0-1002-generic
For debugging i think it is best to use something like:
console=ttySIF0,115200 earlycon=sbi
note that by default kernel/systemd seem to enable sbi0 hvc0 (via sbi)
ttySIF0 consoles all of which seem to be the same thing.
It is quite confusing.
--
You received this bug notification because you
Public bug reported:
v5.11 kernel seems to sometimes hang on unmatched board
** Affects: linux-riscv (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- v5.11 kernel seems to hang on unmatched board
+ v5.11 kernel seems to sometimes hang on unmatched board
**
@Fred eldmannen+launchpad
This issue is only fixed in the Ubuntu patchset for the Linux Kernel.
Although I have submitted this fix upstream, it has not been picked up
yet by kernel.org vanilla kernels. See
https://lkml.org/lkml/2021/1/14/1091
The mainline builds you point to, do not contain
Kind of wish for a config option that would do add_to_platform_keyring a
built-in set of keys, until we have something like the other platforms
have (ipl on s390x, uefi db on EFI platforms).
Similar to how the built-in trusted keys are initialized.
--
You received this bug notification because
this is all very annoying! But I see what you mean now.
We probably should not add opal keys to the trusted_keyring then.
I would rather avoid introducing a new CA key whilst we cannot travel to
assemble and distribute CA shards offline.
I'd rather somehow enable platform_keyring or IMA
191691 has not been mirrored to launchpad, thus Ubuntu developers cannot
see any of that details.
Note that Ubuntu does not have access to the LTC bugzilla, instead
bugproxy mirrors reports to Launchpad as needed. Please check with hws
if 191691 should be mirrored across, or not.
--
You
@Daniel
"In either case, however, the CA that signs the kernel signing key needs to be
built in to the kernel's .builtin_trusted_keys keyring."
On Ubuntu, for OPAL singing, on PowerPC, we do not use CA at all. It is
our understanding that firmware doesn't support verifying signature
chains to a
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1916165
--
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/1912752
Title:
linux-uc20-efi: megaraid_sas required in the initrd
Status in
ubuntu-core-initramfs v40 has support for main & server features, which
on x86 are enabled by default. The next snap build of pc-kernel in 20/
tracks should contain the required modules.
** Changed in: ubuntu-core-initramfs
Status: In Progress => Fix Released
--
You received this bug
Can you please provide the output of:
$ sudo ubuntu-drivers list
In the live session?
There are two ways to get the nvidia kernel driver. One option is to
compile it from scratch on the users machine with dkms. THe other option
is to install a metapackage linux-modules-nvidia for the
** Also affects: ubuntu-core-initramfs
Importance: Undecided
Status: New
** Changed in: ubuntu-core-initramfs
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@kernel team
please check which dkms packages in -updates fix FTBFS, and if they need
to be rebuilt in -security pocket and released in -security pocket.
** Changed in: linux-meta (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You
Public bug reported:
Support noudeb build profile
When building linux package with noudeb profile active, there should not
be required any udeb specific build-dependencies and the build should
not produce any udebs.
Testcase:
$ sbuild --profiles=noudeb linux*.dsc
should not produce any udebs,
Sorry, this bug is not fixed.
After getting better wifi driver, it gains a different kernel name. And
hence NetworkManager "disconnects" and doesn't reconnect.
When this happens, you need to setup Wifi connection again.
I do not know how to fix this, and/or anticipate the new wifi card name.
** Description changed:
nvidia-graphics-drivers-460
[Impact]
* To aid installer testing of the correct kernels with/without nvidia,
it would be helpful to test nvidia driver installation in qemu VMs
without actually needing nvidia hardware.
* We already have `Modaliases:
** Changed in: linux-raspi (Ubuntu)
Status: New => Confirmed
** Also affects: linux-raspi (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-raspi (Ubuntu Hirsute)
Importance: Undecided
Status: Confirmed
** Also affects: linux-raspi (Ubuntu
adding breaks on linux-meta in -security, on dkms package versions that
are in -updates only, would result in the kernel being held back and not
get autoinstalled.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
@seth-arnold @mdeslaur
Mostly the dkms packages ship source code only, without strict binary
deps on packages/libraries from updates. It should be safe to publish
them into -security pocket.
It is correct that there were a few bugs with dkms modules, which are
now resolved in -updates. But one
Please note that v5.10 oem kernel is not available on the installation
iso.
--
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/1914374
Title:
Multiple issues on HP ZBook 15 G7 after
Feb 3 06:48:34 ubuntu ubiquity[1938]: ubuntu-drivers list-oem finished
with: "oem-stella.cmit-meowth-meta"
$ pull-lp-debs oem-stella.cmit-meowth-meta focal
$ less oem-stella.cmit-meowth-meta_20.04~ubuntu1_all.deb | grep Kernel
Ubuntu-Oem-Kernel-Flavour: oem
Feb 3 06:55:03 ubuntu ubiquity:
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Milestone: None => ubuntu-20.04.2
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Kernel
*** This bug is a security vulnerability ***
Public security bug reported:
Whilst discussing
https://discourse.ubuntu.com/t/improvements-for-hardware-support-in-
ubuntu-desktop-installation-media/20606
We have noticed a reference to somebody not having working backport-
iwlwifi-dkms, whilst
$ sudo qemu-system-x86_64 -kernel ./vmlinuz-5.8.0-41-generic -initrd
./initrd-pad4-5.8.0-41-generic -append 'break=top quiet console=ttyS0'
-m 2G -nographic -no-reboot
Spawning shell within the initramfs
BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.3) built-in shell (ash)
Enter 'help' for a list
Verifying v5.8 build
$ sudo qemu-system-x86_64 -kernel ./vmlinuz-5.8.0-41-generic -initrd
./initrd-pad4-5.8.0-41-generic -append 'break=top quiet console=ttyS0'
-m 2G -nograt
Spawning shell within the initramfs
BusyBox v1.30.1 (Ubuntu 1:1.30.1-4ubuntu6.3) built-in shell (ash)
Enter 'help' for
1) checking that reproducer still fails
sudo qemu-system-x86_64 -kernel ./vmlinuz-5.4.0-64-generic -initrd
./initrd-pad4-5.4.0-64-generic -append 'break=top quiet console=ttyS0'
-m 2G -nograt
[3.581106] Initramfs unpacking failed: Decoding failed
Spawning shell within the initramfs
@vmc
this bugfix is not yet available on any .iso for any series yet. It can
only be tested from installed systems and enabling proposed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Ubuntu supports NVMe Multipath on all architectures in Focal. I know
that some other distributions do not.
Setting nvme-core.multipath=0 for s390x isos only, or changing kernel
config to disable multipath to "n" on s390x only, would mean regression
on s390x as compared with amd64/arm64/ppc64le.
Hirsute)
Importance: High
Assignee: Dimitri John Ledkov (xnox)
Status: Invalid
** Also affects: initramfs-tools (Ubuntu Hirsute)
Importance: High
Status: Invalid
** Also affects: linux (Ubuntu Hirsute)
Importance: High
Status: Confirmed
** Also affects: grub2 (Ubuntu
** 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.
https://bugs.launchpad.net/bugs/1835660
Title:
initramfs unpacking failed
Status in OEM Priority
Is the NVMe drive with or without nvme-multipath support?
Does it help to disable multipath?
Please see the below pullrequest from Canonical employee in efivar project that
explains the issue a bit, and the various paths that the NVMe devices can have.
https://github.com/rhboot/efivar/pull/158
** Changed in: s390-tools (Ubuntu Focal)
Milestone: None => ubuntu-20.04.2
--
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/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
@mihajlov
that is a good point. When there are less than 4GB of RAM, the default
cryptsetup benchmark should probably be capped at 128M of RAM, rather
than 1-2GB. Will ponder about that.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Built a fresh riscv64 image with
$ dpkg-query -W linux-* | grep 5.8
linux-generic 5.8.0.11.11
linux-headers-5.8.0-11-generic 5.8.0-11.13
linux-headers-generic 5.8.0.11.11
linux-image-5.8.0-11-generic5.8.0-11.13
linux-image-generic 5.8.0.11.11
linux-image-unsigned-5.8.0-11-generic
and it looks like that is failing to reboot over telnet connection =/
i'll build a brand new image with 5.8.0-11 kernel directly and will try
that.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
Deployed focal image.
And checked where currently loaded modules are coming from
$ cat /proc/modules |cut -f1 -d\ | xargs -L1 modinfo | sed -n 's/filename:
*//p' | xargs dpkg -S
linux-modules-5.4.0-24-generic:
/lib/modules/5.4.0-24-generic/kernel/drivers/uio/uio_pdrv_genirq.ko
starting verification of the groovy's build. It will take a bit of time
=)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1905620
Title:
please promote modules from extra to
** Description changed:
"initramfs unpacking failed: Decoding failed", message appears on boot
up.
If I "update-initramfs" using gzip instead of lz, then boot up passes
without decoding failed message.
---
However, we currently believe that the decoding error reported in
so what grub is doing is correct.
It pads/aligns every initrd by 4, which is fine, and as per spec.
https://www.kernel.org/doc/html/latest/driver-api/early-userspace
/buffer-format.html
initramfs size can be filled with arbitrary amount of "\0" all the way
upto initramfs_size.
"In human terms,
** Changed in: grub2 (Ubuntu)
Status: Triaged => Invalid
** Changed in: linux (Ubuntu)
Status: Invalid => Triaged
--
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/1835660
@twetzel21 this is not related to those changes at all.
--
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/1835660
Title:
initramfs unpacking failed
Status in OEM Priority Project:
New
Public bug reported:
[ 19.051518] Freeing unused kernel memory: 308K
[ 19.062326] [ cut here ]
[ 19.066219] riscv/mm: Found insecure W+X mapping at address
(ptrval)/0xffdff800
[ 19.074930] WARNING: CPU: 0 PID: 1 at arch/riscv/mm/ptdump.c:200
NAK on the linux patch.
I think this is a grub bug.
When loading multiple initrds, grub aligns_up each one of them at 4bytes
boundary, and allocates pages for that. And it declares and passes
ramdisk_image as the total allocated memory. Rather than the true size
of the initrds.
** Changed in:
(Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
--
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/1835660
** Also affects: grub2 (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/1835660
Title:
initramfs unpacking failed
Status in OEM
Public bug reported:
please promote modules from extra to modules for HiFive Unleashed
The following modules are used by the HiFive Unleashed board from extra
Please install them in modules.
linux-modules-extra-5.4.0-24-generic:
/lib/modules/5.4.0-24-generic/kernel/drivers/net/phy/mscc.ko
So lz4 compressed initrd looks like this with hexdump
568f580 0523 00ac 54bf 4152 4c49 5245 2121 0021
568f590 0001 1cff 0050
568f59a
I do wonder what ram is initialized too, and how those things look when
kernel reads initrd from memory as loaded by the bootloader /
Public bug reported:
5.8.0-9.11 and other v5.8 kernels all fail to boot in qemu with opensbi
and qemu.
I'm booting a cloud-image with kenrel install like this:
qemu-system-riscv64 -machine virt -m 2048 -smp 4 -kernel
/usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf -device
linux-meta-aws patch is submitted at https://lists.ubuntu.com/archives
/kernel-team/2020-November/114920.html
** Also affects: linux-meta-aws (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
+ Now that micorocode-initrd is in focal, linux-meta-aws should start
+
@Siarhei
That looks very valid. And we were close to getting to that, when apw &
I timed out looking at this.
lz4 -l Use Legacy format (typically for Linux Kernel compression)
Note : -l is not compatible with -m (--multiple) nor -r
Which must always be used when creating
Also i guess we (i) need to retest if
https://github.com/lz4/lz4/releases/tag/v1.9.3 fixes all the things =/
--
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/1835660
Title:
initramfs
https://github.com/snapcore/secboot/pull/127
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1877533
Title:
[20.10 FEAT] Increase the crashkernel setting if the root volume is
Are these installs with zkey/paes or without?
Because, in Ubuntu, when zkey was introduced I have reverted the
s390-tools upstream change to lower the argon2i settings. Due to my lack
of understanding of the security features there. And later, we have made
similar choices for TPM backed
** Changed in: s390-tools (Ubuntu Focal)
Importance: Undecided => Wishlist
--
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/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
yes kernel config changes will be needed for this.
** Changed in: ubuntu-power-systems
Status: Incomplete => Confirmed
--
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/1903288
Public bug reported:
ubuntu-seed / ubuntu-boot partition detection could be improved
Currently in the initrd, snapd-bootstrap searches for ubuntu-boot /
ubuntu-seed partition by label or by UEFI variable that was set by sd-
boot.
sdboot uses devicepath UEFI protocol to establish
Related ubuntu-drivers bug for better UX
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/1900870
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
** Tags added: block-proposed-groovy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1900865
Title:
NVIDIA drivers aren't running after fresh groovy install with
Two things:
1) Old iso used, which had dkms bit fixed in the 21 iso.
2) nvidia-graphics-drivers-455 got built and migrated with a matching
lrm.
nvidia-graphics-drivers-455 must have never migrated to groovy-release
without lrm
** Also affects: linux-restricted-modules (Ubuntu)
Oct 20 17:23:15 ubuntu-budgie ubiquity: /sbin/update-secureboot-policy: 44: 3:
Bad file descriptor#015
Oct 20 17:23:15 ubuntu-budgie ubiquity: Done.#015
looks like when 3rd party drivers box is not ticked (and mok enrolment
pin not configured), and broadcom driver is attempted to be installed,
btw, what is the state of MOK? i.e.
$ sudo mokutil --list-enrolled
$ ls /var/lib/shim-signed
$ ls /var/lib/shim-signed/mok/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1899678
Title:
Can you open bug report against ubiquity with like $ ubuntu-bug ubiquity
?
that would collect all the installer logs, which will help to
investigate this.
Or can you please attach /var/log/installer as a tarball? do check for
any sensitive info there, or feel free to mark this bug report
** Changed in: linux-meta (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1893205
Title:
linux-generic-hwe-20.04 transitional to
** Changed in: linux (Ubuntu Groovy)
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/1899519
Title:
booting linux-generic-lpae armhf kernel
https://lists.ubuntu.com/archives/kernel-team/2020-October/114068.html
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: bot-stop-nagging
** Tags added: patch
--
You received this bug notification
wait, raspi images must already be using v5.4 kernel on bionic
See https://launchpad.net/ubuntu/+source/linux-raspi-5.4
Why are you upgrading firmware, without upgrading the kernel to v5.4?
Why are you using obsolete images, from the archived location, instead
of the most recent ones?
v4.15
Public bug reported:
UC20 kernel missing /firmware/regulatory.db and
/firmware/regulatory.db.p7s
Whilst present in the UC18 kernel snap.
At runtime, this causes failure to load regulatory database, and perform
wifi scan.
[ 27.510199] platform regulatory.0: Direct firmware load for
The plan was to move kernel to v5.4 kernel in bionic. and the firmware
was already matching that.
You could enable focal repository and install linux-raspi kernel v5.4
from there?
** Also affects: linux-raspi2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
@paulo awesome; will there be a kernel respin? if yes, can we also take
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899582 ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I ponder if raspi kernel also needs this on armhf
debian.raspi/config/config.common.ubuntu:# CONFIG_ARM_MODULE_PLTS is not
set
--
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/1899519
CONFIG_ARM64_MODULE_PLTS is enabled; because CONFIG_ARM64_ERRATUM_843419
is enabled in zesty+ (backported to yakkety too) see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647793
groovy/master:debian.master/config/annotations:CONFIG_ARM64_ERRATUM_843419
So
>> 1/ inode numbers will be seen to have changed between kernel versions.
>>32-bit arches will see large inode numbers now instead of the hashed
>>ones they saw before.
>>
That seems fine to me. This is all during runtime only, and doesn't
change ondisk format at all right?
>> 2/
[0.110128] /cpus/cpu@0 missing clock-frequency property
[0.110426] /cpus/cpu@1 missing clock-frequency property
[0.190376] CPU1: Spectre v2: firmware did not set auxiliary control
register IBE bit, system vulnerable
[ 11.068045] cryptd: section 4 reloc 15 sym '__stack_chk_fail':
and same with 22 kernel.
--
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/1899519
Title:
booting linux-generic-lpae armhf kernel under qemu results in
relocation out of range, and thus
Has this been forwarded to the stable trees?
I do not see it applied on 5.8.x-stable or lower trees.
Currently only available in linux-5.9 which we are not shipping yet.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
** Package changed: ceph (Ubuntu) => linux (Ubuntu)
--
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/1899582
Title:
ceph: fix inode number handling on arches with 32-bit ino_t
Status in
@ubuntu-kernel-bot given i can't boot past initrd, what do you expect
from me?
** Tags added: bot-stop-nagging
** Summary changed:
- booting armhf kernel under qemu results in relocations out of range, and thus
no modules are loaded
+ booting linux-generic-lpae armhf kernel under qemu results
20, 21 kernels were both bad. Testing 22 kernel now.
--
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/1899519
Title:
booting armhf kernel under qemu results in relocations out of range,
-M virt,highmem=off still shows relocation 28 out of range upon trying
to load any kernel modules.
--
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/1899519
Title:
booting armhf kernel
I wonder if this is because -M virt defaults to highmem=on, I will try
again with highmem=off
--
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/1899519
Title:
booting armhf kernel under
Public bug reported:
qemu-system-arm -M virt -m 4096 -smp 2,sockets=2,cores=1,threads=1
-drive file=./groovy-server-cloudimg-armhf.img,if=virtio -kernel
./vmlinuz-5.8.0-21-generic-lpae -initrd ./initrd.img-5.8.0-21-generic-
lpae -append 'root=LABEL=cloudimg-rootfs break=bottom' -nographic
[
** Changed in: linux-raspi (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1881159
Title:
BUG: soft lockup on return from recover to run
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Description changed:
[Impact]
* Currently Canonical Livepatch service is signing kernel modules that
are not trusted
** Description changed:
[Impact]
- * Currently Canonical Livepatch service is signing kernel modules that
+ * Currently Canonical Livepatch service is signing kernel modules that
are not trusted by the default Ubuntu kernels
- * to make Canonical Livepatch service out of the box
Public bug reported:
[Impact]
* Currently Canonical Livepatch service is signing kernel modules that
are not trusted by the default Ubuntu kernels
* to make Canonical Livepatch service out of the box compatible with
SecureBoot, please add Canonical Livepatch service key as trusted in the
https://www.freedesktop.org/software/systemd/man/systemd.network.html#VRF=
VRF= The name of the VRF to add the link to. See systemd.netdev(5).
vrf A Virtual Routing and Forwarding (VRF) interface to create separate
routing and forwarding domains.
[VRF] Section Options
The [VRF] section only
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Status: New => Confirmed
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
i think this was since fixed, no?!
** Tags removed: update-excuse
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1721558
Title:
ubuntu-regression-suite fails
Status in linux
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
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/1863116
Title:
debian/rules editconfigs does not work on s390x to change
https://lists.ubuntu.com/archives/kernel-team/2020-September/113356.html
** Package changed: linux-aws (Ubuntu) => linux-meta-aws (Ubuntu)
** Changed in: linux-meta-aws (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
Public bug reported:
[Availability]
* Groovy Universe
[Rationale]
* Needed to apply microcode updates, on bare-metal public-cloud
machines, that otherwise boot without a full initrd.
[Security]
* This package is tiny, just a single small shell script trigger hook
that create
Yes, kexec-tools should ship finalrd hook to fix this.
** Changed in: finalrd (Ubuntu)
Status: New => Won't Fix
** Changed in: kexec-tools (Ubuntu)
Status: New => Triaged
** Changed in: kexec-tools (Ubuntu)
Importance: Undecided => High
--
You received this bug notification
Public bug reported:
* linux lacks CET, not upstream yet
* snapd lacks CET, as golang has no support for CET yet
* libunwind lacks CET, as no upstream support yet
* klibc lacks CET, no upstream support yet
** Affects: golang-defaults (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (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/1894611
Title:
kmod in bionic can't parse hwe/cloud kernel
** Changed in: linux-meta (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1893205
Title:
linux-generic-hwe-20.04 transitional to
All tests run automatically, and yes flatpak-builder was automatically
tested and new flatpak with this fix migrated fine.
See http://autopkgtest.ubuntu.com/packages/flatpak-builder/groovy/s390x
** Also affects: flatpak (Ubuntu)
Importance: Undecided
Status: New
** Changed in: flatpak
** Changed in: linux (Ubuntu)
Status: Fix Committed => In Progress
** Changed in: ubuntu-z-systems
Status: Fix Committed => In Progress
** Package changed: linux (Ubuntu) => zfcpdump-kernel (Ubuntu)
** Changed in: zfcpdump-kernel (Ubuntu)
Assignee: Canonical Kernel Team
Public bug reported:
linux-generic-hwe-20.04 transitional to linux-generic does not exist in
groovy, instead it still points at 5.4 kernel.
Please create transitional meta from linux-generic-hwe-20.04 to linux-
generic.
Otherwise machines that installed Ubuntu Desktop focal, then upgrade to
@colin-king with or without additional measurements default to
performance and relying on userspace to switch to ondemand at some later
point during boot is wrong. It means we are risking melting laptops and
catching fire. I.e. boot machine, walk away, it sits in the initrd at
the LUKS unlock
901 - 1000 of 1812 matches
Mail list logo
