similar to: BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]

Displaying 20 results from an estimated 1100 matches similar to: "BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]"

2016 Aug 18
4
BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]
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). The details of last issues was reported to retrace.fedoraproject.org. ?Do you have a hint? [root at vmguest ~]# abrt-cli list id
2016 Dec 08
0
BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]
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
2017 Aug 08
0
BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]
Never saw this email....Did anyone get it?? anyone know how to fix this?thanks again. From: KM <info4km at yahoo.com> To: CentOS mailing list <centos at centos.org> Sent: Monday, August 7, 2017 11:26 AM Subject: Re: [CentOS] BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0] All,This happens on all of our CentOS 7 VMs.? but as stated in the email trail, the file
2016 Aug 18
2
BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]
> 2016-08-18 12:39 GMT-04:00 correomm <correomm at gmail.com>: > >> 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
2016 Aug 18
0
BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]
2016-08-18 12:39 GMT-04:00 correomm <correomm at gmail.com>: > 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
2018 Apr 24
2
BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]
Adam Tauno Williams wrote: > On Mon, 2017-08-07 at 15:26 +0000, KM wrote: >> All,This happens on all of our CentOS 7 VMs.? but as stated in the >> email trail, the file softlockup_thresh does not exist.? Should it be >> added?? What is the best way to get rid of this behavior. >> Thanks in advance and sorry if I missed something along the way.KM > > Yes, I see this
2018 Apr 24
0
BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]
On Mon, 2017-08-07 at 15:26 +0000, KM wrote: > All,This happens on all of our CentOS 7 VMs.? but as stated in the > email trail, the file softlockup_thresh does not exist.? Should it be > added?? What is the best way to get rid of this behavior. > Thanks in advance and sorry if I missed something along the way.KM Yes, I see this behavior as well. Never have found a solution - other
2018 Apr 24
0
BUG: soft lockup - CPU#0 stuck for 36s! [swapper/0:0]
On 24 April 2018 at 17:16, <m.roth at 5-cent.us> wrote: > Adam Tauno Williams wrote: >> On Mon, 2017-08-07 at 15:26 +0000, KM wrote: >>> All,This happens on all of our CentOS 7 VMs. but as stated in the >>> email trail, the file softlockup_thresh does not exist. Should it be >>> added? What is the best way to get rid of this behavior. >>>
2015 May 14
4
Delaying systemd reboot for a while
Hi, I'm in need of rebooting a server 1 minute after I give the command. I'm used to shutdown -r +1 which works as advertised. Now that shutdown is part of systemd <http://www.freedesktop.org/software/systemd/man/shutdown.html> and it is actually a link to it in CentOS 7, I've seen in the documentation
2012 Mar 01
1
Preventing hotplug devices in HVM guests
Hi there, Is there a way to prevent Windows HVM guests from seeing passed through devices like graphics cards as being ejectable? i.e. you pass through a graphics adapter to an HVM guest which happens to be Windows. Windows sees this as a device with hotplug capability. Therefore it shows up in "safely remove hardware" option in the windows system tray. VMWare provides an option to
2013 Dec 04
1
samba4.1.2: Allow cryptography algorithms compatible with Windows NT 4.0
Hi all, while fiddling with VmWare View without being able to join windows7 client to samba4 domain, we stumbled on the following article: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1028164 which says, should we run MS Windows 2008R2 AD, we should enable the "Allow cryptography algorithms compatible with Windows NT 4.0"
2014 Jul 17
0
NFS FILE ID not unique when exporting many brtfs subvolumes
Hi BTRFS community I have a problem using btrfs/nfs to store my vmware images. - following setup :(debian wheezy + backports) Linux sncubetest02 3.14-0.bpo.1-amd64 #1 SMP Debian 3.14.12-1~bpo70+1 (2014-07-13) x86_64 GNU/Linux > btrfs --version Btrfs v3.14.1 > btrfs fi show Label: none uuid: 8e37c8d0-e0ef-4857-ae9f-9a1be21901ed Total devices 2 FS bytes used 210.27GiB
2008 May 21
3
VMware and Time moved backwards
Hi, I followed the discussions regarding the "time moved backward" problem and the use of ntp in such cases. At our department we are running two dovecot servers within an vmware server environment, and unfortunately the timedrift (with ntpd active) exceeds sometimes up to 30 minutes virtual drift within 10 minutes realtime (mostly into future). This is due to some overcorrections
2011 Feb 13
2
Journal Aborts in VMware ESX (Filesystem Corruption)
I have several CentOS5 hosts in a VMware ESX 3.5.0 226117 environment using iSCSI storage. Recently we've begun to experience journal aborts resulting in remounted-read-only filesystems as well as other filesystem issues - I can unmount a filesystem and force a check with "fsck -f" and occasionally find errors. I've found -
2014 Nov 24
0
ESXi, CentOS 7 guest, CPU disabled
Hello, Over the last several weeks I've had a couple of CentOS 7 guests running in ESXi freeze because the CentOS halted the CPU. The problem is described here: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2000542 My CentOS 6 VMs are not misbehaving at all, nor are the Ubuntu VMs. Anyone else seeing this bug or know what to do
2014 Nov 25
0
ESXi, CentOS 7 guest, CPU disabled
On Mon, November 24, 2014 15:49, Jack Bailey wrote: > Hello, > > Over the last several weeks I've had a couple of CentOS 7 guests running > in ESXi freeze because the CentOS halted the CPU. The problem is > described here: > > http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2000542 > > My CentOS 6 VMs are not
2013 Aug 21
1
keeping correct time in guest
Hello, I know, often asked, often discussed .. No recommendation from Citrix. What is the better solution? 1) use ntp in the XEN host and synchronize the guests with the clock running on the control domain (independent_wallclock=0, what the default is) 2) or use ntp in host and guest (and independent_wallclock=1) I ask, because the XEN host (bare metal) has a more stable clock and if the ntp
2016 Aug 22
2
dm-0: WRITE SAME failed. Manually zeroing
Hello In a VM with CentOS 7, kernel 3.10.0-327.28.3.el7.x86_64, the console root login shows "[ 72.776182] dm-0: WRITE SAME failed. Manually zeroing". What is wrong? Regards, MM
2014 Jan 20
3
VMware restricting to 3GB RAM
Hi, I am running VMware player on CentOS 5.4 and its working fine. However it does not allow me to increase the RAM more than 3GB. ?It keeps throwing error stating- "Requested memory size is greater than allowed maximum of 3072 MB. Could not initiate memory hot plug."? I understand from few threads that 32bit OS has this kind of limitation but I am able to understand why I am seeing
2014 Feb 06
1
"BUG: soft lockup - CPU#n stuck for X s! [swapper:0]"
I just updated my quad-processor X64 machine (AMD Phenom(tm) II X4 945 Processor) to the latest CentOS 5 xen kernel (2.6.18-371.4.1.el5xen) and I am getting occasional "BUG: soft lockup - CPU#n stuck for X s! [swapper:0]" messages. I did some net searching, and found some bugzilla reports (https://bugzilla.redhat.com/show_bug.cgi?id=649519 and http://bugs.centos.org/view.php?id=4488),