** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Tags added: rls-hh-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu.
https://bugs.launchpad.net/bugs/1923150
20.04.1 is obsolete point release. Can you please try with 20.04.2?
** Changed in: nvidia-graphics-drivers-455 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-455 in
BTW. is https://patchwork.kernel.org/project/linux-
integrity/patch/20210330131636.21711-4-na...@linux.ibm.com/ of any help
to us?
Ideally we'd want to do that, but load the 2017 & 2019 keys there into
the .ima keyring instead of the kernel module signing ones.
--
You received this bug
It appears that although fdtdir option from u-boot-menu works on bare
metal, it breaks qemu booting.
Thus revert it from now, seeking more details from u-boot upstream.
** Also affects: u-boot-menu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: u-boot-menu (Ubuntu)
** Tags added: fr-1282
--
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/1923162
Title:
riscv64 images fail to boot in qemu
Status in linux-riscv package in Ubuntu:
Invalid
Status
So the issue around providing fdtdir was that qemu did not know what fdt
file to attempt loading, and hence was failing to boot.
Now that we dropped fdtdir in extlinux.conf, all riscv64 boards need to
use preboot to pick up fdt from the .itb. This was already the case on
unleashed and smode, but
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu)
Milestone: None => ubuntu-21.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
** Changed in: u-boot (Ubuntu Hirsute)
Status: Fix Released => New
--
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/1923162
Title:
riscv64 images fail to boot in qemu
Status
** Tags added: block-proposed block-proposed-hirsute
--
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/1923162
Title:
riscv64 images fail to boot in qemu
Status in linux-riscv
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.
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,
** Changed in: linux (Ubuntu)
Status: New => 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/1939937
Title:
ath10k: "add target IRAM recovery feature support" breaks
** Tags added: hirsute impish patch
--
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/1939937
Title:
ath10k: "add target IRAM recovery feature support" breaks QCA9984
Firmware load
Hirsute:
$ uname -a
Linux ubuntu 5.11.0-1017-generic #18-Ubuntu SMP Wed Aug 11 18:02:14 UTC 2021
riscv64 riscv64 riscv64 GNU/Linux
$ systemctl is-system-running
running
$ sudo dmesg | grep gcc
[0.00] Linux version 5.11.0-1017-generic
(buildd@riscv64-qemu-lcy01-065) (gcc (Ubuntu
Public bug reported:
872621:59:37 INFO | Timer expired (1800 sec.),
nuking pid 10418
872721:59:38 INFO | ERROR
ubuntu_kernel_selftests.netubuntu_kernel_selftests.net
timestamp=1628805578localtime=Aug 12 21:59:38
Public bug reported:
$ sudo make -C tools/testing/selftests TARGETS=ftrace run_tests
...
# [32] ftrace - Max stack tracer[FAIL]
...
Testing using 5.13.0-1002.2
the full ftrace suite takes just over 2 hours on unmatched.
** Affects: ubuntu-kernel-tests
Importance: Undecided
[10052.121189] rcu: INFO: rcu_sched self-detected stall on CPU
[10052.126125] rcu: 1-: (14995 ticks this GP)
idle=a3a/1/0x4002 softirq=116019/116019 fqs=7426
[10080.057250] watchdog: BUG: soft lockup - CPU#1 stuck for 82s!
[ftracetest:30662]
[10124.057368] watchdog: BUG:
** Description changed:
$ sudo make -C tools/testing/selftests TARGETS=ftrace run_tests
...
# [32] ftrace - Max stack tracer [FAIL]
...
+ Testing using 5.13.0-1002.2
- Testing using 5.13.0-1002.2
+ the full ftrace suite takes just over 2 hours on unmatched.
--
You received
Verifying using hirsute:
# uname -r
5.11.0-1014-kvm
# grep CODENAME /etc/os-release
VERSION_CODENAME=hirsute
UBUNTU_CODENAME=hirsute
# keyctl list %:.blacklist
Can't find 'keyring:.blacklist'
Upgraded kernel:
# uname -r
5.11.0-1015-kvm
# keyctl list %:.blacklist
1 key in keyring:
330780907:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928679/comments/7
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
# grep CODENAME /etc/os-release
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal
# uname -r
5.11.0-34-generic
dmesg:
[0.797134] blacklist: Loading compiled-in revocation X.509 certificates
[0.797696] Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing:
Disabled initrd less boot, and installing linux-generic kernel from
proposed.
--
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/1928679
Title:
Support importing mokx keys into revocation
# uname -r
5.11.0-34-generic
# sudo keyctl list %:.platform
3 keys in keyring:
149920180: ---lswrv 0 0 asymmetric: Microsoft Windows Production PCA
2011: a92902398e16c49778cd90f99e4f9ae17c55af53
434591909: ---lswrv 0 0 asymmetric: Canonical Ltd. Master Certificate
Authority:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928679/comments/6
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
When booting with UEFI, mokvar table and %:.platform keyring must be
available
** Affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm
for failed results, in artifacts, all make.logs are stored and available
for download and inspection.
** Changed in: dkms (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
Public bug reported:
aws 5.11.0-1015 kernel is no longer published in focal.
but nvidia modules for it remain in focal-proposed, preventing lrm-
aws-5.11 from migrating.
please remove the following binaries:
old binaries left on amd64:
linux-modules-nvidia-390-5.11.0-1015-aws
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Tags added: apport-collected
--
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/1936237
Title:
use the upstream
Public bug reported:
08/12 22:10:03 DEBUG| utils:0153| [stdout] # === Ftrace unit tests ===
08/12 22:10:07 DEBUG| utils:0153| [stdout] # [1] Basic trace file check
[PASS]
08/12 22:10:45 DEBUG| utils:0153| [stdout] # [2] Basic test for tracers
[PASS]
08/12 22:10:51 DEBUG|
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Tags added: focal riscv64
** Summary changed:
- selftests net times out
+ ubuntu_kernel_selftests.net times out on riscv64 unmatched hirsute & focal
--
You received this bug notification because you are a
v5.13 in impish-proposed has this fixed on riscv.
it will not be backported to earlier series, hence marking hirsute as
wontfix.
** Changed in: linux (Ubuntu Impish)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Hirsute)
Status: New => Won't Fix
** Changed in:
--
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/1939887
Title:
ubuntu_kernel_selftests.net times out on riscv64 unmatched hirsute &
focal
Status in ubuntu-kernel-tests:
New
*** This bug is a duplicate of bug 1900644 ***
https://bugs.launchpad.net/bugs/1900644
** Summary changed:
- ubuntu_kernel_selftests.net times out on riscv64 unmatched hirsute & focal
+ ubuntu_kernel_selftests.net times out on riscv64 unmatched hirsute & focal
mailing multi_check_sendfile
Focal
ubuntu@ubuntu:~$ dmesg | grep gcc
[0.00] Linux version 5.11.0-1017-generic
(buildd@riscv64-qemu-lcy01-062) (gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0,
GNU ld (GNU Binutils for Ubuntu) 2.34) #18~20.04.1-Ubuntu SMP Thu Aug 12
00:38:00 UTC 2021 (Ubuntu
backports is no good, as it needs to be kernel's build-dep. and most
kernels are built in -security only pocket.
also, nothing else really uses these, apart from kernel. And kernels
have stop using these, because they are too old in focal.
** Changed in: dwarves-dfsg (Ubuntu Focal)
** Also affects: linux-riscv-5.11 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-riscv-5.11 (Ubuntu Hirsute)
** Changed in: linux-riscv-5.11 (Ubuntu)
Status: New => Invalid
** Changed in: linux-riscv-5.11 (Ubuntu Focal)
Status: New => Confirmed
Public bug reported:
[Impact]
* A kernel build can fail to boot with Oops and illegal instruction as
seen at https://bugs.launchpad.net/ubuntu/+source/linux-
riscv-5.11/+bug/1934548 on Unmatched board.
* One cannot frace functions, used in frace setup. On RISC-V these are
sbi calls to
** Also affects: linux-riscv (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-riscv-5.11 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-riscv (Ubuntu Focal)
Status: New => Won't Fix
** Changed in: linux-riscv-5.11 (Ubuntu
Public bug reported:
gcp 5.11.0-1016 kernel is no longer published in focal.
but nvidia modules for it remain in focal-proposed, preventing lrm-
gcp-5.11 from migrating.
please remove the following binaries:
old binaries left on amd64:
linux-modules-nvidia-390-5.11.0-1016-gcp
Public bug reported:
oracle 5.11.0-1015 kernel is no longer published in focal.
but nvidia modules for it remain in focal-proposed, preventing lrm-
oracle-5.11 from migrating.
please remove the following binaries:
old binaries left on amd64
linux-modules-nvidia-390-5.11.0-1015-oracle
** Changed in: linux-restricted-modules-aws-5.11 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules-aws-5.11 in
Ubuntu.
https://bugs.launchpad.net/bugs/1941608
Title:
** Changed in: linux-restricted-modules-oracle-5.11 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules-oracle-5.11 in
Ubuntu.
https://bugs.launchpad.net/bugs/1941612
** Changed in: linux-restricted-modules-gcp-5.11 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules-gcp-5.11 in
Ubuntu.
https://bugs.launchpad.net/bugs/1941610
Title:
Public bug reported:
[Impact]
Bump unmatched CPU clock rate to 1.5GHz
Multiple users report that running unmatched at 1.5GHz is stable, and
gives one performance.
Lets bump clock speed to 1.5GHz in u-boot and kernel.
[Test Plan]
* System with these patches boots, operates normally without
** No longer affects: linux-riscv (Ubuntu)
--
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/1941622
Title:
Bump unmatched CPU clock rate to 1.5GHz
Status in u-boot package in
The security PPA where 5.11.0-27 was built has "build dbgsyms" checked
but not "publish dbgsyms" this seems odd, cause i would think it is
useful to have access to published security ppa dbgsymbols.
Removing debug symbols is not nice. However, surely we can make disk
space savings the other way.
** Changed in: linux-hwe-5.11 (Ubuntu Focal)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: linux-hwe-5.11 (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Kernel
Packages,
** Description changed:
[Impact]
* Unable to use gpio-poweroff driver to poweroff via u-boot/opensbi/kernel
* Unable to use LED colors
* Unable to mmap PCI resources
* Cherrypick dtb changes from meta-sifive 2021.08 release
** Description changed:
[Impact]
- * Unable to use gpio-poweroff driver to poweroff via u-boot/opensbi/kernel
- * Unable to use LED colors
- * Unable to mmap PCI resources
+ * Unable to use gpio-poweroff driver to poweroff via u-boot/opensbi/kernel
+ * Unable to use LED colors
+ *
extensions, which is a step backwards.
OpenSBI v0.1 will not be available in the future.
** Affects: linux-riscv (Ubuntu)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: In Progress
** Changed in: linux-riscv (Ubuntu)
Assignee: (unassigned) => Dimitri J
Imho we must enabled it, especially for Oracle, since compute nodes may
be shared between multiple tenants.
It would be also interesting to check if the hardware used with this
kernel does not have errata / issues discussed in
https://www.spinics.net/lists/arm-kernel/msg788470.html i.e. that it
Re: u-boot-menu backport, imho debian/changelog should have documented
that debhelper-compat version is lowered from 13 to 12, to make it build
on focal. But also it is self-explanatory (i did try to get debhelper 13
into focal before it released, but that upload got rejected).
Otherwise no
@jawn-smith https://paste.ubuntu.com/p/hjqFz46frm/ is what i'm
sponsoring, after fix ups.
--
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/1923162
Title:
riscv64 images fail to boot
re: u-boot-menu backport, imho the debian/changelog should be merged and
focal entries should not be lost.
--
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/1923162
Title:
riscv64
I would have thought that this patch upstream would have been suitable
for stable series.
It seems like the bug that the patch fixes is not annotated correctly,
hence it was not picked for stable updates yet.
I wonder if we should try to submit to linux-stable for v5.4 v5.8
series.
--
You
Public bug reported:
Over at https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-
dkms/+bug/1932158
you can observe that it was chosen to skip the dkms module for a given
kernel, and dkms-autopkgtest did not manage to handle it well.
** Affects: dkms (Ubuntu)
Importance: Undecided
** Description changed:
[Impact]
Upstream linux kernel now supports configuring built-in revoked
certificates for the .blacklist keyring.
Add support in our kernel configuration to have built-in revoked
certificates.
Revoke UEFI amd64 & arm64 2012 signing certificate.
I am failing to reliably reproduce this issue.
At first I have experienced this too. When I tried to bisect it and install
multiple kernel abis they are all booting fine.
So I was able to fail booting 1014 1015 1016 abis. And then they started
to boot fine.
I wonder if there is some
[0.00] XNOX kernel/trace/ftrace.c(6255) ftrace_process_locs:
[0.00] XNOX kernel/trace/ftrace.c(6272) ftrace_process_locs:
[0.00] Oops - illegal instruction [#1]
[0.00] Modules linked in:
[0.00] CPU: 0 PID: 0 Comm: swapper Not tainted 5.11.0-1015-generic
added more pr_info calls inside ftrace_update_code.. and things boot
now for me. =
--
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/1934548
Title:
RISC-V: Illegal
Something like this https://github.com/snapcore/core-
initrd/pull/34/files should do it. Plus respinning the pc-kernel arm64 &
armhf kernel snaps.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
Doing this in "kernel-snaps-uc20" git repo would be tricky, as at the
moment we don't pass any option when making kernel snaps.
Otherwise core-initd itself defaults to "main server" on x86, but just
"main" on all other arches. Maybe we should enable "server" features for
"generic" kernel flavours
$ git grep virtio_blk
features/server/usr/lib/modules-load.d/ubuntu-core-server.conf:virtio_blk
When building initrd into the generic arm64 kernel snap, we should
enable feature "server" like we do on x86.
--
You received this bug notification because you are a member of Kernel
Packages, which
insecure W+X mapping is fixed in v5.13 series and in impish.
the changes to fix those will not be backported to hirsute, hence marking this
bug as fix released.
The kernel panics that is shown in the pastebin is unrelated to the
insecure W+X mapping.
** Changed in: linux-riscv (Ubuntu)
Public bug reported:
[ 15.446646] fu740-pcie e.pcie: invalid resource
[ 15.792898] L2CACHE: DataError @ 0x0008.04B0
[ 16.630923] da9063 0-0058: Chip variant not supported for DA9063
[ 16.746772] macb 1009.ethernet: GEM doesn't support hardware ptp.
[FAILED] Failed to
@cascardo it works
https://lists.ubuntu.com/archives/kernel-team/2021-August/123090.html
** Changed in: linux-riscv-5.11 (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux-riscv (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux-riscv-5.11 (Ubuntu)
** Changed in: linux-riscv (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: linux-riscv-5.11 (Ubuntu)
Status: In Progress => Fix Committed
** Also affects: linux-riscv (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux-riscv-5.11
lttng-modules 2.12.5-1ubuntu2~21.04.1 in hirsute-proposed unapproved
queue
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1932165
Title:
lttng-modules/2.12.2-1ubuntu1~20.04.2
- objcopy/strip changed in 2.36.1, not keeping file attributes of the
original file. Work around that in dh_strip to write to a temporary
file and cat'ing this to the original file to keep the original
attributes.
which is broken for setuid files.
** Also affects: dash (Ubuntu)
separately I'm not sure who/what/why stips setuid bits on file creation
through redirect.
is it like some kind of a CVE in bash/dash? kernel protection?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Based on https://elixir.bootlin.com/linux/latest/source/fs/inode.c#L1928
it seems that setuid and capabilities will be stipped, thus currently
our implementation of dh_strip causes to loose setuid and capabilities.
No idea why this is working with fakeroot when Rules-Requires-Root is set to
** Changed in: bash (Ubuntu)
Status: New => Invalid
** Changed in: dash (Ubuntu)
Status: New => Invalid
** Changed in: debhelper (Ubuntu)
Status: New => Triaged
** Changed in: debugedit (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: New
** Patch added: "chmod-reference.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938886/+attachment/5515876/+files/chmod-reference.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Patch removed: "chmod-reference.patch"
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1938886/+attachment/5515876/+files/chmod-reference.patch
** Patch added: "chmod-reference.patch"
Public bug reported:
linux-riscv-5.11 1015 panics on unmatched
[0.00] SBI specification v0.2 detected
[0.00] SBI implementation ID=0x1 Version=0x9
[0.00] SBI v0.2 TIME extension detected
[0.00] SBI v0.2 IPI extension detected
[0.00] SBI v0.2 RFENCE
** Package changed: ubuntu => linux-riscv-5.11 (Ubuntu)
--
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/1934548
Title:
RISC-V: Illegal instruction
Status in linux-riscv package in
*** This bug is a duplicate of bug 1934548 ***
https://bugs.launchpad.net/bugs/1934548
** This bug has been marked a duplicate of bug 1934548
RISC-V: Illegal instruction
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
https://people.canonical.com/~xnox/lp1934548/
findings published at above location. I am giving up at this point and
need to handover to someone else.
Is there a way to attach gdb over jtag to unmatched board whilst it is
attempting to boot?
Is there a way to analyze the vmlinuz image to figure
** Also affects: linux-hwe-5.13 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939287
Title:
dbgsym package is missing for
I was not expecting for focal/linux to change. This change was expected
to be done in impish/linux only.
How can I figure out why this was done in focal/linux?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
linux (5.4.0-87.98) focal; urgency=medium
* please drop virtualbox-guest-dkms virtualbox-guest-source (LP: #1933248)
- [Config] Disable virtualbox dkms build
Disabled do_dkms_vbox, because src:virtualbox got srued into Focal which no
longer provides virtualbox-guest-dkms
I fear/wonder
reading old modules...
MISS: vboxguest (ignored)
MISS: vboxsf (ignored)
In the current kerenl. So it appears that building with a dkms module got
dropped, and yet the guest modules from upstream code have not been built
either.
And i am able to reproduce
./fs/vboxsf is not available in v5.4 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/1933248
Title:
please drop virtualbox-guest-dkms virtualbox-guest-source
Status in linux
$ git describe 0fd1695766
v5.5-rc6-150-g0fd1695766
0fd1695766 fs: Add VirtualBox guest shared folder (vboxsf) support
** Tags added: block-proposed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://lists.ubuntu.com/archives/kernel-team/2021-September/124249.html
https://lists.ubuntu.com/archives/kernel-team/2021-September/124250.html
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => Triaged
--
You received this bug notification because you are a member of Kernel
Also I wonder if:
grep -a -m10 -E "\*" /dev/urandom 2>/dev/null | tr -dc 'a-z0-9' | cut
-c-6
can be implemented as:
cut -c-6 /proc/sys/kernel/random/uuid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
** Also affects: zfs-linux (Ubuntu Impish)
Importance: Critical
Assignee: Dimitri John Ledkov (xnox)
Status: Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs
** Description changed:
[Impact]
- * zfs fails reverting to a previous snapshot on reboot when selected on
+ * zfs fails reverting to a previous snapshot on reboot when selected on
grub
- * A miss-merge dropped initramfs hook changes, which result in failing
+ * A miss-merge dropped
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-4684/2021-10-12_16:41:27/impish_nvidia-
graphics-drivers-390_content.diff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Description changed:
+ [Impact]
+
+ * zfs fails reverting to a previous snapshot on reboot when selected on
+ grub
+
+ * A miss-merge dropped initramfs hook changes, which result in failing
+ to generate and use a new zfs uid.
+
+ [Test Plan]
+
+ * Create snapshot with $ zsysctl save
Our installer could stop finalrd before issuing shutdown too, as a
workaround.
--
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/1840122
Title:
System fails to reboot from live session or
we should check ordering of services for stop in a booted live session
(desktop / server / next-installer) and then figure out if we can add
additional dependencies to finalr.service (after) such that its stop is
ordered before everything else is stopped.
** Also affects: finalrd (Ubuntu)
I wonder if we need before= or after= umount.target
--
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/1840122
Title:
System fails to reboot from live session or ubiquity-dm -
Testing in https://bileto.ubuntu.com/#/ticket/4681
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1946642
Title:
nvidia-graphics-drivers-390 ftbfs on armhf
Status
That failed, missed one more place. Retesting.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1946642
Title:
nvidia-graphics-drivers-390 ftbfs on armhf
Status in
** Patch added: "lp1946642.patch"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1946642/+attachment/5531917/+files/lp1946642.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
To fix this on hwe-5.11 all of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930713 needs to be
backported. Given that hwe-5.11 will be rolled over to hwe-5.13 soon, I
am not sure if it is worth the effort.
** Changed in: linux-hwe-5.11 (Ubuntu Focal)
Status: Confirmed => Won't Fix
The bug was committed for the linux-hwe-5.13 kernel in proposed:
linux-image-5.13.0-17-generic-dbgsym_5.13.0-17.17~20.04.1_armhf.ddeb (937.5 MiB)
linux-image-5.13.0-17-generic-lpae-dbgsym_5.13.0-17.17~20.04.1_armhf.ddeb
(923.4 MiB)
1001 - 1100 of 1812 matches
Mail list logo
