Public bug reported:
DKMS make.log for bcmwl-6.20.155.1+bdcom for kernel 3.10.2-031002-generic
(x86_64)
samedi 27 juillet 2013, 15:16:56 (UTC+0200)
make: entrant dans le répertoire « /usr/src/linux-headers-3.10.2-031002-generic
»
CFG80211 API is prefered for this kernel version
Using CFG80211 AP
versioned packages
that didn't have that version in their package name (ie, to find the
generic metapackages).
Ewen
PS: Reboots (due to kernel panic, and kernel.panic=15 sysctl) over the
weekend:
-=- cut here -=-
ewen@naosr620:~$ last | grep reboot
reboot system boot 4.15.0-62-generi Mon S
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.
62:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?h=master-
next&id=b502cfeffec81be8564189e5498fd3f252b27900
Ewen
--
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/1843152
T
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
e process
reported, although it seems the last one was a couple of hours ago, so
I guess it's traffic dependent/timing dependent.
ewen@naosr620:~$ uptime
16:27:32 up 5:19, 1 user, load average: 0.08, 0.14, 0.06
ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9]*/
our. (I don't have time at present,
due to my day job being excessively busy, to try to troubleshoot what
Ubuntu changed between 5.4.0-148.165 and 5.4.0-149.166; but if the
problem remains unfixed in a month when I'll hopefully have some more
time I might try to review the diff between those two v
to be a pointer actually isn't used/used as a pointer
(presumably hence 0). Which makes me think "improperly back ported"
(most likely by the Linux kernel "stable" process) is the most likely
cause, and a state check got missed.
Ewen
--
You received this bug notification becau
5f55c3a33512dbab613f7). Yet
Ubuntu Linux released the buggy version in April 2023 :-/
Anyway I'm fairly confident that Ubuntu 5.4.0-152 should be okay. I'll
update my server later this month, and if there are no more reports by
about mid July 2023 I'll close this issue.
Ewen
** Bug wat
the process
reported, although it seems the last one was a couple of hours ago, so I
guess it's traffic dependent/timing dependent.
ewen@naosr620:~$ uptime
16:27:32 up 5:19, 1 user, load average: 0.08, 0.14, 0.06
ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9]*/CPU: N/; s/PI
above (WARNING: CPU: 10 PID: 0 at
net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0) have continued
overnight, but coming in bursts -- some hours had no reports, and other
hours had 5-10 reports. So definitely feels like a race condition of
some sort.
Ewen
--
You received this bug notification be
x Kernel Stable Team fixes being
copied out to various kernel versions (and then pulled into Ubuntu's
kernel updates).
So I'm going to close the issue as "fixed released" for both linux-image
and linux-image-kvm. I believe the fix was released about 1 month ago
(mid June 2023).
the process
reported, although it seems the last one was a couple of hours ago, so
I guess it's traffic dependent/timing dependent.
ewen@naosr620:~$ uptime
16:27:32 up 5:19, 1 user, load average: 0.08, 0.14, 0.06
ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9
the process
reported, although it seems the last one was a couple of hours ago, so
I guess it's traffic dependent/timing dependent.
ewen@naosr620:~$ uptime
16:27:32 up 5:19, 1 user, load average: 0.08, 0.14, 0.06
ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9]*/CPU: N/
14 matches
Mail list logo
