Warning: at net/core/dev.c:1699 skb_gso_segment+0x1df/0x2b0() [SOLVED]

cobradevil

New Member
Dec 8, 2010
19
0
1
Hi all,

i have spent a few days on this particular error. I would like to share the solution here.

A few weeks back i converted my BSD systems to run virtio. At first i thought it had no problems but last week i checked the proxmox server and came accross the error below.
After searching for the problem i found on launchpad a guy which converted his BSD systems back to using e1000 network card and the error disappeared. So i did the same and my Warnings are gone.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1014350

Regards,

William

Oct 21 06:29:35 proxmox kernel: ------------[ cut here ]------------
Oct 21 06:29:35 proxmox kernel: WARNING: at net/core/dev.c:1699 skb_gso_segment+0x1df/0x2b0() (Tainted: G W --------------- )
Oct 21 06:29:35 proxmox kernel: Hardware name: PowerEdge R815
Oct 21 06:29:35 proxmox kernel: bnx2: caps=(0x1949b3, 0x0) len=3345 data_len=0 ip_summed=0
Oct 21 06:29:35 proxmox kernel: Modules linked in: nfsd dlm configfs scsi_dh_rdac lpfc ipmi_si mptctl mptbase vzethdev vznetdev 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 xt_length xt_hl xt_tcpmss xt_TCPMSS iptable_mangle iptable_filter xt_multiport xt_limit xt_dscp vhost_net macvtap macvlan tun ipt_REJECT kvm_amd ip_tables kvm ipmi_devintf ipmi_msghandler dell_rbu ipv6 vzevent fuse dm_round_robin dm_multipath snd_pcsp tpm_tis tpm serio_raw tpm_bios snd_pcm snd_timer dcdbas k10temp snd amd64_edac_mod soundcore edac_core edac_mce_amd i2c_piix4 snd_page_alloc power_meter i2c_core ext4 jbd2 ext3 jbd mbcache sg mpt2sas ahci scsi_transport_fc igb scsi_transport_sas dca scsi_tgt raid_class bnx2 [last unloaded: lpfc]
Oct 21 06:29:35 proxmox kernel: Pid: 218066, comm: vhost-218055 veid: 0 Tainted: G W --------------- 2.6.32-14-pve #1
Oct 21 06:29:35 proxmox kernel: Call Trace:
Oct 21 06:29:35 proxmox kernel: <IRQ> [<ffffffff8106c608>] ? warn_slowpath_common+0x88/0xc0
Oct 21 06:29:35 proxmox kernel: [<ffffffff8106c6f6>] ? warn_slowpath_fmt+0x46/0x50
Oct 21 06:29:35 proxmox kernel: [<ffffffffa000615f>] ? bnx2_get_drvinfo+0x7f/0x90 [bnx2]
Oct 21 06:29:35 proxmox kernel: [<ffffffff8145ff7f>] ? dev_queue_xmit+0x19f/0x710
Oct 21 06:29:35 proxmox kernel: [<ffffffff8145addf>] ? skb_gso_segment+0x1df/0x2b0
Oct 21 06:29:35 proxmox kernel: [<ffffffff8145fa68>] ? dev_hard_start_xmit+0x198/0x510
Oct 21 06:29:35 proxmox kernel: [<ffffffff8147ab4a>] ? sch_direct_xmit+0x15a/0x1d0
Oct 21 06:29:35 proxmox kernel: [<ffffffff814602e8>] ? dev_queue_xmit+0x508/0x710
Oct 21 06:29:35 proxmox kernel: [<ffffffff814f6bcd>] ? br_dev_queue_push_xmit+0x5d/0xc0
Oct 21 06:29:35 proxmox kernel: [<ffffffff814f6c88>] ? br_forward_finish+0x58/0x60
Oct 21 06:29:35 proxmox kernel: [<ffffffff814f6d2a>] ? __br_forward+0x9a/0xc0
Oct 21 06:29:35 proxmox kernel: [<ffffffff814f6db5>] ? br_forward+0x65/0x70
Oct 21 06:29:35 proxmox kernel: [<ffffffff814f7da1>] ? br_handle_frame_finish+0x221/0x300
Oct 21 06:29:35 proxmox kernel: [<ffffffff814f8042>] ? br_handle_frame+0x1c2/0x270
Oct 21 06:29:35 proxmox kernel: [<ffffffff8145a7ce>] ? __netif_receive_skb+0x44e/0x730
Oct 21 06:29:35 proxmox kernel: [<ffffffff8145ab4a>] ? process_backlog+0x9a/0x100
Oct 21 06:29:35 proxmox kernel: [<ffffffff8145f2d3>] ? net_rx_action+0x103/0x2e0
Oct 21 06:29:35 proxmox kernel: [<ffffffff81075363>] ? __do_softirq+0x103/0x260
Oct 21 06:29:35 proxmox kernel: [<ffffffff8100c30c>] ? call_softirq+0x1c/0x30
Oct 21 06:29:35 proxmox kernel: <EOI> [<ffffffff8100df35>] ? do_softirq+0x65/0xa0
Oct 21 06:29:35 proxmox kernel: [<ffffffff8145f738>] ? netif_rx_ni+0x28/0x30
Oct 21 06:29:35 proxmox kernel: [<ffffffffa0152da9>] ? tun_sendmsg+0x1f9/0x4bc [tun]
Oct 21 06:29:35 proxmox kernel: [<ffffffffa021cf15>] ? handle_tx+0x275/0x5b0 [vhost_net]
Oct 21 06:29:35 proxmox kernel: [<ffffffffa021d285>] ? handle_tx_kick+0x15/0x20 [vhost_net]
Oct 21 06:29:35 proxmox kernel: [<ffffffffa021a4dc>] ? vhost_worker+0xbc/0x140 [vhost_net]
Oct 21 06:29:35 proxmox kernel: [<ffffffffa021a420>] ? vhost_worker+0x0/0x140 [vhost_net]
Oct 21 06:29:35 proxmox kernel: [<ffffffff81095606>] ? kthread+0x96/0xa0
Oct 21 06:29:35 proxmox kernel: [<ffffffff8100c20a>] ? child_rip+0xa/0x20
Oct 21 06:29:35 proxmox kernel: [<ffffffff81095570>] ? kthread+0x0/0xa0
Oct 21 06:29:35 proxmox kernel: [<ffffffff8100c200>] ? child_rip+0x0/0x20
Oct 21 06:29:35 proxmox kernel: ---[ end trace aa1c1582856ed468 ]---
 

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!