On Wed, Aug 20, 2014 at 07:08:27AM -0700, Craig Cook wrote: > We have been having problems with VMware 5.5. VMware are pointing fingers at > our storage (EMC). EMC point at VMware and the HBA's. We swapped HBA's with > a different vendor. Issue still happens. Anyone seen errors like this > before? > > This guest is Redhat 6.5 > > ESX hardware is Dell. > > > Aug 20 02:15:52 server01 kernel: [sched_delayed] sched: RT throttling > activated > Aug 20 02:16:01 server01 kernel: hrtimer: interrupt took 1318457321 ns > Aug 20 02:17:12 server01 kernel: BUG: soft lockup - CPU#0 stuck for 21s! > [watchdog/0:11]
BUG: soft lockup detected on CPU#N" messages running RHEL on VMWare https://access.redhat.com/solutions/21849 In Red Hat Enterprise Linux 6, "watchdog" kernel process is implemented and from RHEL-6.1, soft and hard lockups are detected using the "watchdog" process. This "watchdog" process uses "kernel.watchdog_thresh" kernel parameter as threshold limit. Hence the "kernel.softlockup_thresh" is deprecated from Red Hat Enterprise Linux 6.1 onwards. So the value can be set using the command below: echo [time] > /proc/sys/kernel/watchdog_thresh --- Soft lockup messages from Linux kernel running in an SMP-enabled virtual machine (1009996) http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1009996 Solution: The soft lockup messages are not kernel panics, and can be safely ignored. Some kernels allow you to adjust the soft lockup threshold by running the command: echo time > /proc/sys/kernel/softlockup_thresh Where time is the number of seconds after which a soft lockup is reported. The default is generally 10 seconds. HTH, -- Charles Polisher _______________________________________________ Tech mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
