Not sure if this was the last email on this. If not ignore me. However I found a post for new operating systems that says to set the watchdog_thresh value instead of softlockup_thresh.
http://askubuntu.com/questions/592412/why-is-there-no-proc-sys-kernel-softlockup-thresh
this is an Ubuntu post, but on my CentOS 7 system this parameter exists, and softlockup_thresh does not. I have set it but I will need to see if I still get the CPU lock up messages on my VM.
I hope this helps.KM
From: correomm <correomm@xxxxxxxxx>
To: CentOS mailing list <centos@xxxxxxxxxx>
Sent: Thursday, August 18, 2016 1:50 PM
Subject: Re: BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]
Yes, I tried it, but does not exists:
vmguest # cat /proc/sys/kernel/softlockup_thresh
cat: /proc/sys/kernel/softlockup_thresh: No such file or directory
On Thu, Aug 18, 2016 at 2:06 PM, Carlos A. Carnero Delgado <
carloscarnero@xxxxxxxxx> wrote:
> 2016-08-18 12:39 GMT-04:00 correomm <correomm@xxxxxxxxx>:
>
> > This bug is reported only on the VM's with CentOS 7 running on on VMware
> > ESXi 5.1.
> > The vSphere performance graph shows high CPU consume and disk activity
> only
> > on VM's with CentOS 7. Sometimes I can not connect remotely with ssh
> > (timeout error).
> >
>
> I'm also seeing those errors in several servers, running under 5.5.
> Currently investigating if this
> <https://kb.vmware.com/selfservice/microsites/search.
> do?language=en_US&cmd=displayKC&externalId=1009996>
> has anything to do (the resource overcommit bit).
>
> HTH,
> Carlos.
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> https://lists.centos.org/mailman/listinfo/centos
>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
