Kernel panics on all kernels with 4 bonded nics

noway

New Member
Apr 25, 2014
7
0
1
After updating on the latest version we get kernel panic on heavy HP NC360T (Intel 82571EB chipset) nic load.
NC360T.jpg

Code:
root@proxmox:~# pveversion -v
proxmox-ve-2.6.32: 3.2-124 (running kernel: 2.6.32-28-pve)
pve-manager: 3.2-2 (running version: 3.2-2/82599a65)
pve-kernel-2.6.32-27-pve: 2.6.32-121
pve-kernel-2.6.32-28-pve: 2.6.32-124
pve-kernel-2.6.32-26-pve: 2.6.32-114
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-14
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-6
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1

Problem NOT solved with changing nic to broadcom.

ADDON:
Please read the 3-d message. We discovered the problem.
 
Last edited:
Re: Kernel panic on 3.2 with HP NC360T

You could fetch E1000 drivers from Intel website and compile module from source.
 
Re: Kernel panic on 3.2 with HP NC360T

We discovered the problem.

Kernel panics repeated on all our servers with different nics (broadcom and intel) where the network was build on bond with more than 1 nics (4 nics in our case).
As soon as we lowered the count of bonded nics to 1, kernel panics dissapered.

Facts:
1. Kernel panics (with panic sceen or just black screen with Scroll Lock & Caps Lock blinking) appear 1-2 times per week.
2. It does not matter what type of bond it is (lacp or balance-xore or other) - all crashes.
3. It does not matter what proxmox kernels to use (tried 2.6.32-27, 2.6.32-29, 3.10.0-2) - all crashes.
4. CentOS 6.5 with kernel 2.6.32-431.1.2.0.1.el6.x86_64 on the same hardware with heavy loaded lacp bond (4 nics) works perfectly.

----------

Update 11 Aug 2014:

After 2 months of headache I can state, that it was because of "new" nic drivers attached to custom proxmox kernel.
I deleted all e1000e,igb,ixgbe,netxtreme modules from Makefile, rebuilt the kernel and now all is working fine with default stock drivers. Uptime >1 month.
 
Last edited:

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!