Bug 62171 - Kernel Crash In local_bh_enable in case of Vlan Tagged ICMP Packets
Summary: Kernel Crash In local_bh_enable in case of Vlan Tagged ICMP Packets
Status: CLOSED WILL_NOT_FIX
Alias: None
Product: Networking
Classification: Unclassified
Component: Other (show other bugs)
Hardware: Mips64 Linux
: P1 high
Assignee: Stephen Hemminger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-26 13:22 UTC by Gautam Acharya
Modified: 2013-11-04 11:50 UTC (History)
2 users (show)

See Also:
Kernel Version: Linux 2.6.27.18
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Gautam Acharya 2013-09-26 13:22:42 UTC
Hi,

Kernel In based on Linux Version 2.6.27.18, Cavium octeon Board is used. In SMP mode but one one cpu is loaded with Linux Kernel.

Its getting crashed in WARN_ON_ONCE in _local_bh_enable_ip called from local_bh_enable.

Please Find Below Stack Trace Regarding this Crash:

[<ffffffff81154108>] warn_on_slowpath+0x58/0x90

[<ffffffff8115bd20>] local_bh_enable+0x88/0xf8

[<ffffffff81344a44>] dev_queue_xmit+0x144/0x688

[<ffffffff81301f04>] bond_dev_queue_xmit+0x44/0x178

[<ffffffff81302408>] bond_xmit_activebackup+0xb0/0xe8

[<ffffffff81344ea4>] dev_queue_xmit+0x5a4/0x688

[<ffffffff813d59b4>] vlan_dev_hwaccel_hard_start_xmit+0x8c/0xa0

[<ffffffff81344ea4>] dev_queue_xmit+0x5a4/0x688

[<ffffffff81377cbc>] ip_push_pending_frames+0x37c/0x4c0

[<ffffffff813a0768>] icmp_reply+0x170/0x290

[<ffffffff813a0a58>] icmp_echo+0x58/0x68

[<ffffffff813a11b4>] icmp_rcv+0x334/0x390

[<ffffffff813721a4>] ip_local_deliver_finish+0x13c/0x2d8

[<ffffffff813718c4>] ip_rcv_finish+0x134/0x510

[<ffffffff81343af4>] netif_receive_skb+0x41c/0x5d8

[<ffffffff81343d58>] process_backlog+0xa8/0x160

[<ffffffff8134186c>] net_rx_action+0x194/0x2e8

[<ffffffff8115b71c>] __do_softirq+0x114/0x288

[<ffffffff8115b910>] do_softirq+0x80/0x98

[<ffffffff8115bb8c>] irq_exit+0x64/0x78

[<ffffffff81100e40>] plat_irq_dispatch+0xd0/0x1d0

[<ffffffff81120c80>] ret_from_irq+0x0/0x4

[<ffffffff81120ea0>] r4k_wait+0x20/0x40

[<ffffffff81123414>] cpu_idle+0x34/0x60
Comment 1 Alan 2013-11-04 11:50:06 UTC
Obsolete lermel

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