From: Ben Greear <greearb@candelatech.com>
To: netdev <netdev@vger.kernel.org>
Subject: skb_warn_bad_offload related to IPv6 in 3.9.9+
Date: Thu, 11 Jul 2013 11:52:27 -0700 [thread overview]
Message-ID: <51DEFEEB.1080408@candelatech.com> (raw)
This kernel has local patches applied...but I don't think it has anything
that would cause this....
The wanlink module is something we added. It is now GPL, but code is
not upstream. I don't think it's in directly related to the splat though...
Only saw one splat, and system remains stable as far as we can tell.
------------[ cut here ]------------
WARNING: at /home/greearb/git/linux-3.9.dev.y/net/core/dev.c:2179 skb_warn_bad_offload+0xc2/0xcb()
Hardware name: X7DBU
e1000e: caps=(0x00000000700003a9, 0x0000000000000000) len=2942 data_len=1428 gso_size=1428 gso_type=16 ip_summed=1
Modules linked in: iptable_raw xt_CT bridge tcp_lp veth nls_utf8 cifs 8021q garp stp mrp llc nf_nat_ipv4 nf_nat fuse macvlan wanlink(O) pktgen nfsv3 nfs_acl
nfsv4 auth_rpcgss nfs fscache lockd sunrpc w83793 w83627hf hwmon_vid coretemp i5k_amb mperf kvm_intel i5000_edac edac_core iTCO_wdt ioatdma gpio_ich shpchp
iTCO_vendor_support e1000e lpc_ich kvm ptp dca pps_core i2c_i801 microcode pcspkr uinput ipv6 floppy radeon i2c_algo_bit hwmon drm_kms_helper ttm drm i2c_core
[last unloaded: iptable_nat]
Pid: 1587, comm: kwanlink/0 Tainted: G C O 3.9.9+ #104
Call Trace:
<IRQ> [<ffffffff81096291>] warn_slowpath_common+0x85/0x9f
[<ffffffff8109634e>] warn_slowpath_fmt+0x46/0x48
[<ffffffff815110d9>] skb_warn_bad_offload+0xc2/0xcb
[<ffffffff81512cd5>] __skb_gso_segment+0x34/0xa2
[<ffffffff81513233>] dev_hard_start_xmit+0x1c3/0x3b8
[<ffffffff8152de81>] sch_direct_xmit+0x75/0x154
[<ffffffff8151367b>] try_dev_queue_xmit+0x253/0x493
[<ffffffff815138cb>] dev_queue_xmit+0x10/0x12
[<ffffffffa0175707>] ip6_finish_output2+0x2cf/0x339 [ipv6]
[<ffffffffa017580f>] ip6_finish_output+0x9e/0xa3 [ipv6]
[<ffffffffa017376f>] ? __ipv6_neigh_lookup_noref+0x9a/0x9a [ipv6]
[<ffffffffa0176724>] ip6_output+0x8b/0x93 [ipv6]
[<ffffffffa01814b8>] ? ip6_pol_route+0x398/0x398 [ipv6]
[<ffffffffa01736d3>] dst_output+0xf/0x11 [ipv6]
[<ffffffffa0173778>] ip6_forward_finish+0x9/0xb [ipv6]
[<ffffffffa0175433>] NF_HOOK.clone.0+0x30/0x35 [ipv6]
[<ffffffffa01761d5>] ip6_forward+0x6b7/0x732 [ipv6]
[<ffffffffa017f3b3>] ? ip6_route_input+0xaa/0xb5 [ipv6]
[<ffffffffa01767a1>] ? ipv6_is_mld+0x75/0x75 [ipv6]
[<ffffffffa0176841>] ip6_rcv_finish+0xa0/0xa4 [ipv6]
[<ffffffffa0176bbf>] NF_HOOK.clone.1+0x4c/0x53 [ipv6]
[<ffffffffa0176ecf>] ipv6_rcv+0x309/0x342 [ipv6]
[<ffffffff8150fb2e>] __netif_receive_skb_core+0x4e7/0x558
[<ffffffff8150fbed>] __netif_receive_skb+0x4e/0x5e
[<ffffffff8150fcf8>] process_backlog+0xfb/0x1dc
[<ffffffff815123d3>] net_rx_action+0xc2/0x267
[<ffffffff810da28d>] ? ktime_get+0x4a/0x84
[<ffffffff8109da08>] __do_softirq+0x114/0x254
[<ffffffff815d299c>] call_softirq+0x1c/0x30
<EOI> [<ffffffff81011d3e>] do_softirq+0x46/0x83
[<ffffffff8109dcb1>] _local_bh_enable_ip+0x7a/0x9b
[<ffffffff8109dce0>] local_bh_enable_ip+0xe/0x10
[<ffffffff815cacb9>] _raw_spin_unlock_bh+0x24/0x26
[<ffffffffa0d63d67>] wle_tx_pkts+0x85a/0xe8f [wanlink]
[<ffffffff815c9106>] ? schedule_hrtimeout_range_clock+0xe1/0x108
[<ffffffffa0d64440>] do_task+0xa4/0x225 [wanlink]
[<ffffffffa0d64708>] wl_thread_task+0x147/0x1ed [wanlink]
[<ffffffffa0d645c1>] ? do_task+0x225/0x225 [wanlink]
[<ffffffff810b496d>] kthread+0xb5/0xbd
[<ffffffff810b48b8>] ? kthread_freezable_should_stop+0x60/0x60
[<ffffffff815d15ac>] ret_from_fork+0x7c/0xb0
[<ffffffff810b48b8>] ? kthread_freezable_should_stop+0x60/0x60
---[ end trace d5734e2ef6e4f61a ]---
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2013-07-11 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 18:52 Ben Greear [this message]
2013-07-11 21:37 ` skb_warn_bad_offload related to IPv6 in 3.9.9+ Ben Hutchings
2013-07-11 22:08 ` Ben Greear
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=51DEFEEB.1080408@candelatech.com \
--to=greearb@candelatech.com \
--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.