From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 198025] New: <unknown>: hw csum failure
Date: Wed, 29 Nov 2017 10:25:03 -0800 [thread overview]
Message-ID: <20171129102503.07b4b2ab@xeon-e3> (raw)
Looks like a virtio bug
Begin forwarded message:
Date: Wed, 29 Nov 2017 08:16:45 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 198025] New: <unknown>: hw csum failure
https://bugzilla.kernel.org/show_bug.cgi?id=198025
Bug ID: 198025
Summary: <unknown>: hw csum failure
Product: Networking
Version: 2.5
Kernel Version: 4.8.13-1.el6.elrepo.x86_64
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: svimik@gmail.com
Regression: No
Created attachment 260919
--> https://bugzilla.kernel.org/attachment.cgi?id=260919&action=edit
oops message
<unknown>: hw csum failure
CPU: 3 PID: 2741 Comm: openvpn Not tainted 4.8.13-1.el6.elrepo.x86_64 #1
Hardware name: /DH61WW, BIOS BEH6110H.86A.0034.2011.1018.1937
10/18/2011
0000000000000000 ffff880119a2faa8 ffffffff8134d2ef 0000000000000001
000000029083b90d 0000000000000000 ffff88008e629400 ffff880119a2fac8
ffffffff816602f2 ffff880119a2fdc8 0000000000000000 ffff880119a2fb08
Call Trace:
[<ffffffff8134d2ef>] dump_stack+0x67/0x98
[<ffffffff816602f2>] netdev_rx_csum_fault+0x42/0x50
[<ffffffff816563d4>] skb_copy_and_csum_datagram_msg+0xc4/0xf0
[<ffffffff816dd186>] udp_recvmsg+0x286/0x510
[<ffffffff816e67e1>] inet_recvmsg+0x51/0x90
[<ffffffff8164642a>] sock_recvmsg+0x4a/0x60
[<ffffffff8164700b>] ___sys_recvmsg+0xeb/0x210
[<ffffffff810af434>] ? try_to_wake_up+0x54/0x260
[<ffffffff811079a1>] ? get_futex_key+0x251/0x3f0
[<ffffffff81240cec>] ? __fget_light+0x2c/0x70
----cut----
A full message of this oops can be found in attachment. Message was received
using netconsole.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2017-11-29 18:25 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=20171129102503.07b4b2ab@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).