Nmi Watchdog Bug Soft Lockup
I have had a crash. I couldn't access remotely, and after 4 days I could access to the computer, it was irresponsive, I did a hardware reboot. Home Linux Ubuntu Fix Ubuntu BUG: soft lockup CPU stuck (VMWare Server) Fix Ubuntu BUG: soft lockup CPU stuck (VMWare Server). Rcuos, ubuntu cpu stuck, ubuntu soft lockup, virtualization, vmware server. Fix Yoast SEO Sitemaps Broken. A Truly Free LAN Messenger Cross-Platform Open Source Chat Client. Leave a Reply Cancel reply.
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.
Nmi Watchdog: Bug: Soft Lockup Suse
I searched a lot for a similar problem and could not find one.The problem occurs with both 5.1.12 or 5.0.30 and also earlier versions for a few months now.I tried ubuntu 16.04 64bit VM and also Debian machine 32 bit with jessie and now stretch.I recompiled the kernel, 4.8.15 same thing.I am using docker to run the firefox so that is an important information.The freeze occurs after a while using the firefox. I don't have an idea why it happens or in what situation. Sometimes it can run for a long time, sometimes not. It is sporadic. I can add that this happened on a Windows 7 host machine as well with both 5.1.12. 5.0.30 seemed to be working for a day but i did not check it that far.
The linux guest on the osx host is stalling a few times a day for a few months. I was thinking this was due to 64 bit kernel or something like that so when i switched to 32 bits i was surprised it still occured. I tried several versions of docker. Nothing helps, it always stalls.The machine sometimes is semi responsive by returning pings or allowing the port to be opened but not further than that. A similar scenario occurs within a few days with me. But before, I such cases had not noticed.It was not associated with changes in version. At that time, I have not changed anything, and not updated.Host = for Windows 10.
Guest = Ubuntu 16.04. Paravirtualization = default = KVM (for Ubuntu x64).5.1.6 (Guest Additions 5.1.6) and 5.1.14 (Guest Additions 5.1.14)(I update later, when tried to fix the problem, ).Freezing occurs after using any apps, such as IntelliJ IDEA? Or even when copying files. It works not for long - 5-30 min. If do nothing, guest OS can work longer.I changed Paravirtualization to None. 1 days - not freezing. But now there is a small brakes in Guest OS.
I'm new to this. I just downloaded 5.1.28 (from 5.1.26) and now my Ubuntu 16.04 LTS guest (host is Windows 7) runs painfully slow. During boot up I get several of the 'soft lockup' messages on various CPU's (I have it set to 28 because my host machine is a dual Zeon processor with 56 CPU's). Previously this would boot up in less than a minute (now it takes about 15 minutes).My Yocto builds of a Linux kernel would take about 10 minutes. I recently had to kill the machine after 2 hours (it appeared to have made it about half way through the build).
According to Windows Task Manager the VM is using only 18 to 20 CPU's at about 50%. Previously it would use all 28 CPU's flat out at 100% each (dang was that sweet).Oh ya, after the upgrade my VW for the Ubuntu Linux had all of its parameters reset. It was even switched back to Windows instead of Linux.I'm attaching my VBox.log file of my most recent boot up.Any help would be greatly appreciated.Cheers,Mark.
I solved my own problem. A short while back something went wrong with my Ubuntu and the whole Linux system locked up. This happens every now and again (about once a month and I'm using the system nearly constantly for 8 hours every work day). The only solution I've found to this lock up problem is to power cycle the virtual machine.But when this happened the last time I was getting this notice to upgrade to 5.1.28 which I did (that turned out to be a red herring for my problem. When I tried to start up my Ubuntu again, all of the settings in the virtual machine had been cleared out (???!). I went about resetting everything except for three somewhat obscure settings.
Here are the settings and what I set them to in order to get my machine working again:Settings-System-Acceleration-Paravirtualization Interface: set to DefaultSettings-System-Acceleration-Enable VT-x/AMD-V: set to checkedSettings-System-Acceleration-Enable Nested Paging: set to checked.It all runs fine now.Cheers,Mark.