Nov 16, 2016 - CentOS 7 - kernel: BUG: soft lockup - CPU#3 stuck for 23s! 08 NMI backtrace for cpu 3 09 CPU: 3 PID: 19 Comm:. Additional info: reporter: libreport-2.3.0 NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s!
Kernel Nmi
Oops, your web browser is no longer supported.YouTube works with a wide range of browsers. However, if you'd like to use many of our latest and greatest features, please upgrade to a modern, fully supported browser.Find the latest versions of our supported browsers below.This message is based on the the user agent string reported by your browser.
Any extensions and plugins you have installed might modify the user agent string. We received:Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1),gzip(gfe)No thanks.
Kernel:nmi Watchdog: Bug: Soft Lockup
Nmi Watchdog: Bug: Soft Lockup - Cpu#1 Stuck For 22s
HelloThis is an issue that’s been creating big problems for me in the past 6 months.Almost every few days, some of my nodes are getting stuck, dying (only reboot solves it) with the multiple such errors:NMI Watchdog: BUG: soft lockup - CPU#0 stuck for 22s! ksoftirqd/4:36INFO: rcusched self-detected stall on cpuo4-: (2 GPs behind) idle=eb0/01/0 softirq=99753 fqs=7165NMI Watchdog: BUG: soft lockup - CPU#1 stuck for 24s! ksoftirqd/0:7Full trace:This is on debian kernel 4.10.15-1 (proxmox). In lxc 2.0.6 it was showing the process like nginx or something that caused the issue, and if i managed killed that process before the server died completly, it would have fixed the issue.However, on lxc 2.0.8, it’s simply giving the process of ksoftirqd.In the past, one solution that helped reduce the number of such crashes was limiting the maxpids for the container. Some containers were able to crash the node with 200 max pids even.
I’m using 400 as default at the moment.Any idea what other limitations we can add to prevent such issues?Any help would be highly appreciated! I have come across the same issue on an ubuntu 4.15.0-x LXC hostNot sure whether it plays a role but in my case the inital bug was with the KVM hypervisor the LXC host is running on.
After that been rectified the CPU freezes became less frequent and only impacted one CPU whilst prior to the fix on the KVM hypervisor both CPU suffered.It was then recommended to increase kernel.watchdogthresh = 10 to kernel.watchdogthresh = 20 on the LXC host. Since then the CPU stalls are gone, not sure though whether that is a good practice or just a kludge. Stgraber:his is very much a kernel bug. I’m not sure how an older LXC would have influenced this at allafter some testing and investigation of kernel logs I would concur. From the kernel logs it is apparent that lxc is never cited as the culprit and is neither listed in Modules linked in at the time of CPU lockups.VPS are in general proably more prone to the issue than bare metal and low spec VPS even more so.On a physical host, a soft lockup message generally indicates a kernel bug or hardware bug. When running in a virtual machine, this might instead indicate high levels of overcommitment (especially memory overcommitment) or other virtualization overheads.