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
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 th
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 r
** 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.
ht
** 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 a
** 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
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 partic
** 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 valid
** 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:
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"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics
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: "nvidia-dkms-390-jammy-support-linux-6.2.deb
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...):
https://gitlab.com/herecura/packages/nvidia-390x
** 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 because
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 sys
@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: l
** 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
+
** 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 imp
** 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 enab
Public bug reported:
[Impact]
In order to support Rust in the kernel starting with Lunar we had to
apply the following UBUNTU SAUCE patch:
27c4fe11712c ("UBUNTU: SAUCE: modpost: support arbitrary symbol length
in modversion")
This patch can potentially introduce a user-space regression, beca
** Also affects: linux-hwe-6.2 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
** No longer affects: linux (Ubuntu Jammy)
** Changed in: linux-hwe-6.2 (Ubuntu Jammy)
Status: New => Fix Committed
** Also affects: linux-lowlatency-hwe-6.2 (Ubuntu)
@mihalicyn yes, it looks like we are missing "UBUNTU: SAUCE: overlayfs:
allow with shiftfs as underlay" in all the kernels >= 6.2. I'll open a
separate bug for this.
I'm wondering... do we really need to support overlayfs on top of
shiftfs? Of course we don't want to break the old behavior, so the
@mihalicyn update: I did some tests and even if we're missing
d24b8a547be1 ("UBUNTU: SAUCE: overlayfs: allow with shiftfs as
underlay") in kernels >= 6.2 I'm able to use overlayfs on top of shiftfs
(using the shiftfs mount-point as lower). I even tried the test case
mentioned in the commit and I co
Between 6.2.0-1006-kvm and 6.2.0-1007-kvm the main kernel changed from
6.2.0-23 to 6.2.0-24, but the changes are minimal (only 2 fixes), that
seem unrelated to any potential size increase.
Maybe there was a toolchain/binutils update? I'll check the binaries to
see if I spot something interesting.
Applied to mantic/linux-unstable:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/unstable/commit/?id=6f2091e61e72ed73f92cf49d882fb19c50dd860c
Do you think we should SRU this change to lunar kernels (and jammy as
well)?
Thanks!
** Also affects: linux (Ubuntu Mantic)
Impo
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Description changed:
+ [Impact]
+
+ The ubunt
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:
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]
Provide an updated patch set for apparmor / LSM stacking with all the
custom features that we need in the Ubuntu kernel.
This patch set is required to provide the proper confinement with snaps
and other Ubuntu-specific security features.
[Fix]
Apply the latest upd
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
** 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/2028253
Title:
update apparmor and LSM stacking patch set
S
Public bug reported:
[Impact]
When the zfs module is loaded we can see the following errors in dmesg
with the latest 6.5 kernel in mantic:
[ 10.730318] UBSAN: array-index-out-of-bounds in
/build/mantic/debian/build/build-generic/
debdiff in attach fixes the UBSAN warnings with linux 6.5 on mantic.
** Patch added: "zfs-fix-ubsan-warnings.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2033385/+attachment/5696047/+files/zfs-fix-ubsan-warnings.debdiff
--
You received this bug notification because you a
Add LP bug reference to the changelog.
** Patch added: "zfs-fix-ubsan-warnings.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2033385/+attachment/5696048/+files/zfs-fix-ubsan-warnings.debdiff
--
You received this bug notification because you are a member of Kernel
Packages
Public bug reported:
[Impact]
On unload the spl module is not properly cleaning up the registered
sysctl entries with kernel 6.5 in Mantic:
06:58 ubuntu@mantic$ sudo modprobe spl
modprobe: ERROR: could not insert 'spl': Protocol driver not attached
06:58 ubuntu@mantic$ sudo dmesg | grep duplicat
Upstream pull request to fix this issue:
https://github.com/openzfs/zfs/pull/15239
--
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/2034510
Title:
spl fails to unregister sysctl entrie
Attached debdiff seems to fix the bug (reproduced and tested in a local
VM with the latest Mantic 6.5 kernel).
** Patch added: "spl-fix.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2034510/+attachment/5697900/+files/spl-fix.debdiff
--
You received this bug notification b
** 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/2030525
Title:
Installation support for SMARC RZ/G2L platfor
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:
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
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
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
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
*** 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
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
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
** 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
** 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)
** 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
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
** 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
** 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
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
** 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
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
@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)
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
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
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:
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
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
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:
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
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
** 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
** 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
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
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
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
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
@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:
[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
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
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
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
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
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
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
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
@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
...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
601 - 689 of 689 matches
Mail list logo
