By defa ult, this value is set to 10 seconds and the maximum soft lockup timeout is now increased from 60 seconds to 300 seconds for systems that have a large number of cpus. Guest has divider10 kernel parameter to keep the host cpu load low. The problem occurs at a random time, but very often. Thanks in advance and sorry if i missed something along the way. This can sometimes be too low if the system is very busy with io. The issue occurs most often after a reboot from a succeessful kickstart. I can correct the problem by entering recovery mode and.
The centosrhel kernel has a default softlockup threshold of 10 seconds. Download the readaheadcollector program and build it 2. I have installed sap hana studio and added the sap hana express edition as system. Ive seen a few bug reports and questions on stackexchange and elsewhere regarding a nagging bug. I was trying to install again, with increased virtual machine resources 8gb. The messages log with the lockup is attached below. The watchdog daemon will send an nonmaskable interrupt nmi to all cpus in the system who, in turn, print the stack traces of their currently running tasks. Everything seems to be fine except after 1015 min, i get the messages like bug. Any message in varlogmessages referencing soft lockups like these. So far, i havent found any clue as to what to do or try rather, the clues ive found and followed havent stopped this from happening. The linux guest on the osx host is stalling a few times a day for a few months. The technical reason behind a soft lock involves cpu interrupts and nmiwatchdog. The cap optionally fixes the maximum amount of cpu a domain will be able to consume, even if the host system has idle cpu cycles. I have 16gb ram on my desktop and i am using vmware player to run the sap hana express edition.
I am having the exact same problem with kernel version 2. However, if i try to install the driver using rpm and then reboot the system, during startup the os gets stuck spitting out the following soft lockup message for all the cpu cores, except for one core that is in soft lockup in one of the threads created by my driver. We have also seen these messages on an idle system with a large core count. I heard something about disabling acpi but i dont know how that will affect the server. After running fine for a couple of hours the server suddenly timed out on ssh, bind etc. For each cpu on the system, a watchdog process gets created. A soft lockup is defined as a bug that causes the kernel to loop in kernel mode for more than 20 seconds without giving other tasks a chance to run.
After discovering new san luns, the system locks up. Guest was set up with 1 cpu, but since my host has a quad intel processor, i decided to try increasing it to 4 cpus on the guest. I have a linux machine that is giving a lot of bug. I have seen this on hp dl360 g8 servers which were using multiple fiber channel controllers and multipath to attach several hundred san. If you dont have iotop or not able to install it due to company policy you can try. Often i have to poweroff the server, but last time i found some information in syslog. The server became very slow, and couldnt be logined with ssh, after reboot, we found varlogmessage has lots of kernel.
7 833 1619 210 951 870 1551 1003 350 114 687 1400 850 839 1347 125 614 47 1551 1159 490 651 30 474 176 1214 892 70 462 1160 510 1300