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
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
** 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
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
Debdiff in attach fixes the build problems with linux 6.1 and it should
also fix LP: #1998039 (once confirmed/tested we can set 1998039 as
duplicate of this one).
** Patch added: "bcmwl-kernel-6.1-and-netdev-fix.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1999009/+attachment/
Public bug reported:
[Impact]
bcmwl-kernel-source fails to build with the latest linux 6.1 in Lunar.
Moreover, with kernels >= 5.17 there's an incorrect access to struct
netdev (see LP: #1998039).
[Test case]
$ sudo apt install bcmwl-kernel-source
[Fix]
The following upstream commits have ch
** Summary changed:
- focal: merge wireguard into the kernel
+ focal: merge upstream wireguard
** Description changed:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
external module (wireguard-dkms). This dkms is not maintained anymore,
but upstream maint
** Description changed:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
external module (wireguard-dkms). This dkms is not maintained anymore,
but upstream maintainer periodically provides backported patches for
older kernels (like 5.4) in this git reposit
** Description changed:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
external module (wireguard-dkms). This dkms is not maintained anymore,
but upstream maintainer periodically provides backported patches for
older kernels (like 5.4) in this git reposit
** Description changed:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
external module (wireguard-dkms). This dkms is not maintained anymore,
but upstream maintainer periodically provides backported patches for
older kernels (like 5.4) in this git reposit
** Description changed:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
external module (wireguard-dkms). This dkms is not maintained anymore,
but upstream maintainer periodically provides backported patches for
older kernels (like 5.4) in this git reposit
** Description changed:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
- external module (wireguard-linux-compat dkms). This dkms is not
- maintained anymore, but upstream maintainer periodically provides
- backported patches for older kernels (like 5.4) in thi
Public bug reported:
[Impact]
In older kernels, like focal, Wireguard used to be maintained as an
external module (wireguard-linux-compat dkms). This dkms is not
maintained anymore, but upstream maintainer periodically provides
backported patches for older kernels (like 5.4) in this git repositor
With the debdiff in attach applied (on top of the latest debian unstable
zfs) everything seems to work fine on the latest lunar/linux-unstable
(6.1.0-9-generic).
** Patch added: "zfs-dkms-2.1.6.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1998487/+attachment/5633750/+files
** Also affects: zfs-linux (Ubuntu Lunar)
Importance: Undecided
Status: New
--
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/1998487
Title:
zfs-dkms: support linux 6.1
Statu
Public bug reported:
[Impact]
The current version of zfs-dkms available in lunar (2.1.5) fails to
build with kernels >= 6.1.
[Test case]
$ apt install zfs-dkms
[Fix]
Resync with the latest zfs-linux from debian unstable and apply the
following upstream patch to properly support linux 6.1:
ec
** 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.
https://bugs.launchpad.net/bugs/1993818
Title:
Linux kernel crash on Ubuntu 22.10 on Th
** Also affects: linux (Ubuntu Lunar)
Importance: Medium
Status: Triaged
** Also affects: lava (Ubuntu Lunar)
Importance: Undecided
Status: Triaged
** Also affects: bpfcc (Ubuntu Lunar)
Importance: Undecided
Status: Triaged
** Also affects: bpftrace (Ubuntu Lunar)
** Changed in: linux (Ubuntu)
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/1993818
Title:
Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Ca
Thanks for testing and good to know that the kernel doesn't seem to
crash (so far). All the i915 fixes that I applied will be available in
the next official Kinetic kernel, so we should be good. Let me know if
the problem happens again.
About the color distortions I'll investigate a bit. I may ask
I noticed that we're missing some i915 fixes from stable updates, so
I've applied a bunch of patches from stable and produced this test
kernel:
https://kernel.ubuntu.com/~arighi/lp-1993818/
It'd be great if someone affected by this bug could give it a try and
verify if the problem is still happen
*** This bug is a duplicate of bug 1991704 ***
https://bugs.launchpad.net/bugs/1991704
** This bug has been marked a duplicate of bug 1991704
Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
--
You received this bug notification because you are a member of Kernel
Pac
*** This bug is a duplicate of bug 1991704 ***
https://bugs.launchpad.net/bugs/1991704
** This bug has been marked a duplicate of bug 1991704
Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
--
You received this bug notification because you are a member of Kernel
Pac
So, it looks like there are multiple issues here. The NULL pointer
dereference bug that I see in comment #25 seems to be fixed by
458ec0c8f359 ("drm/i915: fix null pointer dereference"), but this can
happen only when i915 is used.
For the other problem(s) do you happen to have a kernel oops / trac
Test kernel (5.19.0-19.19+i915fix) available here:
https://kernel.ubuntu.com/~arighi/lp-1991703/
It would be great if someone affected by this problem could test this
out. Thanks in advance!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
This bug should be fixed by 458ec0c8f359 ("drm/i915: fix null pointer
dereference"), I'll prepare a test kernel with this fix applied on top
of 5.19.0-19.19.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://b
Public bug reported:
[Impact]
Align with the latest apparmor and LSM stacking versions.
To do so we need to:
- revert sauce to get back to upstream apparmor, and drop old LSM stacking
- pull in needed patches from upstream 6.0
- pull in needed patches from apparmor-next 6.1
This is required
Hi Brian, we have also experienced this issue during our tests, but it's
really hard to reproduce it on our side.
It seems to be a regression in virtio-rng and I've prepared a test
kernel, but we still haven't found a way to reproduce it systematically,
so I couldn't verify if this test kernel is
Fix for the 5.4 kernel in bionic reported in attach.
** Patch added: "lttng-support-kernel-5.4-without-random-tracepoints.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1986921/+attachment/5614597/+files/lttng-support-kernel-5.4-without-random-tracepoints.debdiff
--
Yo
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
Public bug reported:
[Impact]
Intel has requested to support the TDX (trust domain extension) guest
attestation driver interface. In a TDX guest "attestation" is used to
verify the trustworthiness of a TD (trusted domain) before provisioning
secrets to the TD (i.e, encrypted keys to mount an encr
** Also affects: linux (Ubuntu Kinetic)
Importance: High
Assignee: Canonical Kernel Team (canonical-kernel-team)
Status: Fix Released
** Changed in: linux (Ubuntu Kinetic)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ke
** Summary changed:
- refactoring of overlayfs fix to report the right mnt_id of files opened from
map_files
+ refactoring of overlayfs fix to properly support shiftfs
** Description changed:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce patch:
- UBUNTU
** No longer affects: linux (Ubuntu Focal)
--
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/1983640
Title:
refactoring of overlayfs fix to report the right mnt_id of files
opened from ma
Public bug reported:
[Impact]
Starting with 5.13 we've incorrectly dropped the following sauce patch:
UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
map_files
This patch is required to use overlayfs on top of shiftfs and without
this patch we may break containers that r
** Also affects: network-manager (Ubuntu Kinetic)
Importance: Undecided
Status: Invalid
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: Invalid
** Also affects: urfkill (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bu
...or if it's easier, I've just uploaded some debs here:
https://kernel.ubuntu.com/~arighi/lp-1981658/
This kernel (5.4.0-1087.92+arighi) is probably going to be the Azure
kernel in proposed and it includes the fix that I mentioned above.
--
You received this bug notification because you are a m
@squirrelsc the next Azure kernel in Focal that will have this fix is
going to be 5.4.0-1087.92, but I don't see it in proposed yet. If it
helps I can upload to a ppa an "unofficial" Azure kernel with the fix.
--
You received this bug notification because you are a member of Kernel
Packages, whic
I think this might be fixed by `55573f3a3f352 tcp: make sure
treq->af_specific is initialized` that is currently applied to
5.4.0-123.139 in focal-proposed.
It'd be great if someone that is able to reproduce the problem could try
to install this new kernel from -proposed and verify if it's still
h
Fix to properly support kernels >= 5.18 in attach.
** Patch added: "bcmwl-support-linux-5.18.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1981968/+attachment/5603690/+files/bcmwl-support-linux-5.18.debdiff
--
You received this bug notification because you are a member of Ker
Public bug reported:
[Impact]
bcmwl fails to build on kernel 5.19 with the following errors:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:603:14:
error: implicit declaration of function ‘pci_alloc_consistent’; did you mean
‘osl_dma_alloc_consistent’? [-Werror=implicit-fu
Fixes for nvidia-dkms-510-server.
** Patch added: "support-linux-5.19-nvidia-510-server.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1978539/+attachment/5597442/+files/support-linux-5.19-nvidia-510-server.debdiff
--
You received this bug notification be
same fixes for nvidia-dkms-470-server
** Patch added: "support-linux-5.19-nvidia-470-server.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1978539/+attachment/5597370/+files/support-linux-5.19-nvidia-470-server.debdiff
--
You received this bug notificatio
same fixes for nvidia-dkms-510.
** Patch added: "support-linux-5.19-nvidia-510.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1978539/+attachment/5597215/+files/support-linux-5.19-nvidia-510.debdiff
--
You received this bug notification because you are a
debdiff in attach fixes all the build failures with kernels >= 5.19.
** Patch added: "support-linux-5.19-nvidia-470.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1978539/+attachment/5597189/+files/support-linux-5.19-nvidia-470.debdiff
--
You received thi
Public bug reported:
[Impact]
nvidia-dkms-470 fails to build on kinetic with the new (upcoming) kernel
5.19.
[Test case]
sudo apt install nvidia-dkms-470
[Fix]
Change driver to support the new 5.19 ABI.
[Regression potential]
We may see build issues / regressions in kernels >= 5.19, since t
@zhanglei-mao have you tried to update the kernel? Does it still happen
also with a more recent 5.4?
--
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/1976511
Title:
kernel taint ( warning
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
Public bug reported:
[Impact]
Use nosuid,noexec mount options on devtmpfs, this allows to provide a
bit of extra security by preventing mmapping stuff in /dev with
PROT_EXEC or having setuid executables.
[Test case]
If we really want to provide a test case for this...:
$ grep devtmpfs /proc/m
Public bug reported:
[Impact]
The patch that we have recently re-introduced to properly support
overlayfs on top of shiftfs can introduce potential kernel panics, for
example:
BUG: kernel NULL pointer dereference, address: 0008
[ 447.039738] #PF: supervisor read access in ke
Alex, thanks for the review! We can definitely remove the dependency of
AUFS and provide a standalone patch, in this way we can provide this
feature also to those kernels that don't have AUFS enabled (like all the
recent kernels in jammy). I'll work on that and will ping you when I
have a patch rea
Everything looks good, so I re-applied the patch with the addition of
this extra fix:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.15-next&id=b4c25dba7993400e9c57d3e60bec4ab8bce1b701
--
You received this bug notification because you are a member of Ke
I think I have a proper fix to re-introduce this patch without panicing
the kernel. I'm currently running some stress tests to make sure nothing
is broken. If everything goes well I'll re-introduce this patch with the
proper fix.
--
You received this bug notification because you are a member of K
@mihalicyn Yes, this patch without AUFS enabled doesn't introduce any
problem, but that's because without AUFS the patch is basically a no-op.
Here's the ported patch that was applied to 5.15:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?h=hwe-5.15-next&id=e3e60
NOTE to clarify: I'm going to revert this patch in focal/hwe-5.15, that
is the only 5.15 kernel with this patch that has AUFS enabled (so the
only kernel where this bug can be triggered).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
This patch seems to introduce this NULL pointer dereference, that can be
triggered systematically running lxc autopkgtest:
BUG: kernel NULL pointer dereference, address: 0008
[ 447.039738] #PF: supervisor read access in kernel mode
[ 447.040369] #PF: error_code(0x) - not-present
** Summary changed:
- disable Intel DMA remapping options by default
+ disable Intel DMA remapping by default
--
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/1971699
Title:
disable Intel
Public bug reported:
[Impact]
It seems that enabling Intel IOMMU can cause some weird gfx problems, see for
example:
https://bugs.launchpad.net/bugs/1971146
https://bugs.launchpad.net/bugs/1965882
[Test case]
We don't have any specific test case, only other bug reports that
tracked down
** Also affects: linux-azure (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Jammy)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-azure (Ub
** Description changed:
+ [Impact]
+
+ Starting with 5.13 we've incorrectly dropped the following sauce patch:
+
+ UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from
+ map_files
+
+ This patch seems to be required to use overlayfs on top of shiftfs and
+ without this patch
Thanks for pointing this out Andrew. It looks like this patch is relying
on AUFS that has been dropped/disabled in jammy, but it's still
available in focal, so we should definitely re-apply this patch.
I'll make sure this is re-applied to 5.13 and 5.15 (changing the code to
properly depend on AUFS
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
Revert "swiotlb: rework "fix info leak with DMA_FROM_DEVICE""
USB: serial: pl2303: add IBM device IDs
dt-bindings: usb: hcd: correct usb-device path
USB: serial: pl2303: fix GS type detection
USB: serial: simple: add Nokia phone driver
mm: kfence: fix missing objcg housekeeping for SLAB
locking/loc
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
** Changed in: linux (Ubuntu Jammy)
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/1968982
Title:
Jammy update: v5.17.1 upstream stable release
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)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andrea Righi (arighi)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member
Public bug reported:
[Impact]
Enable AMX (aka TMUL) new instructions on the 5.15 kernel.
[Test case]
Tests have been performed directly by Intel.
[Fix]
Apply the following upstream commits:
20df73756148 ("selftests/x86/amx: Update the ARCH_REQ_XCOMP_PERM test")
063452fd94d1 ("x86/fpu/xstate:
** Also affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Jeff Lane (bladernr)
Status: In Progress
--
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/1960361
Title:
h
** Also affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Jeff Lane (bladernr)
Status: In Progress
--
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/1960362
Title:
E
Adding also focal, because with the new linux-hwe-5.15 we get the same
failure.
** Summary changed:
- update iproute2 in jammy
+ update iproute2
** Also affects: iproute2 (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member o
Public bug reported:
This ftrace sub-test is failing on focal with the latest hwe-5.15:
[stdout] # [67] event trigger - test inter-event histogram trigger
snapshot action[FAIL]
We have not seen this failure before.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
JFYI, I've sent an SRU email to apply the kernel fix also to Impish
5.13, just to be safe in case the gcc patch lands in Impish:
https://lists.ubuntu.com/archives/kernel-team/2022-February/127652.html
** Also affects: zfs-linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also
The impish kernel is already fixed and the fix is applied to the current
kernel in released. Comment #142 is referring to linux-oem-5.14 in
focal, that also has the fix, so it can be ignored.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this b
Public bug reported:
kernel selftest net:test_bpf.sh can return the following error on
ppc64el and arm64:
10664 02:12:25 DEBUG| [stdout] [ 1001.533842] test_bpf: #313
BPF_ATOMIC | BPF_W, BPF_ADD | BPF_FETCH: Test: 0x12 + 0xab = 0xbd
10665 02:12:25 DEBUG| [std
** Changed in: linux (Ubuntu)
Status: Expired => 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/1943697
Title:
net veth selftest failure
Status in linux package in Ubun
Public bug reported:
It looks like the glibc autopkgtest in jammy for s390x is using gcc-10
and it's failing to build with the following error:
s390x-linux-gnu-gcc-10 ../sysdeps/s390/longjmp.c -c -std=gnu11 -fgnu89-inline
-pipe -O2 -g -fdebug-prefix-map=/tmp/autopkgtest.ehGgT4/build.Jkr/src=. -
GCC: (Ubuntu 11.2.0-14ubuntu1) 11.2.0
^ This version of gcc is reverting the patch that introduces the bug. It
is possible to reproduce the bug with gcc <= 11.2.0-13ubuntu1.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubu
New debdiff, because v2 was missing the gcc-10 dependency for zfs-dkms
in debian/control.
** Patch added: "zfs-update-to-2.1.2-v3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1954676/+attachment/5553379/+files/zfs-update-to-2.1.2-v3.debdiff
--
You received this bug notifica
New debdiff in attach that enforces gcc-10 to build the dkms part on
s390x.
** Description changed:
[Impact]
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
rtance: Undecided => Critical
** Changed in: zfs-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 zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/19
** Also affects: gcc-11 (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
[Impact]
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
I've tried multiple versions of gcc and here's the result:
- gcc 11.2.0-13ubuntu1 : bad
- gcc 11.2.0-12ubuntu1 : bad
- gcc 11.2.0-10ubuntu1 : bad
- gcc 11.2.0-7ubuntu2 : good
- gcc 10.3.0-13ubuntu1 : good
Apparently the last version of gcc that seems to work with zfs + kernel
5.15 is 11.2.0
Quick summary: it really looks like a compiler issue, because everything
works using the same version of kernel + zfs, but on Impish. Also trying
to compile zfs with gcc-10 doesn't show any problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscr
Update: we're still getting the same failure even with zfs 2.1.2. I've opened
an issue upstream:
https://github.com/openzfs/zfs/issues/12942
** Bug watch added: github.com/openzfs/zfs/issues #12942
https://github.com/openzfs/zfs/issues/12942
--
You received this bug notification because you
Public bug reported:
[Impact]
c4.large instances are stuck at boot with kernel 5.15.0-15.15.
[Test case]
Simply deploy a c4.large instance and install the latest jammy kernel
(5.15.0-15.15).
[Fix]
It looks like the offending commit is the following:
02c70033b98b ("PCI/MSI: Mask MSI-X vector
*** This bug is a duplicate of bug 1928890 ***
https://bugs.launchpad.net/bugs/1928890
** This bug has been marked a duplicate of bug 1928890
vrf_route_leaking.sh in net from ubuntu_kernel_selftests linux ADT test
failure with linux/5.11.0-18.19 (Ping received ICMP Packet too big)
--
You
This issue is still present also on jammy 5.15. Some details that I
found:
- the purpose of this test is to verify that an ICMP6 packet is not forwarded
by a virtual router if it needs to do fragmentation
- the test creates 3 network namespaces representing host1, host2 and router
- host1 a
Public bug reported:
Kernel selftest srv6_end_dt46_l3vpn_test.sh reports the following error
(it seems to be an upstream issue):
15187 19:34:40 DEBUG| [stdout] #
15188 19:
Public bug reported:
Script srv6_end_dt4_l3vpn_test.sh reports the following failure
(upstream issue):
15321 19:35:52 DEBUG| [stdout] #
15322 19:35:52 DEBUG| [stdout] # TE
Public bug reported:
Running vrf_route_leaking.sh returns the following error:
###
IPv6 (sym route): VRF ICMP fragmentation error route lookup ping
###
New iproute has been merged in jammy. We can close this.
** Changed in: iproute2 (Ubuntu Jammy)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https:
New iproute has been merged in jammy. We can close this.
--
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:
update iproute2 in jammy
Statu
New debdiff to move to zfs 2.1.2 in attach.
** Patch added: "zfs-update-to-2.1.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1954676/+attachment/5551832/+files/zfs-update-to-2.1.2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1951440
Title:
Enable CONFIG_INTEL_IOMMU_DEFAULT_ON and
CONFIG
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
201 - 300 of 689 matches
Mail list logo
