Bug 1148612 - "hw csum failure" message flood after upgrading kernel to 3.16
Summary: "hw csum failure" message flood after upgrading kernel to 3.16
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: fedora-kernel-ethernet
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-01 21:30 UTC by Darrien Lambert
Modified: 2015-05-26 04:01 UTC (History)
6 users (show)

Fixed In Version: kernel-3.19.8-100.fc20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-05-26 03:55:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
The fix (2.18 KB, patch)
2015-05-16 18:51 UTC, Darrien Lambert
no flags Details | Diff

Description Darrien Lambert 2014-10-01 21:30:18 UTC
Description of problem:
-----------------------

After upgrading kernel packages to 3.16, messages file is quickly flooded with similar errors:

Oct  1 10:49:23 afftar kernel: [    9.558032] ppp0: hw csum failure
Oct  1 10:49:23 afftar kernel: [    9.558041] CPU: 1 PID: 1000 Comm: java Not tainted 3.16.3-200.fc20.x86_64 #1
Oct  1 10:49:23 afftar kernel: [    9.558044] Hardware name: System manufacturer System Product Name/M3N-H/HDMI, BIOS ASUS M3N-H/HDMI ACPI BIOS Revision 2701 09/27/2010
Oct  1 10:49:23 afftar kernel: [    9.558046]  0000000000000000 000000007cd0c47e ffff880127c43b60 ffffffff81707091
Oct  1 10:49:23 afftar kernel: [    9.558050]  ffff8800bb1a2000 ffff880127c43b78 ffffffff815f54ea ffff8800cafdbb00
Oct  1 10:49:23 afftar kernel: [    9.558053]  ffff880127c43ba8 ffffffff815ecd2a 1763efe1cafdbb00 ffff8800cafdbb00
Oct  1 10:49:23 afftar kernel: [    9.558056] Call Trace:
Oct  1 10:49:23 afftar kernel: [    9.558058]  <IRQ>  [<ffffffff81707091>] dump_stack+0x45/0x56
Oct  1 10:49:23 afftar kernel: [    9.558070]  [<ffffffff815f54ea>] netdev_rx_csum_fault+0x3a/0x40
Oct  1 10:49:23 afftar kernel: [    9.558075]  [<ffffffff815ecd2a>] __skb_checksum_complete+0xaa/0xb0
Oct  1 10:49:23 afftar kernel: [    9.558079]  [<ffffffff816874fc>] nf_ip_checksum+0xcc/0x100
Oct  1 10:49:23 afftar kernel: [    9.558095]  [<ffffffffa03fb573>] udp_error+0x103/0x200 [nf_conntrack]
Oct  1 10:49:23 afftar kernel: [    9.558100]  [<ffffffffa0507e30>] ? pppol2tp_seq_show+0x2d0/0x2d0 [l2tp_ppp]
Oct  1 10:49:23 afftar kernel: [    9.558106]  [<ffffffffa03f4873>] nf_conntrack_in+0xf3/0xab0 [nf_conntrack]
Oct  1 10:49:23 afftar kernel: [    9.558111]  [<ffffffff816357b0>] ? ip_rcv_finish+0x350/0x350
Oct  1 10:49:23 afftar kernel: [    9.558114]  [<ffffffff81635460>] ? inet_del_offload+0x40/0x40
Oct  1 10:49:23 afftar kernel: [    9.558119]  [<ffffffffa04312f2>] ipv4_conntrack_in+0x22/0x30 [nf_conntrack_ipv4]
Oct  1 10:49:23 afftar kernel: [    9.558122]  [<ffffffff8162c45a>] nf_iterate+0xaa/0xc0
Oct  1 10:49:23 afftar kernel: [    9.558125]  [<ffffffff81635460>] ? inet_del_offload+0x40/0x40
Oct  1 10:49:23 afftar kernel: [    9.558127]  [<ffffffff8162c4f4>] nf_hook_slow+0x84/0x140
Oct  1 10:49:23 afftar kernel: [    9.558130]  [<ffffffff81635460>] ? inet_del_offload+0x40/0x40
Oct  1 10:49:23 afftar kernel: [    9.558133]  [<ffffffff81635e88>] ip_rcv+0x2f8/0x3d0
Oct  1 10:49:23 afftar kernel: [    9.558136]  [<ffffffff815f82a2>] __netif_receive_skb_core+0x562/0x790
Oct  1 10:49:23 afftar kernel: [    9.558139]  [<ffffffff815f84e8>] __netif_receive_skb+0x18/0x60
Oct  1 10:49:23 afftar kernel: [    9.558142]  [<ffffffff815f91ce>] process_backlog+0x9e/0x150
Oct  1 10:49:23 afftar kernel: [    9.558145]  [<ffffffff815f8989>] net_rx_action+0x149/0x240
Oct  1 10:49:23 afftar kernel: [    9.558149]  [<ffffffff810924d5>] __do_softirq+0xf5/0x2a0
Oct  1 10:49:23 afftar kernel: [    9.558152]  [<ffffffff810928ed>] irq_exit+0xbd/0xd0
Oct  1 10:49:23 afftar kernel: [    9.558156]  [<ffffffff81711408>] do_IRQ+0x58/0xf0
Oct  1 10:49:23 afftar kernel: [    9.558159]  [<ffffffff8170f1ed>] common_interrupt+0x6d/0x6d

