Kernel Panic
- Thread starter rahs
- Start date
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
No effect. I also tried disabling tso (ethtool -K eth0 tso off)maybe can you try to disable gso ? ethtool -K eth0 gso off
pve-kernel-2.6.32-13-pve with same virtual environment works without any warnings or other problems
# pveversion -v
pve-manager: 2.3-7 (pve-manager/2.3/1fe64d18)
running kernel: 2.6.32-13-pve
proxmox-ve-2.6.32: 2.3-88
pve-kernel-2.6.32-13-pve: 2.6.32-72
pve-kernel-2.6.32-18-pve: 2.6.32-88
pve-kernel-2.6.32-17-pve: 2.6.32-83
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.4-4
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-36
qemu-server: 2.3-8
pve-firmware: 1.0-21
libpve-common-perl: 1.0-44
libpve-access-control: 1.0-25
libpve-storage-perl: 2.3-2
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: not correctly installed
vzquota: 3.1-1
pve-qemu-kvm: 1.3-18
ksm-control-daemon: 1.1-1
pve-kernel-2.6.32-13-pve with same virtual environment works without any warnings or other problems
About skb_gso, I found an old thread on proxmox
http://forum.proxmox.com/threads/11...v-c-1699-skb_gso_segment-0x1df-0x2b0()-SOLVED
But it was about freebsd guests.
(what os do you use in your vms ?)
About skb_gso, I found an old thread on proxmox
http://forum.proxmox.com/threads/116...0x2b0()-SOLVED
But it was about freebsd guests.
(what os do you use in your vms ?)
Debian 6.0.6
also found a similar problem here :
http://lists.openwall.net/netdev/2012/12/18/61
solution is disabling gso with ethtool. (this is strange that you have the error message with gso disabled ....)
Note that I have had network performance (spike latency) problems with debian squeeze 2.6.32 kernel since qemu 1.2. (seem to be a problem with virtio driver and qemu 1.2)
Not sure it's related, but i'm using 3.2 kernel from backports, and it's working fine
http://lists.openwall.net/netdev/2012/12/18/61
solution is disabling gso with ethtool. (this is strange that you have the error message with gso disabled ....)
Note that I have had network performance (spike latency) problems with debian squeeze 2.6.32 kernel since qemu 1.2. (seem to be a problem with virtio driver and qemu 1.2)
Not sure it's related, but i'm using 3.2 kernel from backports, and it's working fine
also found a similar problem here :
http://lists.openwall.net/netdev/2012/12/18/61
solution is disabling gso with ethtool. (this is strange that you have the error message with gso disabled ....)
My syslog don't have messages like skb_warn_bad_offload
Note that I have had network performance (spike latency) problems with debian squeeze 2.6.32 kernel since qemu 1.2. (seem to be a problem with virtio driver and qemu 1.2)
Not sure it's related, but i'm using 3.2 kernel from backports, and it's working fine
guest 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux - same problem
My syslog don't have messages like skb_warn_bad_offload
guest 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux - same problem
another similar bugreport on citrix xenserver
http://support.citrix.com/article/CTX133961
Code:
[COLOR=#35383D][FONT=Arial]Enabling Generic Receive Offload (GRO) on Physical Network Interfaces (PIF) can flood the log file with the following messages:[/FONT][/COLOR]WARNING: at net/core/dev.c:1594 skb_gso_segment+0x1a1/0x250()[COLOR=#35383D][FONT=Arial]. This is due to a bug that incorrectly clears the feature flags in the netback driver.
[/FONT][/COLOR]Do you have tried to disable GRO ?
Do you have tried to disable GRO ?
# ethtool -K eth0 gro off - same problem
# ethtool -K eth0 gro off - same problem
Just an idea, can you try to disable gso/gro on your bridge ?
I see on my test server that disabling on interface does not disable it on the bridge.
ethtool -K vmbrX gro/gso off
Just an idea, can you try to disable gso/gro on your bridge ?
I see on my test server that disabling on interface does not disable it on the bridge.
ethtool -K vmbrX gro/gso off
Yes, I tried disabling gro\gso on eth0 and vmbr0 simultaneously.
https://bugzilla.proxmox.com/show_bug.cgi?id=329