Reset Search
 

 

Article

Kernel crash observed randomly with the presence of IPv6 multicast stream.

« Go Back

Information

 
TitleKernel crash observed randomly with the presence of IPv6 multicast stream.
Symptoms
The switch crashes when IPv4 and IPv6 multicast traffic streams are started
x460G2-142.1 # CPU 1 Unable to handle kernel paging request at virtual address 0000000000000000, epc == ffffffffc1657f70, ra == ffffffffc1657f70
Oops[#1]:
Cpu 1
$ 0   : 0000000000000000 000000000000001c 0000000000000080 0000000000000001
$ 4   : 0000000000000008 0000000000000000 0000000000000001 0000000000002ab0
$ 8   : 0000000000007fff ffffffff8169a4d0 ffffffff816a0000 0000000000000004
$12   : 0000000000000003 ffffffff803e3300 0000000000018001 0000000000018001
$16   : ffffffffc1b40000 a80000004a96b470 a80000004a96b400 0000000000000000
$20   : ffffffffc24d66a0 ffffffffc0c31318 a80000004a96b460 fffffffffffffffe
$24   : 0000000000000004 ffffffffc1657f40                                  
$28   : a80000004a968000 a80000004a96b120 0000000000000001 ffffffffc1657f70
Hi    : 0000000000000fff
Lo    : 000000002e48fe76
epc   : ffffffffc1657f70 _default_assert+0x30/0x38 [linux_bcm_diag_full]
    Tainted: P          
ra    : ffffffffc1657f70 _default_assert+0x30/0x38 [linux_bcm_diag_full]
Status: 10109ce3    KX SX UX KERNEL EXL IE 
Cause : 0080000c
BadVA : 0000000000000000
PrId  : 000d9301 (Cavium Octeon II)
Modules linked in: exfipSnoop(P) exfib exsflow(P) exacl(P) exsnoop(P) exosmc exdos(P) exdhcpsnoop bcmpkt exvlan ocpd(P) nettx exosmailbox(P) exosq(P) exstm kicm(P) bcmhelper(P) linux_uk_extr(P) linux_bcm_diag_full(P) linux_uk_proxy(P) linux_kernel_bde(P) pciphymod(P) aspenpmap(P) watchdog shid(P) exosnvram(P)
Process bcmASYNC (pid: 1532, threadinfo=a80000004a968000, task=a80000004ee62240, tls=0000000000000000)
Stack : 0000000000000000 ffffffffc0c2fb5c 0000000000000ef8 0000000000018001
        a80000004a96b220 a80000004a96b470 a80000004a96b400 0000000000000000
        0000000000000ef8 ffffffffc0c31318 a80000004a96b460 ffffffffc0c539b0
        0000000000000000 0000000000000000 0000000000000018 a800000002f5f180
        7fffffffffffffff 7fffffffffffffff ffffffffc24d66a0 ffffffffc0c53080
        0000000000000117 ffffffffc24d66a0 0000000000000000 0000000000000000
        0000000000000000 0000000000000000 0000000000000000 0000000000000000
        0000000000000000 0000000000000000 0000000000000000 0000000000000000
        0000004000600018 0000000000000000 a80000004a96b474 ffffffffc0c31c40
        a80000004a96b720 0000000000000118 0000000000000117 a80000004a96b478
        ...
Call Trace:
[<ffffffffc1657f70>] _default_assert+0x30/0x38 [linux_bcm_diag_full]
[<ffffffffc0c2fb5c>] soc_meminfo_field_get+0x1b4/0x520 [linux_bcm_diag_full]
[<ffffffffc0c539b0>] soc_ism_gen_crc_key_from_keyfields+0x100/0x368 [linux_bcm_diag_full]
[<ffffffffc0c5494c>] soc_generic_hash+0x2bc/0xc28 [linux_bcm_diag_full]
[<ffffffffc0c55960>] soc_mem_multi_hash_move+0xf8/0xb78 [linux_bcm_diag_full]
[<ffffffffc0c875f0>] _soc_mem_multi_hash_insert+0xf8/0x148 [linux_bcm_diag_full]
[<ffffffffc1187e00>] _bcm_tr3_l3_ipmc_add+0x398/0x3d0 [linux_bcm_diag_full]
[<ffffffffc0db5db4>] bcm_xgs3_l3_add+0x27c/0x1098 [linux_bcm_diag_full]
[<ffffffffc0f3ddec>] _bcm_tr_ipmc_add+0x17c/0x258 [linux_bcm_diag_full]
[<ffffffffc0f3e888>] bcm_tr_ipmc_add+0x230/0x348 [linux_bcm_diag_full]
[<ffffffffc0a37e90>] bcm_esw_ipmc_add+0x1a0/0x298 [linux_bcm_diag_full]
[<ffffffffc066a650>] bcm_ipmc_add+0x68/0x2b8 [linux_bcm_diag_full]
[<ffffffffc036f4e0>] pib_ipmc_add_bcm+0x3c8/0xe30 [linux_bcm_diag_full]
[<ffffffffc05ed824>] bcm_async_run+0xa4/0x1eab0 [linux_bcm_diag_full]
[<ffffffffc060c2f8>] _bcm_async_thread+0xc8/0x150 [linux_bcm_diag_full]
[<ffffffffc1659664>] thread_boot+0xdc/0xf0 [linux_bcm_diag_full]
[<ffffffff80293924>] kthread+0x5c/0xb8
[<ffffffff8024ed58>] kernel_thread_helper+0x10/0x18


Code: 6442eb9c  0040f809  0060282d <ac000000> 00000034  10800003  3c02c316  03e00008  fc44aba0 
Fatal exception: panic in 5 seconds
CPU 1: Kernel thread was stuck for 4.24 seconds, jiffies: 4294969093
Kernel panic - not syncing: Fatal exception

 
Environment
  • X460G2
  • IPv4 Multicast
  • IPv6 Multicast
Cause
The issue is documented under CR xos0062555.
Resolution
Upgrade to an EXOS version which contains the fix for xos0062555.

Target Releases:
EXOS 21.1.1 
EXOS 16.2.5patch1-11
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255