From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 199233] New: vxlan: hw csum failure
Date: Thu, 29 Mar 2018 11:39:34 -0700 [thread overview]
Message-ID: <20180329113934.05afa89b@xeon-e3> (raw)
Begin forwarded message:
Date: Wed, 28 Mar 2018 17:08:14 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 199233] New: vxlan: hw csum failure
https://bugzilla.kernel.org/show_bug.cgi?id=199233
Bug ID: 199233
Summary: vxlan: hw csum failure
Product: Networking
Version: 2.5
Kernel Version: 4.9.82
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: IPV4
Assignee: stephen@networkplumber.org
Reporter: asilva@wirelessmundi.com
Regression: No
when vxlan is encapsulated with ipsec (libreswan) i see lots of messages with
"hw csum failure".
my setup:
boxA [vxlan100] === ipsec/internet === [vxlan100]boxB
Both box have the same setup running debian stretch:
kernel 4.9.82
libreswan 3.23
iproute 4.9.0
NOTE: not sure if it duplicates issues #111331 and #198025, they seam very
similar... if so please forgive me.
Some errors in dmesg:
[76811.241149] vxlan100: hw csum failure
[76811.242677] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.9.0-6-amd64 #1
Debian 4.9.82-1+deb9u3
[76811.242685] Hardware name: AAEON UP-CHT01/UP-CHT01, BIOS UPC1BM0S 06/04/2016
[76811.242696] 0000000000000000 ffffffffa652e074 0000000000000000
ffff9b3b765b2500
[76811.242721] ffffffffa6706c4a ffff9b3b765b2500 ffffc8437fc10a08
0000000000000000
[76811.242738] 0000000000000074 ffffffffa677df2f ffff9b3b76860488
ffff9b3b765b2500
[76811.242756] Call Trace:
[76811.242766] <IRQ>
[76811.242792] [<ffffffffa652e074>] ? dump_stack+0x5c/0x78
[76811.242809] [<ffffffffa6706c4a>] ? __skb_gro_checksum_complete+0x9a/0xa0
[76811.242826] [<ffffffffa677df2f>] ? udp4_gro_receive+0xef/0x2d0
[76811.242839] [<ffffffffa6786418>] ? inet_gro_receive+0x1f8/0x2a0
[76811.242851] [<ffffffffa670a353>] ? dev_gro_receive+0x233/0x3c0
[76811.242864] [<ffffffffa670a513>] ? napi_gro_receive+0x33/0xe0
[76811.242889] [<ffffffffc0a18390>] ? gro_cell_poll+0x50/0x90 [vxlan]
[76811.242900] [<ffffffffa6709fe6>] ? net_rx_action+0x246/0x380
[76811.242915] [<ffffffffa6814dda>] ? __do_softirq+0x10a/0x29e
[76811.242930] [<ffffffffa627d7fe>] ? irq_exit+0xae/0xb0
[76811.242940] [<ffffffffa6813f0f>] ? do_IRQ+0x4f/0xd0
[76811.242952] [<ffffffffa6811c96>] ? common_interrupt+0x96/0x96
[76811.242956] <EOI>
[76811.242975] [<ffffffffa66d44a2>] ? cpuidle_enter_state+0xa2/0x2d0
[76811.242990] [<ffffffffa62ba404>] ? cpu_startup_entry+0x154/0x240
[76811.243006] [<ffffffffa6f3df62>] ? start_kernel+0x44b/0x46b
[76811.243017] [<ffffffffa6f3d120>] ? early_idt_handler_array+0x120/0x120
[76811.243027] [<ffffffffa6f3d408>] ? x86_64_start_kernel+0x14c/0x170
[76812.329058] br2: hw csum failure
[76812.330679] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.9.0-6-amd64 #1
Debian 4.9.82-1+deb9u3
[76812.330701] Hardware name: AAEON UP-CHT01/UP-CHT01, BIOS UPC1BM0S 06/04/2016
[76812.330729] 0000000000000000 ffffffffa652e074 ffff9b3b778c2400
ffff9b3b76561000
[76812.330751] ffffffffa66fb712 000000003ca7c358 ffff9b3b778c2400
ffffffffa6781805
[76812.330769] ffffffffa6a99c60 ffff9b3b778c2400 ffffffffa6edbb00
ffff9b3b78f44000
[76812.330787] Call Trace:
[76812.330796] <IRQ>
[76812.330819] [<ffffffffa652e074>] ? dump_stack+0x5c/0x78
[76812.330836] [<ffffffffa66fb712>] ? __skb_checksum_complete+0xb2/0xc0
[76812.330848] [<ffffffffa6781805>] ? icmp_rcv+0xa5/0x3a0
[76812.330879] [<ffffffffa674a853>] ? ip_local_deliver_finish+0x93/0x1c0
[76812.330913] [<ffffffffa674ab1b>] ? ip_local_deliver+0x6b/0xf0
[76812.330952] [<ffffffffa674a7c0>] ? ip_rcv_finish+0x400/0x400
[76812.330984] [<ffffffffa674ae20>] ? ip_rcv+0x280/0x3a0
[76812.330997] [<ffffffffa67fbbd1>] ? packet_rcv+0x41/0x430
[76812.331010] [<ffffffffa67091fd>] ? __netif_receive_skb_core+0x51d/0xa40
[76812.331024] [<ffffffffa62a2064>] ? try_to_wake_up+0x54/0x3c0
[76812.331037] [<ffffffffa670979f>] ? netif_receive_skb_internal+0x2f/0xa0
[76812.331091] [<ffffffffc03a5e9a>] ? xhci_queue_bulk_tx+0x26a/0x940
[xhci_hcd]
[76812.331148] [<ffffffffc0a3b6c2>] ? br_pass_frame_up+0xc2/0x160 [bridge]
[76812.331206] [<ffffffffc0a3b980>] ? br_handle_frame_finish+0x220/0x510
[bridge]
[76812.331235] [<ffffffffa62afa82>] ? enqueue_task_fair+0x82/0x940
[76812.331270] [<ffffffffc0a3bcb0>] ? br_handle_local_finish+0x40/0x40
[bridge]
[76812.331303] [<ffffffffc0a3be1b>] ? br_handle_frame+0x16b/0x2f0 [bridge]
[76812.331390] [<ffffffffc03325ad>] ? usb_hcd_submit_urb+0xad/0xaf0 [usbcore]
[76812.331420] [<ffffffffa66f2d3e>] ? __kmalloc_reserve.isra.35+0x2e/0x80
[76812.331433] [<ffffffffa6708fe8>] ? __netif_receive_skb_core+0x308/0xa40
[76812.331562] [<ffffffffc056ca22>] ? ieee80211_rx_napi+0x2f2/0x9c0 [mac80211]
[76812.331599] [<ffffffffa622e210>] ? recalibrate_cpu_khz+0x10/0x10
[76812.331620] [<ffffffffa670979f>] ? netif_receive_skb_internal+0x2f/0xa0
[76812.331631] [<ffffffffa670a598>] ? napi_gro_receive+0xb8/0xe0
[76812.331652] [<ffffffffc0a18390>] ? gro_cell_poll+0x50/0x90 [vxlan]
[76812.331663] [<ffffffffa6709fe6>] ? net_rx_action+0x246/0x380
[76812.331701] [<ffffffffa6814dda>] ? __do_softirq+0x10a/0x29e
[76812.331726] [<ffffffffa627d7fe>] ? irq_exit+0xae/0xb0
[76812.331736] [<ffffffffa6813f0f>] ? do_IRQ+0x4f/0xd0
[76812.331746] [<ffffffffa6811c96>] ? common_interrupt+0x96/0x96
[76812.331751] <EOI>
[76812.331770] [<ffffffffa66d44a2>] ? cpuidle_enter_state+0xa2/0x2d0
[76812.331812] [<ffffffffa62ba404>] ? cpu_startup_entry+0x154/0x240
[76812.331842] [<ffffffffa6f3df62>] ? start_kernel+0x44b/0x46b
[76812.331854] [<ffffffffa6f3d120>] ? early_idt_handler_array+0x120/0x120
[76812.331864] [<ffffffffa6f3d408>] ? x86_64_start_kernel+0x14c/0x170
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2018-03-29 18:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180329113934.05afa89b@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.