Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
New debdiff in attach, that also includes the fix for a potential data
corruption with zfs-2.1.1 (https://github.com/openzfs/zfs/issues/12762).
** Bug watch added: github.com/openzfs/zfs/issues #12762
https://github.com/openzfs/zfs/issues/12762
** Patch added: "zfs-update-to-2.1.1-v2.debdiff"
Moving to Debian zfs 2.1.1 + applying the debdiff in attach seems to fix
the problem.
** Patch added: "zfs-update-to-2.1.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1954676/+attachment/5547343/+files/zfs-update-to-2.1.1.debdiff
** Description changed:
+ [Impact]
+
Public bug reported:
Installing zfs-dkms seems to trigger a soft lockup issue as soon as
zfs.ko is loaded. When the soft lockup happens the system isn't
reachable anymore via ssh and on the console we can see some exlicit rcu
stall warnings.
** Affects: zfs-linux (Ubuntu)
Importance: Undecid
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
I was waiting for a review / acknowledge from the upstream maintainer,
before applying this fix and unfortunately I didn't receive that in time
to push this fix in 5.13.0-22.
But now I got the ok from the maintainer, so I just sent the SRU fix to
the ubuntu kernel team mailing list:
https://list
** Description changed:
+ [Impact]
+
+ On some thinkpads we may get a kernel panic at boot, because the
+ elantech driver (trakcpad) can trigger out-of-bounds access in the
+ stack.
+
+ [Test case]
+
+ Simply boot the kernel on one of the affected systems (e.g., Thinkpad
+ E14 Gen2).
+
+ [Fix]
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
It looks like this dkms is actually needed so ignore my previous
comment.
** Description changed:
+ [Impact]
+
+ backport-iwlwifi-dkms fails to build on the latest jammy kernel 5.15:
+
CC [M]
/tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.o
In file included from
/
Unfortunately I don't have control on the generation of the ISOs, the
best thing I can do is to set this bug to critical and ping people...
** Changed in: linux (Ubuntu Impish)
Importance: High => Critical
** Changed in: linux (Ubuntu Jammy)
Importance: High => Critical
--
You received th
** Also affects: bbswitch (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Jammy)
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
Public bug reported:
CC [M] /var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.o
/var/lib/dkms/ddcci/0.4.1/build/ddcci/ddcci.c:1295:27: error: initialization of
‘void (*)(struct device *)’ from incompatible pointer type ‘int (*)(struct
device *)’ [-Werror=incompatible-pointer-types]
1295 |
Attached debdiff can fix the build error on armhf and ppc64el.
** Patch added: "bbswitch-fix-build-error-on-armhf-and-ppc64el.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951583/+attachment/5542102/+files/bbswitch-fix-build-error-on-armhf-and-ppc64el.debdiff
--
You received
Public bug reported:
It looks like bbswitch is using acpi_bus_get_device() on any
architectures, but this function is not available on armhf or ppc64el:
CC [M] /var/lib/dkms/bbswitch/0.8/build/bbswitch.o
/var/lib/dkms/bbswitch/0.8/build/bbswitch.c: In function ‘bbswitch_off’:
/var/lib/dkms/bbs
Actually... is this dkms really needed in jammy?
Now that the build is fixed I just noticed that I get this error if I
try to install it on a 5.15 kernel:
iwlwifi.ko:
Running module version sanity check.
Module has been obsoleted due to being included
in kernel 5.14.0. We will avoid installing
Debdiff in attach seems to resolve the problem (tested on jammy with the
latest 5.15 from -proposed).
** Patch added: "iwlwifi-fix-build-error-with-kernel-5.15.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951580/+attachment/5542079/+files/iwlwifi-fix-build-error-with-kernel-5
https://gitlab.com/vicamo/backport-iwlwifi-dkms/-/issues/12 <- also
filed an issue here
--
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/1951580
Title:
backport-iwlwifi-dkms fails to build
Public bug reported:
CC [M] /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.o
In file included from
/tmp/backport-iwlwifi-dkms/backport-include/asm-generic/bug.h:3,
from ./arch/x86/include/asm/bug.h:84,
from ./include/linux/bug.h:5,
** Description changed:
- Starting with the following commit, upstream kernel is enabling Intel IOMMU
related options by default:
-
- 792fb43ce2c9 ("iommu/vt-d: Enable Intel IOMMU scalable mode by default")
-
- We should follow upstream direction enabling INTEL_IOMMU_DEFAULT_ON and
CO
Public bug reported:
Starting with the following commit, upstream kernel is enabling Intel
IOMMU related options by default:
792fb43ce2c9 ("iommu/vt-d: Enable Intel IOMMU scalable mode by
default")
We should follow upstream direction enabling
CONFIG_INTEL_IOMMU_DEFAULT_ON and
CONFIG_INTEL_IOMMU
debdiff against Debian iproute2 5.15.0-1 (re-applied Ubuntu Fan driver).
v2: added this tracking bug to the changelog entry.
** Patch added: "iproute2-update-to-5.15-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1951390/+attachment/5541717/+files/iproute2-update-to-5.15-
** Patch added: "iproute2-update-to-5.15.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1951390/+attachment/5541716/+files/iproute2-update-to-5.15.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ub
** Also affects: iproute2 (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1951390
Title:
upd
Public bug reported:
Kernel 5.15 requires iproute2 at least v5.14 to properly support IPv6
In-situ OAM (IOAM6). This lack of support is also triggering the
following kernel selftest failure:
# selftests: net: ioam6.sh
# SKIP: iproute2 too old, missing ioam command
not ok 1 selftests: net: ioam
@manolo I asked around and it looks like ISOs are updated only in there
are really critical bugs (but to be 100% sure you should try to ask the
Lubuntu community directly). In this case I guess the only workaround
(if disabling the pad, installing and upgrading the kernel doesn't work)
is to instal
@manolo once the fix is applied to the generic kernel all the other
derivatives will be updated as well. About the ISO I need to check, it'd
make sense to update that as well, since there's a critical boot problem
in this case.
--
You received this bug notification because you are a member of Ker
buntu Jammy)
Importance: High
Status: Confirmed
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Andrea Righi (arighi)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
Uploaded another test kernel (5.13.0-22.22+arighi2020+1):
https://kernel.ubuntu.com/~arighi/lp1945590/
However, looking more at the KASAN error, it seems that the reported
error is actually an out-of-bound read... so that still doesn't explain
the stack corruption, but it's still something th
@marco-098 sorry I had to disable zfs, because it doesn't build
correctly with CONFIG_KASAN enabled.
However, thanks to @randombop dmesg.txt now I think I see a potential
stack corruption in the elantech code!
IIRC param[] in elantech_cahnge_report_id must be at least 3 bytes,
because elantech_re
Alright, I checked with Chris Chiu, he confirms that all the tests
kernels that he provided don't have -fcf-protection=none. However, we
still don't think that touching this compiler option is a proper fix for
the bug, more likely it's just hiding the problem, so we could still
have a potential sta
Without having access to the hardware it's quite hard to figure out what
is happening exactly, I wasn't able to reproduce the issue in any other
test machines.
I'm wondering if this bug is still happening with a 5.15 kernel (linux
5.15 is available here ppa:canonical-kernel-team/bootstrap). If we
Public bug reported:
[Impact]
KFENCE devs are changing CONFIG_KFENCE_STATIC_KEYS to be disabled by
default, because it's introducing more problems than benefits:
https://lore.kernel.org/all/20211019102524.2807208-2-el...@google.com/T/#u
This also seems to trigger QEMU bugs during the systemd au
** Description changed:
+ [Impact]
+
+ It is possible to trigger a kernel panic with the latest impish kernel
+ running systemd autopkgtest using --enable-kvm with the test instances
+ created by systemd during the autotest. The panic happens in the host,
+ not in the guest VM executed by systemd
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Hirsute)
Status: Incomplete => Co
** Description changed:
[Impact]
"UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file
while vmscan is active" has been applied to fix a page leaking issue.
However a slightly different fix has been applied upstream:
9a24ce5b66f9c8190d63b15f4473600db4935f1f ca
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Import
Public bug reported:
[Impact]
"UBUNTU: SAUCE: cachefiles: Page leaking in cachefiles_read_backing_file
while vmscan is active" has been applied to fix a page leaking issue.
However a slightly different fix has been applied upstream:
9a24ce5b66f9c8190d63b15f4473600db4935f1f cachefiles: Fix page
https://lore.kernel.org/lkml/YW6N2qXpBU3oc50q@arighi-desktop/T/#u
^ Potential upstream fix (I tested with this one applied and I couldn't
break the kernel), let's wait for a feedback from the LKML, if that fix
is reasonable I'll send a proper SRU email to apply it to the Ubuntu
kernel.
--
You re
Additional information about this (from the memory dump that I was able
to get):
crash> gdb list *(wb_timer_fn+0x44)
0x991abcc4 is in wb_timer_fn (/build/impish/block/blk-wbt.c:237).
235 static int latency_exceeded(struct rq_wb *rwb, struct blk_rq_stat *stat)
236 {
237
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Impish)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andrea Righi (arighi)
** Changed in: linux (Ubuntu Impish)
Assignee: (u
Public bug reported:
I can trigger the following kernel panic with the latest impish kernel
5.13.0-19-generic, running systemd autopkgtest using --enable-kvm for
the instances created by systemd to run the autotest:
[ 119.987108] BUG: kernel NULL pointer dereference, address: 0098
[
** Description changed:
+ [Impact]
+
+ Impish is missing the nvidia server drivers.
+
+ [Test case]
+
$ 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
Versio
** Also affects: linux-restricted-modules (Ubuntu Impish)
Importance: High
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-restricted-modules in Ubuntu.
https://bugs.l
You just need to install linux and linux-modules (sorry I wasn't very
clear). But it looks like my patch didn't make any difference.
I'll investigate a bit more. Thanks for testing!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Test kernel is available here, if you want to give it a try:
https://kernel.ubuntu.com/~arighi/lp1945590/
Thanks!
** Changed in: linux (Ubuntu Impish)
Assignee: (unassigned) => Andrea Righi (arighi)
** Changed in: linux (Ubuntu Impish)
Importance: Undecided => High
--
You re
Hm.. it's not trivial to revert that commit, because it depends on other
subsystem changes. I was thinking that we may actually corrupt the stack
because elantech_create_smbus() is using too much stack. How about
allocating that i2c_props array in the heap. See the patch in attach.
** Patch added:
Hm.. it's not trivial to revert that commit, because it depends on other
subsystem changes. I was thinking that we may actually corrupt the stack
because elantech_create_smbus() is using too much stack. How about
allocating that i2c_props array in the heap. See the patch in attach.
** Patch added:
Looking at the oops it seems that the stack gets corrupted inside
elantech_change_report_id(), that is defined in
drivers/input/mouse/elantech.c.
According to Stephan it seems that 5.11 is the last kernel that seems to
work.
If we look at the changes between 5.11 and 5.13 that are touching
driver
OK, so at least we know that it's a mainline issue. I'll investigate a
bit and will keep you informed. Thank you so much for all the tests!
--
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/19
Maybe disable secure boot from the BIOS? Test kernels can't be signed,
so I guess that's the only way...
--
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/1945590
Title:
Thinkpad E14 Gen2:
Update: apparently CONFIG_KFENCE can only reduce the probability to
trigger the bug, so it's not a reliable fix. According to all the traces
that we got the soft lockup is always happening to any SLUB allocation
function (__kmalloc, kmem_cache_alloc, and similar), and the instruction
pointer is on
ok, another interesting test to do would be to see what happens with a
mainline kernel (just to see if the problem is a mainline issue or if
it's limited to the Ubuntu kernel).
Can you try to do a test with this kernel?
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.19/
^ This is basically
@Pietro, thanks for reporting this.
Can you do a test with the kernel that is currently in impish-proposed
(5.13.0-18.18)? See https://wiki.ubuntu.com/Testing/EnableProposed on
how to enable proposed (for this you need to upgrade from 21.04, then
enable proposed, install 5.13.0-18.18, then reboot)
Update: disabling CONFIG_KFENCE_STATIC_KEYS prevents this problem from
happening, so we may consider to disable this option as a temporary
workaround, or even disable KFENCE entirely, since it's more like a
debugging feature (low-overhead out-of-bounds / use-after-free /
invalid-free memory detecto
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: 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/1836694
Title:
memcg_test_3 from controllers in LT
Public bug reported:
Found this when running the systemd autopkgtest on linux-aws
5.13.0-1004.5 (apparently it seems to affect nested kvm only):
systemd-testsuite login: [ 70.235559] int3: [#1] SMP NOPTI
[ 70.237824] CPU: 0 PID: 326 Comm: systemd-journal Not tainted
5.13.0-1004-aws #5-U
** Patch added: "sysdig-fix-arm64-build.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.6/+bug/1945757/+attachment/5529831/+files/sysdig-fix-arm64-build.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5
** Patch added: "sysdig-fix-arm64-build.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.6/+bug/1945757/+attachment/5529832/+files/sysdig-fix-arm64-build.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5
Public bug reported:
[Impact]
sysdig-dkms fails to build on arm64 with the latest impish kernel
(5.13):
/var/lib/dkms/sysdig/0.27.1/build/main.c:1942:28: error: ‘SYSCALL_TABLE_ID0’
undeclared (first use in this function); did you mean ‘SYSCALL_TABLE_SIZE’?
1942 | table_index = id - SYS
Public bug reported:
81727 04:16:04 INFO | START
ubuntu_ltp_syscalls.perf_event_open02ubuntu_ltp_syscalls.perf_event_open02
timestamp=1632284164timeout=900localtime=Sep 22 04:16:04
81728 04:16:04 DEBUG| Persistent state
client._recor
Public bug reported:
This option will disable uprivileged BPF by default. It can be reenabled,
though, as it uses the new value 2 for the kernel.unprivileged_bpf_disabled
sysctl. That value disables it, but allows the sysctl knob to be set back to 0.
This allows sysadmins to enable unprivil
Public bug reported:
ubuntu_nbd_smoke_test seems to fail on small instances when tested in
any cloud:
355 NBD device /dev/nbd0 created
356 found nbd export
357 NBD exports found:
358 test
359 starting client with NBD device /dev/nbd0
360
We likely need this commit to fix this build issue, but it's not trivial
to backport it, we are going to hint the test for now:
commit 4d1b62986125b6de596c98310543652a7892e097
Author: Alexei Starovoitov
Date: Thu May 13 17:36:20 2021 -0700
selftests/bpf: Convert few tests to light skeleton
Public bug reported:
12886 Warning: Kernel ABI header at
'tools/include/uapi/linux/if_link.h' differs from latest version at
'include/uapi/linux/if_link.h'
12887 libbpf: elf: skipping unrecognized data
section(5) .rodata.str1.1
Public bug reported:
5.13 with KCSAN enabled reports the following bug on Xen-based
instances.
Maybe it's worth investigating to determine if they are false positives
or not, for now, I think we can just disable CONFIG_KCSAN to prevent
this boot problem:
200 01:51:29
Public bug reported:
We should consider to increase the timeout for this test, because in
some slow systems it may fail with the following error:
16:25:59 DEBUG| [stdout] tag=cve-2018-101 stime=1631117534 dur=0
exit=exited stat=0 core=no cu=0 cs=0
16:25:59 DEBUG| [stdout] startup='Wed Sep 8
Public bug reported:
6:28:16 DEBUG| [stdout] tag=af_alg06 stime=1631118362 dur=0 exit=exited stat=0
core=no cu=0 cs=0
16:28:16 DEBUG| [stdout] startup='Wed Sep 8 16:26:02 2021'
16:28:16 DEBUG| [stdout] tst_test.c:1353: TINFO: Timeout per run is 0h 05m 00s
16:28:16 DEBUG| [stdout] ../../../includ
Public bug reported:
This is an old error that doesn't seem to happen if we run this test
isolated from the others, maybe the reason is that something is not
cleaned up properly (we should probably consider to exclude this test
from the net tests and run it isolated as a separate test):
1
Public bug reported:
I think we need to fix the test itself (not really a kernel issue
probably), but worth investigating:
07:35:14 DEBUG| [stdout] mount: /dev/cpuctl: cpuctl already mounted or mount
point busy.
07:35:14 DEBUG| [stdout] cpuctl_test_fj1 TFAIL : ltpapicmd.c:188: failed
to
Public bug reported:
Some times this test can fail with the following error:
06:20:37 DEBUG| [stdout] tag=isofs stime=1631081630 dur=0 exit=exited stat=32
core=no cu=1 cs=1
...
06:20:37 DEBUG| [stdout] Test timeouted, sending SIGKILL!
06:20:37 DEBUG| [stdout] tst_test.c:1399: TINFO: If you are r
Public bug reported:
ubuntu_ltp cpuhotplug03 test is failing with the following error on
arm64:
cpuhotplug03 1 TFAIL: No cpuhotplug_do_spin_loop processes found on
CPU1
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
Public bug reported:
ubuntu_ltp.kernel_misc test failure on impish linux 5.13:
STARTubuntu_ltp.kernel_miscubuntu_ltp.kernel_misc
02:33:58 DEBUG| [stdout] cpufreq_boost1 TFAIL : cpufreq_boost.c:189:
compare time spent with and without boost (-2%)
...
384612 Traceb
** No longer affects: linux
** 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.
https://bugs.launchpad.net/bugs/1937773
Title:
WARNING: CPU
** Description changed:
+ [Impact]
+
+ lttng-modules-dkms is reporting many build errors with linux-hwe-5.11,
+ because of many kernel ABI changes.
+
+ [Fix]
+
+ Backporting the individual patches to fix all the build errors would be
+ a lot of work and the risk to introduce regressions would b
Here's a patch that should fix the build issue on s390x (or more in
general on all systems that don't have USB support enabled).
** Patch added: "evdi-support-usbless-systems.debdiff"
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1932163/+attachment/5512245/+files/evdi-support-usbless-sy
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
New debdiff for the backport from impish to focal in attach.
** Patch added: "lttng-modules-backport-from-impish.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1932165/+attachment/5511922/+files/lttng-modules-backport-from-impish.debdiff
--
You received this bug notifi
Bad debdiff, ignore it for now, new debdiff incoming.
--
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 ADT test failure with l
I've just created a ppa with the latest lttng-modules-dkms from impish
recompiled for focal
https://launchpad.net/~arighi/+archive/ubuntu/lttng/
And tested (ubuntu_lttng_smoke_test) with the 5.11 hwe and 5.4 kernels.
Everything looks good with both kernels.
The debdiff in attach (against the imp
** 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.
https://bugs.launchpad.net/bugs/1936475
Title:
ipv6: fix 'disable_policy' for forwarded
*** This bug is a duplicate of bug 1935807 ***
https://bugs.launchpad.net/bugs/1935807
** This bug has been marked a duplicate of bug 1935807
Impish update: v5.13.1 upstream stable release
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The up
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Debdiff in attach seems to fix the build errors w/ the guest drivers.
** Patch added: "vbox-guest-support-linux-5.13.debdiff"
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1929193/+attachment/5506486/+files/vbox-guest-support-linux-5.13.debdiff
--
You received this bug notificati
** 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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1927692
Title:
AWS: out of entropy on Graviton 2 inst
# [73] event trigger - test synthetic_events syntax parser [PASS]
# [74] event trigger - test synthetic_events syntax parser errors [PASS]
^ test is passing now.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notificatio
** Attachment added: "make.log"
https://bugs.launchpad.net/bugs/1929192/+attachment/5499200/+files/make.log
--
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/1929192
** Attachment added: "make.log"
https://bugs.launchpad.net/bugs/1929192/+attachment/5499198/+files/make.log
--
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/1929192
** Attachment added: "make.log"
https://bugs.launchpad.net/bugs/1929192/+attachment/5499199/+files/make.log
--
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/1929192
Public bug reported:
This is a scripted bug report about ADT failures while running nvidia-
graphics-drivers-390 tests for linux-unstable/5.13.0-3.3 on impish.
Whether this is caused by the dep8 tests of the tested source or the
kernel has yet to be determined.
Testing failed on:
amd64:
http
** Summary changed:
- properly tear down KVM PV features on hibernate
+ kvm: properly tear down PV features on hibernate
** Description changed:
[Impact]
In LP: #1918694 we applied a fix and a workaround to solve the
hibernation issues on c5.18xlarge. The workaround was in the form of a
** Also affects: linux-aws (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
[Impact]
In L
** Description changed:
[Impact]
In LP: #1918694 we applied a fix and a workaround to solve the
hibernation issues on c5.18xlarge. The workaround was in the form of a
SAUCE patch:
"UBUNTU: SAUCE: aws: kvm: double the size of hv_clock_boot"
- It looks like we can replace this w
** Summary changed:
- out of entropy on Graviton 2 instances types (mg6.*)
+ AWS: out of entropy on Graviton 2 instances types (mg6.*)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/19
** Description changed:
[Impact]
AWS Graviton 2 instances do not have enough entropy available at boot,
so any task that require entropy (even reading few bytes from
/dev/random) will be stuck forever.
[Fix]
The proper fix for this problem is to correctly refill the entropy po
Public bug reported:
[Impact]
AWS Graviton 2 instances do not have enough entropy available at boot,
so any task that require entropy (even reading few bytes from
/dev/random) will be stuck forever.
[Fix]
The proper fix for this problem is to correctly refill the entropy pool
with some real ran
Public bug reported:
[Impact]
The synthetic_events ftrace test is failing in 5.11:
01:58:54 DEBUG| [stdout] # [68] event trigger - test synthetic_events
syntax parser errors [FAIL]
This happens because the synthetic_event parser/syntax has been reworked
in 5.12 and the selftest has been al
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
301 - 400 of 689 matches
Mail list logo
