BUG: soft lockup - CPU#0 stuck for 67s! [ifenslave:1964]

lelik67

New Member
Nov 21, 2012
9
0
1
Freshly installed system via proxmox VE 2.x ISO.

When trying to reboot via terminal:
Code:
# reboot
system starts going down for reboot then hangs with the following message:
Deconfiguring network interfaces...BUG: soft lockup - CPU#0 stuck for 67s! [ifenslave:1964]

Three network cards installed:

Code:
# lspci | egrep -i --color 'network|ethernet'
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
03:01.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5701 Gigabit Ethernet (rev 15)
03:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5701 Gigabit Ethernet (rev 15)

eth0 bridged to vmbr0
eth1 and eth2 bonded and bridged to vmbr1

Code:
# cat /etc/network/interfaces

auto lo
iface lo inet loopback
iface eth0 inet manual
iface eth1 inet manual
iface eth2 inet manual

auto bond0
iface bond0 inet manual
    slaves eth1 eth2
    bond-mode balance-rr
    bond-miimon 100
    bond-downdelay 200
    bond-updelay 200

auto vmbr0
iface vmbr0 inet static
    bridge_stp off
    bridge_fd 0

auto vmbr1
iface vmbr1 inet static
    address 192.168.1.2
    netmask 255.255.255.0
    gateway 192.168.1.1
    bridge_ports bond0
    bridge_stp off
    bridge_fd 0
 
Code:
# pveversion -v
pve-manager: 2.2-31 (pve-manager/2.2/e94e95e9)
running kernel: 2.6.32-16-pve
proxmox-ve-2.6.32: 2.2-82
pve-kernel-2.6.32-16-pve: 2.6.32-82
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.93-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.9-1
pve-cluster: 1.0-33
qemu-server: 2.0-69
pve-firmware: 1.0-21
libpve-common-perl: 1.0-39
libpve-access-control: 1.0-25
libpve-storage-perl: 2.0-36
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.2-7
ksm-control-daemon: 1.1-1
 
Are you sure? It's marked as resolved plus kernel is rhel6-2.6.32_042stabXXX
I have a box with identical hardware and CentOS 6.3 + openvz kernel 2.6.32-042stab062.2 = no such problem.
 
That bug is marked as solved because is divided in much more bugtracks. Is not only 1 bug. Is this the reason that I say is crazy :)
At this moment, the OVZ 2.6.32 kernel is more stable than 6 months ago than the first bug in this term was reported,
But your error is the same.
I dont know how to provide you more help. Sorry.
Regards!
 
After futher investigation it looks like the problem starts when bridging a bond device.

The first configuration gives no error:
Code:
# network interface settings
auto lo
iface lo inet loopback

iface eth0 inet manual
iface eth1 inet manual
iface eth2 inet manual

auto bond0
iface bond0 inet manual
        slaves eth1 eth2
        bond_miimon 100
        bond_mode balance-xor

auto vmbr0
iface vmbr0 inet static
        address  192.168.1.1
        netmask  255.255.255.0
        gateway  192.168.1.3
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0
the second configuration gives the error described above:
Code:
# network interface settings
auto lo
iface lo inet loopback

iface eth0 inet manual
iface eth1 inet manual
iface eth2 inet manual

auto bond0
iface bond0 inet manual
        slaves eth1 eth2
        bond_miimon 100
        bond_mode balance-xor

auto vmbr0
iface vmbr0 inet static
        address  192.168.1.1
        netmask  255.255.255.0
        gateway  192.168.1.3
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

auto vmbr1
iface vmbr1 inet manual
        address  192.168.1.2
        netmask  255.255.255.0
        gateway  192.168.1.3
        bridge_ports bond0
        bridge_stp off
        bridge_fd 0

I have a faint suspicion that disabling ipv6 for bonding would fix a problem.

Anybody knows how to disable ipv6 on proxmox?
 
Last edited:
Maybe you should have a look on your kernel modules/drivers?
I only know this problem from my desktop machine at home with debian sqeeze + nvidia drivers. After wakeup from suspend i get a "GPU has fallen off the bus", followed by periodic "BUG: soft lockup - CPU#0 stuck for 61s!" but sometimes with different entries at the end of the message [....:xxx]. The system responds less and less until i have to hard-reset it, producing more and more syslog entries with the mentioned message.

I haven't investigated this any further yet, but in my case it's definately the nvidia driver causing other programs to lock up the CPU even if not named at the error message! But it's the only constant entry at the traceback list appearing several times plus the problem disappears when switching back to older/other drivers.
Maybe in your case it's also a driver/module causing this? Have a look at the traceback list in the syslog if there is any process appearing very often and after every lockup!
 
You are right. I narrowed it down to tg3 NIC driver (Broadcom chip gigabit cards).

Apparently a known open bug. No resolution.
 
Last edited:
I was able to download new driver from Broadcom web site (v. 3.124) and built it from source. The driver works very well with no lockups.
 
Last edited:
Message from syslogd@pveabs1 at Dec 5 05:02:01 ...
kernel:BUG: soft lockup - CPU#3 stuck for 67s! [php:160510]


Message from syslogd@pveabs1 at Dec 5 05:02:49 ...
kernel:BUG: soft lockup - CPU#1 stuck for 67s! [kvm:699902]


Message from syslogd@pveabs1 at Dec 5 05:03:25 ...
kernel:BUG: soft lockup - CPU#3 stuck for 67s! [php:160510]


Message from syslogd@pveabs1 at Dec 5 05:04:13 ...
kernel:BUG: soft lockup - CPU#1 stuck for 67s! [kvm:699902]


Message from syslogd@pveabs1 at Dec 5 05:04:49 ...
kernel:BUG: soft lockup - CPU#3 stuck for 67s! [php:160510]


Message from syslogd@pveabs1 at Dec 5 05:05:37 ...
kernel:BUG: soft lockup - CPU#1 stuck for 67s! [kvm:699902]


Message from syslogd@pveabs1 at Dec 5 05:06:13 ...
kernel:BUG: soft lockup - CPU#3 stuck for 67s! [php:160510]
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!