Fixed in linux-image-kvm-1093 by pulling in upstream Linux Kernel Stable
Team fix.
** Changed in: linux-signed-kvm (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
h
Fixed in linux-image-5.4.0-151 and later, by pulling in upstream Linux
Kernel Stable Team fix.
** Changed in: linux-signed (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in U
I have seen no further reports since upgrading to linux-image-5.4.0-152.
So given the analysis above, I believe this bug was introduced by the
(upstream) Linux Kernel Stable Team, due to a change in freeing memory
that didn't take this assertion into account. And then was later fixed
by the (upstr
Thanks to Steve Matos for pointing out that the relevant warning was
likely reverted in the Linux Kernel "Stable" release 5.4.234, which is
tracked in Ubuntu as:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017691
>From digging into the Linux kernel stable git history (below) I'm fairly
Based on the comments above, and the Oracle Linux report that Leif M
found (thanks!) it seems likely that this is an upstream Linux kernel
"stable" backport which (probably in the upstream Linux kernel "stable")
was incomplete. Which now a bunch of Linux distros (including Ubuntu
and Oracle Linux)
As Steve Matos notes, linux-image-5.4.0-149-generic seems to have been
released into the main focal-updates repository, apparently without
making an attempt to address the regression that causes the
"net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0".
So I have retitled the bug with "regressio
** Summary changed:
- linux-image-5.4.0-149-generic (focal-proposed): 0 at net/core/stream.c:212
sk_stream_kill_queues+0xcf/0xe0
+ linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212
sk_stream_kill_queues+0xcf/0xe0
--
You received this bug notification because you are a memb
FTR, I figured out how focal-proposed ended up enabled, with packages
intalled from focal-proposed: the system had bionic-proposed enabled,
but pinned to be low priority (so packages could be installed from
proposed by manual override), at some point in the past. After upgrade
to focal, the apt so
Public bug reported:
After upgrading and rebooting this Ubuntu 20.04 LTS server (Ubuntu
Focal), I noticed that it was suddenly getting a bunch of kernel log
(dmesg) reports like:
WARNING: CPU: 4 PID: 0 at net/core/stream.c:212
sk_stream_kill_queues+0xcf/0xe0
while investigating I determined that
FTR, 4.15.0-62 seems *much* better than 4.15.0-60. With 4.15.0-60 this
system was kernel panic restarting every 75-90 minutes; now it's been up
since I installed 4.15.0-62, over 5 hours ago:
-=- cut here -=-
ewen@naosr620:~$ uname -r
4.15.0-62-generic
ewen@naosr620:~$ uptime
16:09:54 up 5:26,
These symptoms sound very much like
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447 (I found
the bug I'm commenting on while searching for additional links about the
issue in 1842447). There's a -62 kernel in proposed updates which
hopefully contains the fix for this bug. See
https:/
FTR, I think this is the fix in -62:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?h=master-
next&id=b502cfeffec81be8564189e5498fd3f252b27900
and it appears to be the only change from -60 to -62:
-=- cut here -=-
ewen@naosr620:~$ zcat
/usr/share/doc/linux-headers-4.15.0-62-gene
I agree with Taher (in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/comments/15),
this bug seems to impact a lot of systems (my colo host was kernel panic
restarting about every 75-90 minutes, all weekend). It has a NAT
firewall on it (for the hosted VMs), but no Docker/Wireguard,
13 matches
Mail list logo
