Kernel Warning

mattym

Renowned Member
Mar 8, 2011
30
0
71
hi,

any ideas why im getting this every minute in my syslog -

Apr 5 01:18:06 pm4 kernel: ------------[ cut here ]------------
Apr 5 01:18:06 pm4 kernel: WARNING: at net/core/dev.c:1711 skb_gso_segment+0x1e2/0x2c0() (Tainted: G W --------------- )
Apr 5 01:18:06 pm4 kernel: Hardware name: ProLiant BL460c G6
Apr 5 01:18:06 pm4 kernel: tun: caps=(0x80000000, 0x0) len=2788 data_len=1368 ip_summed=1
Apr 5 01:18:06 pm4 kernel: Modules linked in: 8021q garp vzethdev vznetdev pio_nfs pio_direct pfmt_raw pfmt_ploop1 ploop simfs vzrst nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 vzcpt nfs lockd fscache nfs_acl auth_rpcgss sunrpc nf_conntrack vzdquota vzmon vzdev ip6t_REJECT ip6table_mangle ip6table_filter ip6_tables mptctl mptbase xt_length xt_hl xt_tcpmss xt_TCPMSS iptable_mangle iptable_filter sg vhost_net macvtap xt_multiport macvlan tun xt_limit xt_dscp kvm_intel ipt_REJECT kvm ip_tables ipmi_devintf vzevent ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr ipv6 iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi fuse radeon ttm snd_pcsp snd_pcm drm_kms_helper i7core_edac edac_core drm i2c_algo_bit hpilo ipmi_si ipmi_msghandler hpwdt i2c_core shpchp snd_timer snd soundcore snd_page_alloc tpm_tis tpm tpm_bios power_meter serio_raw ext3 jbd mbcache hpsa bnx2 bnx2x mdio [last unloaded: scsi_wait_scan]
Apr 5 01:18:06 pm4 kernel: Pid: 0, comm: swapper veid: 0 Tainted: G W --------------- 2.6.32-19-pve #1
Apr 5 01:18:06 pm4 kernel: Call Trace:
Apr 5 01:18:06 pm4 kernel: <IRQ> [<ffffffff8106d6c8>] ? warn_slowpath_common+0x88/0xc0
Apr 5 01:18:06 pm4 kernel: [<ffffffff8106d7b6>] ? warn_slowpath_fmt+0x46/0x50
Apr 5 01:18:06 pm4 kernel: [<ffffffff814c09d5>] ? inet_gso_segment+0xf5/0x270
Apr 5 01:18:06 pm4 kernel: [<ffffffff81454dd2>] ? skb_gso_segment+0x1e2/0x2c0
Apr 5 01:18:06 pm4 kernel: [<ffffffff8105a632>] ? default_wake_function+0x12/0x20
Apr 5 01:18:06 pm4 kernel: [<ffffffff8145972e>] ? dev_hard_start_xmit+0x19e/0x510
Apr 5 01:18:06 pm4 kernel: [<ffffffff8147467a>] ? sch_direct_xmit+0x15a/0x1d0
Apr 5 01:18:06 pm4 kernel: [<ffffffff81459fb8>] ? dev_queue_xmit+0x518/0x730
Apr 5 01:18:06 pm4 kernel: [<ffffffff814ef9d0>] ? br_dev_queue_push_xmit+0x60/0xc0
Apr 5 01:18:06 pm4 kernel: [<ffffffff814efa88>] ? br_forward_finish+0x58/0x60
Apr 5 01:18:06 pm4 kernel: [<ffffffff814efb2a>] ? __br_forward+0x9a/0xc0
Apr 5 01:18:06 pm4 kernel: [<ffffffff814efbb5>] ? br_forward+0x65/0x70
Apr 5 01:18:06 pm4 kernel: [<ffffffff814f0b71>] ? br_handle_frame_finish+0x221/0x300
Apr 5 01:18:06 pm4 kernel: [<ffffffff814f0e12>] ? br_handle_frame+0x1c2/0x270
Apr 5 01:18:06 pm4 kernel: [<ffffffff814fec50>] ? vlan_hwaccel_do_receive+0x70/0x130
Apr 5 01:18:06 pm4 kernel: [<ffffffff814547ae>] ? __netif_receive_skb+0x45e/0x750
Apr 5 01:18:06 pm4 kernel: [<ffffffff81456b48>] ? netif_receive_skb+0x58/0x60
Apr 5 01:18:06 pm4 kernel: [<ffffffff81456c60>] ? napi_skb_finish+0x50/0x70
Apr 5 01:18:06 pm4 kernel: [<ffffffff814ff394>] ? vlan_gro_receive+0x84/0xa0
Apr 5 01:18:06 pm4 kernel: [<ffffffffa0046a10>] ? bnx2x_rx_int+0x1110/0x16a0 [bnx2x]
Apr 5 01:18:06 pm4 kernel: [<ffffffff81250407>] ? ftrace_raw_reg_event_block_bio_bounce+0x17/0x20
Apr 5 01:18:06 pm4 kernel: [<ffffffff8136022f>] ? loop_set_status+0x20f/0x330
Apr 5 01:18:06 pm4 kernel: [<ffffffffa004704b>] ? bnx2x_poll+0xab/0x300 [bnx2x]
Apr 5 01:18:06 pm4 kernel: [<ffffffff81458f83>] ? net_rx_action+0x103/0x2f0
Apr 5 01:18:06 pm4 kernel: [<ffffffff81076573>] ? __do_softirq+0x103/0x260
Apr 5 01:18:06 pm4 kernel: [<ffffffff8100c2ac>] ? call_softirq+0x1c/0x30
Apr 5 01:18:06 pm4 kernel: [<ffffffff8100def5>] ? do_softirq+0x65/0xa0
Apr 5 01:18:06 pm4 kernel: [<ffffffff8107639d>] ? irq_exit+0xcd/0xd0
Apr 5 01:18:06 pm4 kernel: [<ffffffff81526545>] ? do_IRQ+0x75/0xf0
Apr 5 01:18:06 pm4 kernel: [<ffffffff8100ba93>] ? ret_from_intr+0x0/0x11
Apr 5 01:18:06 pm4 kernel: <EOI> [<ffffffff812d1dbe>] ? intel_idle+0xde/0x170
Apr 5 01:18:06 pm4 kernel: [<ffffffff812d1da1>] ? intel_idle+0xc1/0x170
Apr 5 01:18:06 pm4 kernel: [<ffffffff81421827>] ? cpuidle_idle_call+0xa7/0x140
Apr 5 01:18:06 pm4 kernel: [<ffffffff8100a023>] ? cpu_idle+0xb3/0x110
Apr 5 01:18:06 pm4 kernel: [<ffffffff81505555>] ? rest_init+0x85/0x90
Apr 5 01:18:06 pm4 kernel: [<ffffffff81c2ef6e>] ? start_kernel+0x412/0x41e
Apr 5 01:18:06 pm4 kernel: [<ffffffff81c2e33a>] ? x86_64_start_reservations+0x125/0x129
Apr 5 01:18:06 pm4 kernel: [<ffffffff81c2e438>] ? x86_64_start_kernel+0xfa/0x109
Apr 5 01:18:06 pm4 kernel: ---[ end trace d4855a519f6804c0 ]---
Apr 5 01:18:06 pm4 kernel: ------------[ cut here ]------------
Apr 5 01:18:06 pm4 kernel: WARNING: at net/core/dev.c:1711 skb_gso_segment+0x1e2/0x2c0() (Tainted: G W --------------- )
Apr 5 01:18:06 pm4 kernel: Hardware name: ProLiant BL460c G6
Apr 5 01:18:06 pm4 kernel: tun: caps=(0x80000000, 0x0) len=2788 data_len=1368 ip_summed=1
Apr 5 01:18:06 pm4 kernel: Modules linked in: 8021q garp vzethdev vznetdev pio_nfs pio_direct pfmt_raw pfmt_ploop1 ploop simfs vzrst nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 vzcpt nfs lockd fscache nfs_acl auth_rpcgss sunrpc nf_conntrack vzdquota vzmon vzdev ip6t_REJECT ip6table_mangle ip6table_filter ip6_tables mptctl mptbase xt_length xt_hl xt_tcpmss xt_TCPMSS iptable_mangle iptable_filter sg vhost_net macvtap xt_multiport macvlan tun xt_limit xt_dscp kvm_intel ipt_REJECT kvm ip_tables ipmi_devintf vzevent ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr ipv6 iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi fuse radeon ttm snd_pcsp snd_pcm drm_kms_helper i7core_edac edac_core drm i2c_algo_bit hpilo ipmi_si ipmi_msghandler hpwdt i2c_core shpchp snd_timer snd soundcore snd_page_alloc tpm_tis tpm tpm_bios power_meter serio_raw ext3 jbd mbcache hpsa bnx2 bnx2x mdio [last unloaded: scsi_wait_scan]
Apr 5 01:18:06 pm4 kernel: Pid: 0, comm: swapper veid: 0 Tainted: G W --------------- 2.6.32-19-pve #1
Apr 5 01:18:06 pm4 kernel: Call Trace:
Apr 5 01:18:06 pm4 kernel: <IRQ> [<ffffffff8106d6c8>] ? warn_slowpath_common+0x88/0xc0
Apr 5 01:18:06 pm4 kernel: [<ffffffff8106d7b6>] ? warn_slowpath_fmt+0x46/0x50
Apr 5 01:18:06 pm4 kernel: [<ffffffff81454dd2>] ? skb_gso_segment+0x1e2/0x2c0
Apr 5 01:18:06 pm4 kernel: [<ffffffff8105a632>] ? default_wake_function+0x12/0x20
Apr 5 01:18:06 pm4 kernel: [<ffffffff8145972e>] ? dev_hard_start_xmit+0x19e/0x510
Apr 5 01:18:06 pm4 kernel: [<ffffffff8147467a>] ? sch_direct_xmit+0x15a/0x1d0
Apr 5 01:18:06 pm4 kernel: [<ffffffff81459fb8>] ? dev_queue_xmit+0x518/0x730
Apr 5 01:18:06 pm4 kernel: [<ffffffff814ef9d0>] ? br_dev_queue_push_xmit+0x60/0xc0
Apr 5 01:18:06 pm4 kernel: [<ffffffff814efa88>] ? br_forward_finish+0x58/0x60
Apr 5 01:18:06 pm4 kernel: [<ffffffff814efb2a>] ? __br_forward+0x9a/0xc0
Apr 5 01:18:06 pm4 kernel: [<ffffffff814efbb5>] ? br_forward+0x65/0x70
Apr 5 01:18:06 pm4 kernel: [<ffffffff814f0b71>] ? br_handle_frame_finish+0x221/0x300
Apr 5 01:18:06 pm4 kernel: [<ffffffff814f0e12>] ? br_handle_frame+0x1c2/0x270
Apr 5 01:18:06 pm4 kernel: [<ffffffff814fec50>] ? vlan_hwaccel_do_receive+0x70/0x130
Apr 5 01:18:06 pm4 kernel: [<ffffffff814547ae>] ? __netif_receive_skb+0x45e/0x750
Apr 5 01:18:06 pm4 kernel: [<ffffffff81456b48>] ? netif_receive_skb+0x58/0x60
Apr 5 01:18:06 pm4 kernel: [<ffffffff81456c60>] ? napi_skb_finish+0x50/0x70
Apr 5 01:18:06 pm4 kernel: [<ffffffff814ff394>] ? vlan_gro_receive+0x84/0xa0
Apr 5 01:18:06 pm4 kernel: [<ffffffffa0046a10>] ? bnx2x_rx_int+0x1110/0x16a0 [bnx2x]
Apr 5 01:18:06 pm4 kernel: [<ffffffff81250409>] ? ftrace_raw_reg_event_block_bio_bounce+0x19/0x20
Apr 5 01:18:06 pm4 kernel: [<ffffffff81360230>] ? loop_set_status+0x210/0x330
Apr 5 01:18:06 pm4 kernel: [<ffffffffa004704b>] ? bnx2x_poll+0xab/0x300 [bnx2x]
Apr 5 01:18:06 pm4 kernel: [<ffffffff81458f83>] ? net_rx_action+0x103/0x2f0
Apr 5 01:18:06 pm4 kernel: [<ffffffff81076573>] ? __do_softirq+0x103/0x260
Apr 5 01:18:06 pm4 kernel: [<ffffffff8100c2ac>] ? call_softirq+0x1c/0x30
Apr 5 01:18:06 pm4 kernel: [<ffffffff8100def5>] ? do_softirq+0x65/0xa0
Apr 5 01:18:06 pm4 kernel: [<ffffffff8107639d>] ? irq_exit+0xcd/0xd0
Apr 5 01:18:06 pm4 kernel: [<ffffffff81526545>] ? do_IRQ+0x75/0xf0
Apr 5 01:18:06 pm4 kernel: [<ffffffff8100ba93>] ? ret_from_intr+0x0/0x11
Apr 5 01:18:06 pm4 kernel: <EOI> [<ffffffff812d1dbe>] ? intel_idle+0xde/0x170
Apr 5 01:18:06 pm4 kernel: [<ffffffff812d1da1>] ? intel_idle+0xc1/0x170
Apr 5 01:18:06 pm4 kernel: [<ffffffff81421827>] ? cpuidle_idle_call+0xa7/0x140
Apr 5 01:18:06 pm4 kernel: [<ffffffff8100a023>] ? cpu_idle+0xb3/0x110
Apr 5 01:18:06 pm4 kernel: [<ffffffff81505555>] ? rest_init+0x85/0x90
Apr 5 01:18:06 pm4 kernel: [<ffffffff81c2ef6e>] ? start_kernel+0x412/0x41e
Apr 5 01:18:06 pm4 kernel: [<ffffffff81c2e33a>] ? x86_64_start_reservations+0x125/0x129
Apr 5 01:18:06 pm4 kernel: [<ffffffff81c2e438>] ? x86_64_start_kernel+0xfa/0x109
Apr 5 01:18:06 pm4 kernel: ---[ end trace d4855a519f6804c1 ]---

pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
running kernel: 2.6.32-19-pve
proxmox-ve-2.6.32: 2.3-93
pve-kernel-2.6.32-19-pve: 2.6.32-93
pve-kernel-2.6.32-18-pve: 2.6.32-88
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-18
pve-firmware: 1.0-21
libpve-common-perl: 1.0-49
libpve-access-control: 1.0-26
libpve-storage-perl: 2.3-6
vncterm: 1.0-3
vzctl: 4.0-1pve2
vzprocps: 2.0.11-2
vzquota: 3.1-1
pve-qemu-kvm: 1.4-8
ksm-control-daemon: 1.1-1

if its to do with bnx2x I thought that was fixed in the latest kernel?

tried turning off GSO, TSO on all interfaces with ethtool and it hasnt done anything, the log is still filling up. There is a single CentOS 6.4 guest VM. I have VLANs defined on Proxmox but none on the guest VM.

thanks

matt
 
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!