From: Andreas Schwab <schwab@linux-m68k.org>
To: linuxppc-dev@ozlabs.org
Subject: eth0: hw csum failure
Date: Sat, 23 Nov 2013 01:44:00 +0100 [thread overview]
Message-ID: <87d2ls54mn.fsf@igel.home> (raw)
I get a lot of "eth0: hw csum failure" with 3.13-rc1 on my G5.
eth0: hw csum failure
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.13.0-rc1 #1
Call Trace:
[c00000000ffef1d0] [c00000000000f97c] .show_stack+0x60/0x14c (unreliable)
[c00000000ffef2a0] [c00000000069fad8] .dump_stack+0x80/0xa0
[c00000000ffef320] [c000000000552bc0] .netdev_rx_csum_fault+0x4c/0x58
[c00000000ffef3a0] [c000000000546f88] .__skb_checksum_complete_head+0x54/0x78
[c00000000ffef420] [c0000000005f1118] .nf_ip_checksum+0xf4/0x100
[c00000000ffef4b0] [c00000000058e520] .udp_error+0x198/0x210
[c00000000ffef560] [c000000000587694] .nf_conntrack_in+0x14c/0xa20
[c00000000ffef690] [c0000000005f195c] .ipv4_conntrack_in+0x24/0x38
[c00000000ffef700] [c00000000058343c] .nf_iterate+0x64/0xb4
[c00000000ffef7c0] [c00000000058353c] .nf_hook_slow+0xb0/0x188
[c00000000ffef890] [c00000000059ea9c] .ip_rcv+0x390/0x3f0
[c00000000ffef930] [c000000000551578] .__netif_receive_skb_core+0x8c4/0x964
[c00000000ffefa30] [c000000000551c38] .netif_receive_skb+0xb0/0x130
[c00000000ffefae0] [c000000000552740] .napi_gro_receive+0x50/0xc0
[c00000000ffefb60] [c000000000447754] .gem_poll+0x10f0/0x1328
[c00000000ffefcc0] [c000000000552418] .net_rx_action+0xd8/0x240
[c00000000ffefd90] [c00000000004dfc4] .__do_softirq+0x158/0x2c0
[c00000000ffefea0] [c00000000004e448] .irq_exit+0x6c/0xc4
[c00000000ffeff10] [c00000000000ce14] .__do_irq+0xec/0xf8
[c00000000ffeff90] [c000000000019474] .call_do_irq+0x14/0x24
[c0000001f615ba30] [c00000000000cea0] .do_IRQ+0x80/0xc0
[c0000001f615bac0] [c0000000000024b8] hardware_interrupt_common+0x138/0x180
--- Exception: 501 at .arch_cpu_idle+0x78/0x124
LR = .arch_cpu_idle+0x78/0x124
[c0000001f615bdb0] [c0000000000a3af4] .rcu_idle_enter+0x98/0xb8 (unreliable)
[c0000001f615be30] [c00000000009a978] .cpu_startup_entry+0x110/0x1a0
[c0000001f615bee0] [c00000000001f14c] .start_secondary+0x288/0x290
[c0000001f615bf90] [c0000000000087fc] .start_secondary_prolog+0x10/0x14
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next reply other threads:[~2013-11-23 0:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-23 0:44 Andreas Schwab [this message]
2013-11-23 21:17 ` eth0: hw csum failure Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2018-06-14 19:43 Mathieu Malaterre
2011-12-05 12:51 Pavel Mateja
2011-12-05 16:17 ` Stephen Hemminger
2011-12-05 16:18 ` Stephen Hemminger
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=87d2ls54mn.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=linuxppc-dev@ozlabs.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.