The issue does not happen with previous kernel 3.15.


Version-Release number of selected component (if applicable):
-------------------------------------------------------------
kernel-3.16.3-200.fc20.x86_64
kernel-modules-extra-3.16.3-200.fc20.x86_64
kernel-headers-3.16.3-200.fc20.x86_64
ppp-2.4.5-34.fc20.x86_64
xl2tpd-1.3.6-1.fc20.x86_64


How reproducible:
-----------------
Always when xl2tpd/ppp is connected.


Steps to Reproduce:


Actual results:


Expected results:


Additional info:

Comment 1 Justin M. Forbes 2014-11-13 16:04:10 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.17.2-200.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21.

If you experience different issues, please open a new bug report for those.

Comment 2 Darrien Lambert 2014-12-04 22:21:16 UTC
The issue still happens with 3.17.2-200.fc20

Comment 3 Fedora Kernel Team 2015-02-24 16:24:59 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.18.7-100.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21.

If you experience different issues, please open a new bug report for those.

Comment 4 Kristian McColm 2015-03-11 03:23:21 UTC
Occurring for me on Fedora 21 with these versions:

kernel-3.18.8-201.fc21.x86_64
xl2tpd-1.3.6-6.fc21.x86_64
strongswan-5.2.0-4.fc21.x86_64
ppp-2.4.7-6.fc21.x86_64


I have opened https://bugzilla.redhat.com/show_bug.cgi?id=1200635 against Fedora 21 but it looks the same.

Comment 5 Darrien Lambert 2015-03-11 07:38:17 UTC
Reverting Need Info status as the issue has been confirmed.

Comment 6 Fedora Kernel Team 2015-04-28 18:31:26 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.19.5-100.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21.

If you experience different issues, please open a new bug report for those.

Comment 7 Darrien Lambert 2015-04-29 07:52:33 UTC
Still happens with updated kernel.

Comment 8 Darrien Lambert 2015-05-16 18:48:16 UTC
There is a patch available for upstream: http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/patch/?id=91f5bd8437d39feecfee215e032f440b1faa25f8

I recommend to include it in the current fc20 kernel version.

Comment 9 Darrien Lambert 2015-05-16 18:51:48 UTC
Created attachment 1026270 [details]
The fix

Comment 10 Josh Boyer 2015-05-18 12:27:00 UTC
It already is in the F20 kernel.  Those two commits you referenced in comment #9 both went into the upstream stable 3.19.7 release.

That build is sitting in updates testing, so feel free to provide karma for it if you would like.

Comment 11 Fedora Update System 2015-05-18 17:25:30 UTC
kernel-3.19.7-100.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/FEDORA-2015-7911/kernel-3.19.7-100.fc20

Comment 12 Fedora Update System 2015-05-18 17:32:36 UTC
kernel-3.19.8-100.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/kernel-3.19.8-100.fc20

Comment 13 Darrien Lambert 2015-05-18 22:03:36 UTC
3.19.8-100.fc20.x86_64 resolves the bug for me. I will monitor the stability of new kernel a couple of days.

Comment 14 Fedora Update System 2015-05-19 16:25:11 UTC
Package kernel-3.19.8-100.fc20:
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-3.19.8-100.fc20'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-8518/kernel-3.19.8-100.fc20
then log in and leave karma (feedback).

Comment 15 Fedora Update System 2015-05-26 03:55:56 UTC
kernel-3.19.8-100.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.