I did found a workaround, but iam still convinced that we have a kind of bug.
I think i should explain our typical systemsetup, for better understandig.
Typical field of application are failoversystems. overall we use very few
software and systems have minimal load.
we have 2 servers in a
lspci -vvnn
00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host
bridge [8086:7190] (rev 01)
Subsystem: VMware Virtual Machine Chipset [15ad:1976]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
uname
Linux myhost 5.15.0-83-generic #92-Ubuntu SMP Mon Aug 14 09:30:42 UTC 2023
x86_64 x86_64 x86_64 GNU/Linux
--
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/2034701
Title:
/proc/version_signature
Ubuntu 5.15.0-83.92-generic 5.15.116
--
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/2034701
Title:
unexpected system behaviour after kernel update
Status in
dmesg
[0.00] Linux version 5.15.0-83-generic (buildd@lcy02-amd64-027) (gcc
(Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
#92-Ubuntu SMP Mon Aug 14 09:30:42 UTC 2023 (Ubuntu 5.15.0-83.92-generic
5.15.116)
[0.00] Command line:
It seems that Ubuntu 22.04 is affected in a critical way. Currently we had
freezes only on Ubuntu22, but in Ubuntu 20.04 there are similiar loglines.
After some hours of running the ubuntu 22.04 crashes and kernel/systemd are
damaged.
--
You received this bug notification because you are a
I collected some more loglines, produced by unproductive member of a
haproxy failoversystem with usually zero load. over the weekend there
are affected several servers. I think this is serious.
Sep 8 17:01:06 myhost kernel: [115882.039808] CIFS: Attempting to mount
\\host123\folder
Sep 8
Our servers are not connected with public internet. i cant run apport-
collect:
ERROR: connecting to Launchpad failed: [Errno 110] Connection timed out
You can reset the credentials by removing the file
"/root/.cache/apport/launchpad.credentials"
Today Morning same notice like yesterday. Again
Thanks.
Just for general information, when this patch will be published to live-
repos?
Thanks.
--
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/1772671
Title:
Kernel produces empty
yes, 4.4.0-129 also seems to be ok, but again no
Speculation_Store_Bypass line in /proc/PID/status.
--
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/1772671
Title:
Kernel produces empty
** Also affects: iotop (Ubuntu)
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/1772671
Title:
Kernel produces empty lines in /proc/PID/status
Hello,
i installed v4.17-rc6 and this problem seems fixed, no emtpy line in
/proc/PID/status, but i also miss the line Speculation_Store_Bypass which was
existing in 4.4.0-127-generic #153-Ubuntu
So may be this is fixed because meltdown/spectre patches are not applied? Iam
not sure, so i
yes, i can fix this in iotop, but i thin the main problem is kernel and
there should not exist an empty line under /proc/PID/status
Ubuntu Kernel Bot told me to send logs, but i cant run apport-collect
for security/dataprotection reasons.
Thanks
--
You received this bug notification because
Public bug reported:
Hello,
after running updates today to linux-
image-4.4.0-127-generic_4.4.0-127.153 and rebooting i noticed that iotop
is not working any more. Reason are empty lines in /proc/PID/status,
which confuse iotop (and me)
In new view there is an empy line between Seccomp and
When this new kernel will be released? This bug is killing our MySQL
Servers. Booting old kernels is only a bad workaround. I think a lot of
people with busy servers will have a problem.
This is 2.nd time we were hit by a big bug within short time. In oct 2016 our
nameservers got problems
I also upgraded to 3.13.0-106-generic from canonical-kernel-team ppa and
can confirm it is working again:
# sysctl -w net.ipv4.neigh.default.gc_thresh1=8192
net.ipv4.neigh.default.gc_thresh1 = 8192
# uname -a
Linux myhostname 3.13.0-106-generic #153-Ubuntu SMP Tue Dec 6 15:44:32 UTC 2016
x86_64
Today we updated 14.04 to 3.13.0-105-generic, bug still present.
--
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/1634892
Title:
Setting net.ipv4.neigh.default.gc_thresh1/2/3 on
When this fix will appear in official kernel-release?
Yesterday i updated Trusty Tahr/14.04 to 3.13.0-103-generic and this problem is
still present.
This is a problem for all people who use 14.04 in high frequented environments,
just like nameservers.
--
You received this bug notification
18 matches
Mail list logo
