** Changed in: linux (Ubuntu Mantic)
Status: Incomplete => Fix Committed
--
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/2021605
Title:
introduce do_lib_rust=true|false to
** Changed in: linux-lowlatency (Ubuntu Mantic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lowlatency in Ubuntu.
https://bugs.launchpad.net/bugs/2023007
Title:
kernel .config lowlatency
** Description changed:
+ [Impact]
+
+ Opened files reported in /proc/pid/map_files can be shows with the wrong
+ mount point using overlayfs with filesystem namspaces.
+
+ This incorrect behavior is fixed:
+
+ UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
+ map_files
+
@bluescreen-avenger thanks for testing, I'll send a proper SRU email to
apply this fix to the affected kernels!
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects:
Test kernel with the additional overlayfs fix applied:
https://kernel.ubuntu.com/~arighi/lp2016398/
--
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/2016398
Title:
stacked overlay file
This patch should fix this bug without breaking the behavior of
/proc/self/map_files.
Can you give it a try? I can also prepare a test kernel if you need.
** Patch added: "0001-UBUNTU-SAUCE-overlayfs-fix-reference-count-mismatch.patch"
** Changed in: linux (Ubuntu Mantic)
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/2023629
Title:
enable multi-gen LRU by default
Status in
** Description changed:
[Impact]
Kernels >= 6.1 have the option to use an alternative least-recently-used
(LRU) page reclaiming mechanism, called multi-gen LRU [1].
In short: the kernel used to maintain two LRU lists of "touched" pages:
the "active" and "inactive" lists. The
** Description changed:
[Impact]
Kernels >= 6.1 have the option to use an alternative least-recently-used
(LRU) page reclaiming mechanism, called multi-gen LRU [1].
In short: the kernel used to maintain two LRU lists of "touched" pages:
the "active" and "inactive" lists. The
** Description changed:
[Impact]
Kernels >= 6.1 have the option to use an alternative least-recently-used
(LRU) page reclaiming mechanism, called multi-gen LRU [1].
In short: the kernel used to maintain two LRU lists of "touched" pages:
the "active" and "inactive" lists. The
Public bug reported:
[Impact]
Kernels >= 6.1 have the option to use an alternative least-recently-used
(LRU) page reclaiming mechanism, called multi-gen LRU [1].
In short: the kernel used to maintain two LRU lists of "touched" pages:
the "active" and "inactive" lists. The former contains pages
Public bug reported:
[Impact]
The lowlatency kernel in Ubuntu is specifically designed to prioritize
high responsiveness, making it ideal for multimedia environments like
DAWs and audio processing platforms, as well as soft real-time
environments.
With the introduction of a real-time kernel, it
** Also affects: nvidia-graphics-drivers-450-server (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-450-server in
Ubuntu.
Public bug reported:
[Impact]
Provide a variable do_lib_rust=true|false in the kernel build system to
selectively enable the Rust packaging (linux-lib-rust) with specific
kernels and specific architectures.
Right now Rust should be enabled only in lunar and mantic and only on
amd64.
[Test
@zniavre in comment #6 I posted a patch for lunar, so it'll be applied
also there at some point.
--
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/2019869
Title:
And here's the debdiff for jammy. Same fix.
** Patch added: "nvidia-dkms-390-jammy-better-support-for-linux-6.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+attachment/5675616/+files/nvidia-dkms-390-jammy-better-support-for-linux-6.2.debdiff
--
Wrong debdiff, here's a new one cleaned up properly, ignore comment #5.
** Patch added: "nvidia-dkms-390-lunar-better-support-for-linux-6.2-v2.debdiff"
Attached debdiff contains the SRU patch to fix the same nvidia-dkms-390
build error with kernel 6.2 for lunar.
** Patch added: "nvidia-dkms-390-lunar-better-support-for-linux-6.2.debdiff"
** Also affects: nvidia-graphics-drivers-390 (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-450-server (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-470 (Ubuntu Lunar)
Importance:
Public bug reported:
[Impact]
At the moment we can't use the annotations scripts in focal, because we
are using the'|=' update operator for merging dicts, that has been
introduced with python 3.9.
Rewrite the code that is using this operator in a more portable way and
apply this change
Public bug reported:
[Impact]
After migrating to the new annotations-only model in jammy we introduced
a typo in debian/rules.d/4-checks.mk, that is triggered if we opt to not
migrate to the new model and still use the old configs+annotations.
[Test case]
With
Public bug reported:
[Impact]
Rust is only supported by amd64 at the moment, so there is no reason to
generate linux-lib-rust packages on the other architectures.
[Test case]
Simply build the kernel, generating all the deb packages.
[Fix]
Produce linux-lib-rust only on amd64.
[Regression
** Patch added: "nvidia-dkms-390-mantic-better-support-for-linux-6.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2019869/+attachment/5673352/+files/nvidia-dkms-390-mantic-better-support-for-linux-6.2.debdiff
--
You received this bug notification
Public bug reported:
[Impact]
Instead of disabling acpi support completely with nvidia-dkms-390, we
should try instead to see if it's possible to support it somehow.
[Fix]
This patch looks promising (even if it says huge hack in the comments...):
Better debdiff to backport only the patch required to support linux 6.2
(that is much better from an SRU perspective). Tested with positive
result in a VM both with 5.15 and the new hwe 6.2 kernels. So, please
ignore my previous comment.
** Patch added:
Moving jammy to the same version of the driver used in lunar allows to
use nvidia-dkms-390 both with the stock 5.15 kernel and the new hwe 6.2
(verified in a VM doing a simple test build).
** Patch added: "nvidia-dkms-390-jammy.debdiff"
** Also affects: nvidia-graphics-drivers-390 (Ubuntu Jammy)
Importance: Undecided
Status: New
--
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/2009142
Title:
** Description changed:
[Impact]
Starting with lunar we have introduced a new way to manage kernel
configs, unifying the duplicated information defined in the annotations
file + config chunks into an annotations-only model.
[Test case]
- An kernel build can be considered a
Public bug reported:
[Impact]
Starting with lunar we have introduced a new way to manage kernel
configs, unifying the duplicated information defined in the annotations
file + config chunks into an annotations-only model.
[Test case]
An kernel build can be considered a valid test case, in
** Description changed:
[Impact]
Commit f382fb0bcef4 ("block: remove legacy IO schedulers") introduced a
behavior change in the blkio throttle cgroup subsystem: IO statistics
are not reported anymore unless a throttling rule is explicitly defined,
because the current code only counts
** Description changed:
+ [Impact]
+
+ After enabling Rust support in the kernel we noticed an increased size
+ in linux-headers, because all the Rust libraries required to build out-
+ of-tree kernel modules are now included in linux-headers directly.
+
+ The increased size goes from ~30MB to
** Description changed:
+ [Impact]
+
+ Commit f382fb0bcef4 ("block: remove legacy IO schedulers") introduced a
+ behavior change in the blkio throttle cgroup subsystem: IO statistics
+ are not reported anymore unless a throttling rule is explicitly defined,
+ because the current code only counts
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-aws (Ubuntu)
** No longer affects: linux-azure (Ubuntu)
** No longer affects: linux-gcp (Ubuntu)
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
[Impact]
The current version of zfs-dkms available in lunar fails to build with
kernels >= 6.3.
[Test case]
$ apt install zfs-dkms
[Fix]
Resync with zfs version in Debian (2.1.1) and apply the usual Ubuntu
specific changes.
[Regression potential]
We may experience zfs
Potential upstream fix:
https://lore.kernel.org/lkml/20230401094708.77631-1-hanjinke@bytedance.com/
However this seems to partially restore the old behavior of cgroup v1,
because we still need to set io throttling limits in order to get the io
statistics.
We may need an additional fix like
Public bug reported:
[Impact]
We maintain custom LSM stacking and AppArmor SAUCE patches in our kernel
to provide additional features that are not available in the upstream
AppArmor.
We have experienced occasional bugs in the lunar kernel (specifically
with the environ.sh test) that can lead to
It might be worth to report this also upstream, apparently there was a
behavior change with the blkio controller in cgroup1 that happend at
some point between 5.15 and 5.19. I'll do more tests and will let you
know if I find anything relevant. Thanks for reporting this!
--
You received this bug
Same issue as LP: #2011748, that should be fixed by: a6d8a9c1e5fa
("arm64: efi: Use SMBIOS processor version to key off Ampere quirk")
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
The devlink command seems to print a warning that is considered as a
failure during this test:
435612:18:20 DEBUG| Running 'make run_tests -C net
TEST_PROGS=devlink_port_split.py TEST_GEN_PROGS='' TEST_CUSTOM_PROGS='''
14357 12:18:20 DEBUG|
Upstream commit 65b32f801bfb ("uapi: move IPPROTO_L2TP to in.h")
introduced this regression.
With that commit we moved IPPROTO_L2TP from a define to an enum,
breaking the macro that generates the module alias. This is the reason
why the modules are not loaded automatically anymore.
Upstream
Public bug reported:
lxc checkpoint-restore test case is failing with the following error (it
seems to be unable to connect to a counterpart, maybe it requires to
enable other components):
480010:27:55 INFO | START
ubuntu_lxc.lxc-test-checkpoint-restore
Public bug reported:
16637 zram01 5 TINFO: make xfs filesystem on /dev/zram3
16638 Filesystem must be larger than 300MB.
16639 Usage: mkfs.xfs
16640 /* blocksize */[-b size=num]
16641 /* config file */[-c options=xxx]
16642
Public bug reported:
212921:50:41 INFO | START
ubuntu_kvm_unit_tests.debug-wp-migration
ubuntu_kvm_unit_tests.debug-wp-migrationtimestamp=1679867441
timeout=1800localtime=Mar 26 21:50:41
213021:50:41 DEBUG| Persistent state client._record_indent now
It looks like the problem here is that with 6.2 (in lunar) the l2tp
modules are not loaded automatically, in 5.19 (kinetic) they were loaded
automatically without an explicit modprobe.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
After explicitly loading the modules the test completes correctly:
sudo modprobe l2tp_ip6
sudo modprobe l2tp_ip
sudo modprobe l2tp_eth
$ sudo ./tools/testing/selftests/net/l2tp.sh
TEST: IPv4 basic L2TP tunnel[ OK ]
TEST: IPv4 route through L2TP tunnel
Public bug reported:
[Impact]
nbd smoke test is triggering the following hung task timeout trace with
lunar/linux 6.2:
615 10:58:25 DEBUG| [stdout] [ 484.429923] INFO: task
systemd-udevd:16656 blocked for more than 120 seconds.
616 10:58:25 DEBUG|
Public bug reported:
[Impact]
Kernel selftest net:l2tp.sh is failing with the latest lunar/linux 6.2
kernel, the error is the following:
RTNETLINK answers: Protocol not supported
Using `bash -x` we can see that the last command executed is the
following:
ip -netns host-1 l2tp add tunnel
** Changed in: linux (Ubuntu Lunar)
Status: Incomplete => 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/2011748
Title:
lunar/linux 6.2 fails to boot on arm64
Public bug reported:
[Impact]
Refresh LSM stacking and AppArmor patch sets in linux 6.2. These patches
are required to properly support the new Apparmor features in Ubuntu.
[Test case]
Run Apparmor test cases included in our QA regression testing suite.
[Fix]
Patch set shared in the
** Description changed:
[Impact]
On certain bare metal arm64 boards the latest lunar/linux
6.2.0-17-generic fails to boot, the kernel gets stuck reporting the
following oops:
[ 72.043484] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 72.049571] rcu: 22-...0:
Public bug reported:
[Impact]
On certain bare metal arm64 boards the latest lunar/linux
6.2.0-17-generic fails to boot, the kernel gets stuck reporting the
following oops:
[ 72.043484] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
[ 72.049571] rcu: 22-...0: (30 GPs behind)
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
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
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
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
Public bug reported:
[Impact]
Try to boot the latest lunar/linux 6.2.0-16.16 on a ppc64 VM triggers
the following bug at boot:
event-sources: Unable to request interrupt 23 for /event-sources/hot-plug-events
WARNING: CPU: 0 PID: 1 at arch/powerpc/platforms/pseries/event_sources.c:26
** Description changed:
+ [Impact]
+
+ CONFIG_SERIAL_8250_MID=y is required to properly use the serial console
+ on some platforms that are using the "mid" serial driver (such as some
+ Intel SoC platforms).
+
+ The generic kernel should build this driver statically to make sure we
+ properly
** Also affects: linux (Ubuntu Lunar)
Importance: Critical
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/2009355
Title:
linux-libc-dev is no longer
I've applied this change to lunar. Next lunar 6.2 kernel will have
CONFIG_SERIAL_8250_MID=y.
--
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/2009283
Title:
linux:
It looks like this problem has been introduce by this commit:
a5ddd0de7d8b ("UBUNTU: [Packaging] install headers to debian/linux-libc-
dev directly")
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/lunar/commit/?id=a5ddd0de7d8b2159fc5f8df55527e0e447328953
It seems to include
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This was fixed during the regular rebase with upstream. We can close
this one now.
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: Fix Released
--
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/1989983
Title:
kinetic: apply new apparmor and
Public bug reported:
[Impact]
TDX guest attestation has been merged as SAUCE patches in the kinetic
kernel with the following commits:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/kinetic/commit/?h=master-next=285d6d8136ebadcee7fd6452b9e4223996a2a0af
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
Public bug reported:
[Impact]
nvidia-dkms-515-server fails to build with linux 6.2:
/var/lib/dkms/nvidia-srv/515.86.01/build/nvidia-drm/nvidia-drm-drv.c:245:21:
error: ‘struct drm_mode_config’ has no member named ‘fb_base’
245 | dev->mode_config.fb_base = 0;
| ^
debdiff in attach allows to use nvidia-dkms-470-server with linux 6.2.
** Patch added: "nvidia-470-server-support-linux-6.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470-server/+bug/2009254/+attachment/5651533/+files/nvidia-470-server-support-linux-6.2.debdiff
Public bug reported:
[Impact]
nvidia-dkms-470-server fails to build with linux 6.2:
/var/lib/dkms/nvidia-srv/470.161.03/build/nvidia/nv-acpi.c:84:19: error:
initialization of ‘void (*)(struct acpi_device *)’ from incompatible pointer
type ‘int (*)(struct acpi_device *, int)’
Public bug reported:
[Impact]
nvidia-dkms-450-server fails to build with linux 6.2, reporting the
following error:
/var/lib/dkms/nvidia-srv/450.216.04/build/nvidia/nv-acpi.c:84:19: error:
initialization of ‘void (*)(struct acpi_device *)’ from incompatible pointer
type ‘int (*)(struct
Public bug reported:
[Impact]
nvidia-dkms-515 fails to build with linux 6.2, reporting the following
error:
/var/lib/dkms/nvidia/515.86.01/build/nvidia-drm/nvidia-drm-drv.c:245:21: error:
‘struct drm_mode_config’ has no member named ‘fb_base’
245 | dev->mode_config.fb_base = 0;
|
debdiff in attach allows to use nvidia-dkms-510 with linux 6.2.
** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: nvidia-graphics-drivers-470 (Ubuntu Lunar)
** No longer affects: nvidia-graphics-drivers-470 (Ubuntu)
** Patch
** Summary changed:
- nvidia-dkms-390 FTBS with linux 6.2
+ nvidia-dkms-470 FTBS with linux 6.2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/2009246
Title:
Public bug reported:
[Impact]
nvidia-dkms-510 fails to build with linux 6.2, reporting the following
error:
/var/lib/dkms/nvidia/510.108.03/build/nvidia-drm/nvidia-drm-drv.c:245:21:
error: ‘struct drm_mode_config’ has no member named ‘fb_base’
245 | dev->mode_config.fb_base = 0;
|
debdiff in attach allows to use nvidia-dkms-470 with linux 6.2.
** Patch added: "nvidia-470-support-linux-6.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2009246/+attachment/5651505/+files/nvidia-470-support-linux-6.2.debdiff
--
You received this bug
** Also affects: nvidia-graphics-drivers-390 (Ubuntu Lunar)
Importance: Undecided
Status: Triaged
--
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/2009142
Public bug reported:
[Impact]
nvidia-dkms-470 fails to build with linux 6.2:
error: ‘struct drm_mode_config’ has no member named ‘fb_base’
244 | dev->mode_config.fb_base = 0;
| ^
[Fix]
Change the driver to support also the 6.2 kernel ABI.
[Test case]
With linux 6.2 installed, run:
debdiff in attatch allows to build nvidia-dkms-390 with linux 6.2.
** Patch added: "nvidia-390-support-linux-6.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2009142/+attachment/5651284/+files/nvidia-390-support-linux-6.2.debdiff
--
You received this
Public bug reported:
[Impact]
nvidia-dkms-390 fails to build with linux 6.2:
/var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:244:21: error:
‘struct drm_mode_config’ has no member named ‘fb_base’
244 | dev->mode_config.fb_base = 0;
| ^
[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
New debdiff on top of Debian zfs-linux 2.1.9-2. Smoke-tested in a local
VM. Thanks!
** Patch added: "zfs-linux-2.1.9-2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2008245/+attachment/5651251/+files/zfs-linux-2.1.9-2.debdiff
--
You received this bug notification because
debdiff in attach applied to zfs-2.1.9 from Debian seems to work fine on
linux 6.2
** Description changed:
[Impact]
The current version of zfs-dkms available in lunar fails to build with
kernels >= 6.2, reporting the following configure error:
- configure: error:
- *** None of
Public bug reported:
[Impact]
The current version of zfs-dkms available in lunar fails to build with
kernels >= 6.2, reporting the following configure error:
configure: error:
*** None of the expected "iops->get_acl()" interfaces were detected.
*** This may be because your
"hello world" test module:
+ Build the following "hello world" test module:
== hello_rust.rs ==
// SPDX-License-Identifier: GPL-2.0
//! Rust hello world example.
use kernel::prelude::*;
module! {
- type: HelloRust,
- name: "hello_rust"
lo_rust.rs ==
+
// SPDX-License-Identifier: GPL-2.0
//! Rust hello world example.
use kernel::prelude::*;
module! {
- type: RustMinimal,
- name: b"hello_rust",
- author: b"Andrea Righi ",
- description: b"Rust hello world example",
-
=
// SPDX-License-Identifier: GPL-2.0
//! Rust hello world example.
use kernel::prelude::*;
module! {
type: HelloRust,
name: "hello_rust",
author: "Andrea Righi ",
description: "Rust hello world example",
license: "GPL",
}
struc
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
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/1980484
Title:
temporarily disable CONFIG_X86_KERNEL_IBT
I performed a smoke test with v4l2loopback-dkms in jammy, everything
looks good.
Test case:
$ sudo apt install v4l2loopback-dkms
...
$ sudo modprobe v4l2loopback devices=1 video_nr=8 exclusive_caps=1
max_buffers=2
$ sudo v4l2loopback-ctl set-fps 60 /dev/video8
OK
$ sudo v4l2-ctl
Public bug reported:
[Impact]
dm-writeboost-dkms fails to build with linux 6.1 in lunar with the
following error(s):
/home/righiandr/src/dm-writeboost/src/dm-writeboost.h:506:46: error: ‘struct
dm_io_request’ has no member named ‘bi_op’; did you mean ‘bi_opf’?
506 | #define req_is_write(req)
debdiff in attach disables ACPI support with kernel >= 6.0 and it allows
to use this driver with the latest 6.1 kernel (this should be probably
considered a temporary workaround, until nvidia provides an updated
version of this driver with a proper fix).
** Patch added:
** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: nvidia-graphics-drivers-470 (Ubuntu)
** Also affects: nvidia-graphics-drivers-390 (Ubuntu Lunar)
Importance: Undecided
Status: New
** No longer affects:
Public bug reported:
[Impact]
Trying to install nvidia-dkms-390 with linux 6.1 in lunar produces the
following error:
error: ‘struct acpi_device’ has no member named ‘children’
[Test case]
$ sudo apt install nvidia-dkms-390
[Fix]
Support linux 6.1 ABI.
[Regression potential]
We may
I just tested autopkgtest and our kernel regression zfs testsuite
(ubuntu_zfs, ubuntu_zfs_fstest, ubuntu_zfs_smoke_test,
ubuntu_zfs_stress, ubuntu_zfs_xfs_generic) both with the new 5.19 kernel
and stock 5.15 in jammy. Everything looks good, no error. I'm trying to
figure out how to test the zsys
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: Confirmed
** Also affects: zfs-linux (Ubuntu Lunar)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux
I confirm that this fix
(https://lore.kernel.org/all/patch-1.thread-41c676.git-41c676c2d153.your-
ad-here.call-01675030179-ext-9637@work.hours/) applied to lunar/linux-
unstable seems to fix the initramfs boot problem, with this fix applied
we can restore the upstream zstd. Thanks!
--
You
debdiff in attach (that doesn't change anything, it's basically a resync
of the same version in kinetic, recompiled with the jammy toolchain).
With this applied I was able to successfully run ubuntu_zfs_smoke_test
and ubuntu_zfs_stress both on 5.15 and 5.19.
** Patch added:
Public bug reported:
[Impact]
zfs-dkms fails to build on jammy with the latest linux hwe 5.19:
*** ZFS Version: zfs-2.1.4-0ubuntu0.1
*** Compatible Kernels: 3.10 - 5.17
[Test case]
$ sudo apt install zfs-dkms
[Fix]
The most reliable fix is probably to move to the same version that is
new debdiff for jammy (v2) with the proper changelog entry.
** Patch added: "bcmwl-support-5.19-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1981968/+attachment/5640985/+files/bcmwl-support-5.19-v2.debdiff
--
You received this bug notification because you are a member of
Opened LP: #2002634 for the other issue (kernel warning) in kinetic.
--
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/1981968
Title:
bcmwl fails to build on the latest kinetic kernel 5.19
debdiff in attach allows to properly support kernel 5.19.
** Patch added: "kinetic-bcmwl-properly-support-linux-5.19.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/2002634/+attachment/5640977/+files/kinetic-bcmwl-properly-support-linux-5.19.debdiff
--
You received this bug
101 - 200 of 689 matches
Mail list logo
