eam (canonical-kernel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
*
eam (canonical-kernel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
--
You r
** Changed in: ubuntu-kernel-tests
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.net/bugs/1812845
Ti
** Changed in: zfs-linux (Ubuntu Xenial)
Status: In Progress => Invalid
** Changed in: zfs-linux (Ubuntu Bionic)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bug
I've tried to reproduce this problem running the following commands:
ubuntu@focal:~$ fallocate -l 8G /home/ubuntu/disk.img
ubuntu@focal:~$ sudo zpool create pool1 /home/ubuntu/disk.img
ubuntu@focal:~$ sudo zfs create -o encryption=on -o keyformat=passphrase
pool1/pool1
Enter passphrase:
Re-enter
Steps used to verify the fix (both in focal and groovy):
$ fallocate -l 8G /home/ubuntu/disk.img
$ sudo zpool create pool /home/ubuntu/disk.img
$ for i in {1..20}; do sudo zfs create pool/ds$i; done
$ sudo zfs unmount pool/ds20
$ sudo zfs mount -a & sudo zfs mount -a &
[1] 1964
[2] 1965
ubuntu@gr
Hi @seth-arnold,
adding some details to this bug:
dn->dn_type = 19 = DMU_OT_PLAIN_FILE_CONTENTS
dn->dn_type = 20 = DMU_OT_DIRECTORY_CONTENTS
So they look correct, they seem to be just plain files and directories.
However, the specific object that is causing the panic seems to have
dn_type=32
I just noticed the bug on github that also mentions about potential data
corruption. It looks like we need to recompile zfs with --enable-debug.
I'll try to produce a debug package with that.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I've uploaded the latest version of zfs with debugging enabled (--enable-debug)
in this ppa:
https://launchpad.net/~arighi/+archive/ubuntu/zfs-linux
sudo add-apt-repository ppa:arighi/zfs-linux
sudo apt-get update
sudo apt-get install zfs-dkms
It'd be interesting to repeat the test using this ve
Public bug reported:
[Impact]
On hibernation xen-netfront is setting the device state on the xenbus to
"Closing" and then it's waiting for the backend state to acknowledge
that state (with a timeout). However, if the device is already in the
state "Closed" this opteration will always hit the time
This time I don't see any error or panic in `journalctl -b` and
apparently everything is fine according to smartctl, so it looks like we
are not getting any obvious I/O error at the moment.
IIUC you have done already a `zpool scrub` and that also didn't report
any error, so apparently the zfs data
Public bug reported:
[Impact]
nvidia-graphics-drivers-390 fails to build against linux 5.10:
ERROR (dkms apport): kernel package linux-headers-5.10.0-6-generic is not
supported
Error! Bad return status for module build on kernel: 5.10.0-6-generic (x86_64)
Consult /var/lib/dkms/nvidia/390.138/bu
make.log in attach.
** Attachment added: "make.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1908099/+attachment/5443483/+files/make.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics
debdiff that fixes the 5.10 build errors reported in attach.
** Patch added: "hirsute-nvidia-dkms-390.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1908099/+attachment/5443484/+files/hirsute-nvidia-dkms-390.debdiff
--
You received this bug notification b
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Andrea Righi (arighi)
--
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/1887727
Title:
Permission denied opening f
It doesn't seem to be a specific zfs issue, I can reproduce this
behavior on any filesystem apparently. It might be caused by a change in
the VFS layer, I'll keep investigating.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in
This new behavior is enforced by /proc/sys/fs/protected_regular, a new
sysctl introduced by commit 30aba6656f61ed44cba445a3c0d38b296fa9e8f5
("namei: allow restricted O_CREAT of FIFOs and regular files").
The default behavior is to make data spoofing attacks harder,
disallowing the open of files no
** Changed in: zfs-linux (Ubuntu)
Status: New => Invalid
--
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/1887727
Title:
Permission denied opening file in a directory with a sti
I'm trying to reproduce the problem, but the zpool is always imported
correctly for me also at boot. How does your /etc/crypttab look like?
And zpool list -v? Thanks.
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Andrea Righi (arighi)
--
You received this bug noti
*** This bug is a duplicate of bug 1841377 ***
https://bugs.launchpad.net/bugs/1841377
** This bug has been marked a duplicate of bug 1841377
package zfsutils-linux 0.8.1-1ubuntu9 failed to install/upgrade: installed
zfsutils-linux package post-installation script subprocess returned error
It looks like this issue has been happening multiple times. Apparently
it doesn't happen if we try to update a clean install. And the common
denominator seems to be that lxd is installed and some containers are
running.
So, I've tried the following:
- setup a bionic VM with an encrypted storage:
Setting the status as "won't fix" for now, because I can't reproduce the
problem. If it happens again, please re-open the bug. Thanks.
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which
*** This bug is a duplicate of bug 1841377 ***
https://bugs.launchpad.net/bugs/1841377
** This bug has been marked a duplicate of bug 1841377
package zfsutils-linux 0.8.1-1ubuntu9 failed to install/upgrade: installed
zfsutils-linux package post-installation script subprocess returned error
*** This bug is a duplicate of bug 1841377 ***
https://bugs.launchpad.net/bugs/1841377
** This bug has been marked a duplicate of bug 1841377
package zfsutils-linux 0.8.1-1ubuntu9 failed to install/upgrade: installed
zfsutils-linux package post-installation script subprocess returned error
** Changed in: zfs-linux (Ubuntu)
Status: New => Confirmed
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Wishlist
--
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/
*** This bug is a duplicate of bug 1841377 ***
https://bugs.launchpad.net/bugs/1841377
Possibly also a duplicate of 1841377.
** This bug has been marked a duplicate of bug 1841377
package zfsutils-linux 0.8.1-1ubuntu9 failed to install/upgrade: installed
zfsutils-linux package post-instal
If I'm not wrong ZFS on root support has been introduced officially from
19.10 (eoan). I'm not sure if this one is still relevant, but with 20.04
I can't reproduce any errors/issues using ZFS as root and zfs-import-
cache.service is working just fine.
If you are still experiencing this problem, ca
Isn't this the expected behavior? In order to show the boot menu in grub
we need to set GRUB_TIMEOUT_STYLE / GRUB_TIMEOUT in /etc/default/grub
and run update-grub. Am I missing something?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Andrea Righi (arighi)
--
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/1881747
Title:
cephadm does not work with
I've tried to reproduce the problem on a VM (that uses ZFS as rootfs)
setting up a single-node ceph cluster, but OSD is coming up correctly:
$ sudo ceph -s | grep osd
osd: 1 osds: 1 up (since 50m), 1 in (since 59m)
Could you provide more details about your particular ceph configuration
/ infr
BTW, how did you install ceph-ansible? I can't find a 20.04 package in
the ansible ppa.
--
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/1881747
Title:
cephadm does not work with zfs r
I was pretty much following this simple tutorial:
http://prashplus.blogspot.com/2018/01/ceph-single-node-setup-ubuntu.html
I'll try to add docker and ceph-ansible to the equation and see if I can
reproduce it.
** Changed in: zfs-linux (Ubuntu)
Status: New => In Progress
--
You received t
Public bug reported:
[Impact]
SRU test ubuntu_ltp_syscalls is reporting the following message:
11:52:03 DEBUG| [stdout] ioctl_loop07.c:62: FAIL: /sys/block/loop4/size != 1024
got 2048
11:52:03 DEBUG| [stdout] ioctl_loop07.c:63: PASS:
/sys/block/loop4/loop/sizelimit = 524288
11:52:03 DEBUG| [st
** Changed in: linux-aws (Ubuntu)
Assignee: (unassigned) => Andrea Righi (arighi)
--
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/1896604
Title:
Groovy kernel (5.8.0-1004-
Adding some details about this issue. It looks like the real problem is
the serial driver, in fact with a 5.4 kernel we can see the following in
dmesg:
[4.991325] :16:00.0: ttyS0 at MMIO 0xc5a0 (irq = 85,
base_baud = 115200) is a 16550A
With the 5.8 kernel we don't see any message at
The reason of this problem is that in 5.8 the default amount of nr_uarts
has been changed from 4 to 32. This is causing ttyS0 to be remapped to
ttyS4, breaking the user-space.
The solution is to set back the number of UARTS to 4. I tried to boot
the kernel adding 8250.nr_uarts=4 to the kernel boot
** Description changed:
+ [Impact]
+
+ Starting with kernel 5.8 the default nr_uarts has been changed from 4 to
+ 2 for amd64, but this seems to affect i3.metal instances in AWS, because
+ ttyS0 is now remapped to ttyS4 and this is breaking tools like cloud-
+ init (and probably something else).
Public bug reported:
[Impact]
During our AWS testing we were experiencing deadlocks on hibernate across all
Xen instance types.
The trace was showing that the system was stuck in xennet_remove():
[ 358.109087] Freezing of tasks failed after 20.006 seconds (1 tasks refusing
to freeze, wq_busy=
Public bug reported:
[Impact]
With hardware dirty bit management enabled calling pte_wrprotect() on a
dirty PTE will clean the dirty state without flushing the content of the
page to the backing store.
[Test case]
Bug reported by Amazon, a specific test case is not provided. This
problem has be
** Changed in: linux-aws (Ubuntu Bionic)
Assignee: (unassigned) => Andrea Righi (arighi)
** Changed in: linux-aws (Ubuntu Focal)
Assignee: (unassigned) => Andrea Righi (arighi)
** Changed in: linux-aws (Ubuntu Groovy)
Assignee: (unassigned) => Andrea Righi (arighi)
** C
Public bug reported:
[Impact]
AWS has seen some customers reporting networking performance degradation
after they upgraded their Ubuntu instanceses. This regression is highly
impacting customers who are using MTU=9000 (which is the default in
EC2).
[Test case]
Bug reproduced internally in AWS (
** Also affects: linux-aws (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: linux-aws (Ubuntu Bio
New debdiff that prevents building UVM w/ Linux 5.10 (thanks
@albertomilone) and with a refreshed version of
buildfix_kernel_5.10.patch that should prevent a potential memory leak
due to the missing .gem_free_object in 5.10.
** Patch added: "hirsute-nvidia-dkms-390.debdiff"
https://bugs.launch
Sorry, I posted the wrong file in comment #3, this is the right one.
** Patch added: "hirsute-nvidia-dkms-390-v2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1908099/+attachment/5450290/+files/hirsute-nvidia-dkms-390-v2.debdiff
--
You received this bug
Public bug reported:
With commit 30460e1ea3e6 ("fs: Enable bmap() function to properly return
errors"), applied to v5.6-rc1, running swapon on a file that has holes
returns an error (EINVAL); hibinit-agent is creating the swap file just
using fallocate(), without touching the whole file by deafult
certain arm64
instance types.
** Affects: linux-aws (Ubuntu)
Importance: High
Assignee: Andrea Righi (arighi)
Status: New
** Affects: linux-aws (Ubuntu Bionic)
Importance: High
Assignee: Andrea Righi (arighi)
Status: New
** Affects: linux-aws (Ubuntu Focal
** Also affects: linux-aws (Ubuntu Groovy)
Importance: Undecided
Status: New
--
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/1879711
Title:
aws: disable CONFIG_DMA_CMA
Stat
** Also affects: linux-aws (Ubuntu Groovy)
Importance: Undecided
Status: New
--
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/1732512
Title:
xen hibernation support for linux
Public bug reported:
[Impact]
During hibernation and resume the kernel is submitting an individual IO
request for each page of data. In the aws kernel we are using a custom
SAUCE patch to batch IO requests together in order to achieve better
performance.
Recently a patch designed to achieve the
Public bug reported:
[Impact]
The 5.8 kernel (groovy) is not still 100% reliable with hibernation,
especially on the Xen instance type. However, re-aligning the config
options as much as possible with the 5.4 kernel (focal) allows to
hibernate and resume with a success rate close to 100% (accordi
** Description changed:
[Impact]
The 5.8 kernel (groovy) is not still 100% reliable with hibernation,
especially on the Xen instance type. However, re-aligning the config
options as much as possible with the 5.4 kernel (focal) allows to
hibernate and resume with a success rate close t
** Also affects: zfs-linux (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: zfs-linux (Ubuntu
** Description changed:
+ [Impact]
+
+ zfs_write() doesn't properly account partial copies done by
+ copy_from_user(), causing accesses past the end of objects and
+ triggering kernel panics.
+
+ [Test case]
+
+ The problem seems to be workload specific, there is not a specific test
+ case to r
debdiff for focal reported in attach (built and tested).
** Patch added: "focal-zfs-fix-double-free-with-zfs-mount.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902588/+attachment/5438801/+files/focal-zfs-fix-double-free-with-zfs-mount.debdiff
--
You received this bug no
debdiff for groovy in attach (all zfs autotests completed correctly).
** Patch added: "groovy-zfs-fix-double-free-with-zfs-mount.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902588/+attachment/5438809/+files/groovy-zfs-fix-double-free-with-zfs-mount.debdiff
--
You recei
debdiff for hirsute in attach.
** Patch added: "hirsute-zfs-fix-double-free-with-zfs-mount.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902588/+attachment/5438827/+files/hirsute-zfs-fix-double-free-with-zfs-mount.debdiff
--
You received this bug notification because you
New debdiff for focal applied on top of the latest 0.8.3-1ubuntu12.6.
** Patch added: "zfs-fix-uio-partial-copies.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1904589/+attachment/5439545/+files/zfs-fix-uio-partial-copies.debdiff
--
You received this bug notification beca
New debdiff for focal on top of 0.8.3-1ubuntu12.7.
--
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/1902588
Title:
zfs mount -a: double free / memory corruption / segfault when
mount
** Patch added: "focal-zfs-fix-double-free-with-zfs-mount.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1902588/+attachment/5439561/+files/focal-zfs-fix-double-free-with-zfs-mount.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, wh
cal-kernel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
--
You r
** Summary changed:
- eoan/linux-aws: 5.3.0-1000.0 -proposed tracker
+ eoan/linux-aws: 5.3.0-1001.1 -proposed tracker
--
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/1844138
Title:
e
cal-kernel-team) => Andrea Righi
(arighi)
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi
(arighi)
--
You recei
Public bug reported:
[Impact]
It looks like nvidia-dkms-535 is using a symbol that became GPL-only in
the latest 6.7 kernel, causing the following build error:
# MODPOST <>/build/nvidia/535.146.02/build/Module.symvers
scripts/mod/modpost -M -m -a -o
<>/build/nvidia/535.146.02/build/Modu
The same problem happens also with nvidia-dkms-545 (still on arm64
only).
** Also affects: nvidia-graphics-drivers-545 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-dr
** Also affects: linux (Ubuntu Noble)
Importance: Critical
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/2028253
Title:
update apparmor and LSM stacking p
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
** Changed in: linux (Ubuntu Noble)
Status: New => 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/2046040
Title:
enable CONFIG_INTEL_TDX_HOST in linux >= 6.7 for nob
** Also affects: linux (Ubuntu Noble)
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/2045503
Title:
apply sched-ext patch set to linux-unstabl
Public bug reported:
[Impact]
Ubuntu provides the "lowlatency" kernel: a kernel optimized for
applications that have special "low latency" requirements.
Currently, this kernel does not include any specific UBUNTU SAUCE
patches to improve the extra "low latency" requirements, but the only
differe
** Description changed:
[Impact]
Ubuntu provides the "lowlatency" kernel: a kernel optimized for
applications that have special "low latency" requirements.
Currently, this kernel does not include any specific UBUNTU SAUCE
patches to improve the extra "low latency" requirements, but
** Description changed:
[Impact]
Ubuntu provides the "lowlatency" kernel: a kernel optimized for
applications that have special "low latency" requirements.
Currently, this kernel does not include any specific UBUNTU SAUCE
patches to improve the extra "low latency" requirements, but
** Description changed:
[Impact]
Ubuntu provides the "lowlatency" kernel: a kernel optimized for
applications that have special "low latency" requirements.
Currently, this kernel does not include any specific UBUNTU SAUCE
patches to improve the extra "low latency" requirements, but
** Description changed:
[Impact]
Ubuntu provides the "lowlatency" kernel: a kernel optimized for
applications that have special "low latency" requirements.
Currently, this kernel does not include any specific UBUNTU SAUCE
patches to improve the extra "low latency" requirements, but
@dsmythies thank you so much for sharing the results of your tests,
really useful info!
I'm planning to do more tests setting the performance governor, I've
been doing my initial tests only with the default Ubuntu settings, that
means with the "Balanced" power mode enabled (that I think it's using
@colin-king thanks! Any suggestion in particular? I was thinking to
lmbench, netperf and fio.
--
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/2051342
Title:
Enable lowlatency settings in
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Assignee: Timo Aaltonen (tjaalton)
Status: Confirmed
** Also affects: nvidia-graphics-drivers-470 (Ubuntu Noble)
Importance: Undecided
Status: Fix Released
--
You received this bug notification because you are a
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
@colin-king noticed, I just left a thank you message in the article.
I'll still do the tests, but it's nice to see that someone else is
contributing to this!
Another thing that I'd like to measure is to bpftrace the time spent in
the tick handler before and after these changes applied, because we
@andysem correct, without `nohz_full` specified at boot
CONFIG_NO_HZ_FULL has no effect, except for the little extra overhead
that it's adding to the tick handler (there is still some overhead with
this option enabled, even if it's not used). That's why I'd like to
measure the time spent in some of
@dsmythies IIUC this happens also with a mainline kernel, right? Not
just the Ubuntu lowlatency one.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-lowlatency-hwe-6.5 in
Ubuntu.
https://bugs.launchpad.net/bugs/2051733
Title:
@andysem yes that is also another possibility. The idea is to do a lot
of tests and if we find that there's a remote possibility to introduce
significant performance regressions in certain cases we can still keep
HZ=250, but definitely go with the other options.
--
You received this bug notificat
More tests and results available here:
https://discourse.ubuntu.com/t/enable-low-latency-features-in-the-
generic-ubuntu-kernel-for-24-04/42255
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
@turner basically any type of I/O workload can benefit from the HZ=1000
change, I haven't posted any test result, because in the scope of this
proposal I wanted to focus mainly at the regression potential for CPU-
intensive workloads and the benefits in terms of power consumption (this
one as a pos
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
** Description changed:
+ SRU Justification
- 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
+
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
** Also affects: bcmwl (Ubuntu Jammy)
Importance: Undecided
Status: New
--
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
I included the extra fixes in the attached debdiff to properly support
5.19 in jammy, I'll create a separate bug tracker to fix the issue
reported by satadru-umich in kinetic... thanks and sorry I'm noticing it
only now!
** Patch added: "bcmwl-support-5.19.debdiff"
https://bugs.launchpad.net/u
Public bug reported:
[Impact]
As reported in LP: #1981968 kernel 5.19 requires additional patches to
properly support this driver:
https://gist.github.com/joanbm/37fd0590f30b41e7e89ade6e242ca16e
https://gist.github.com/joanbm/052d8e951ba63d5eb5b6960bfe4e031a
Without these patches the kernel wou
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 not
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
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
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 tu
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| [stdou
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
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
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
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:
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
ubuntu_lxc.lxc-test
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 threa
201 - 300 of 689 matches
Mail list logo
