Fortiweb 400D / firmware 5.53 kernel panic under HA

[ispcolohost]

Hi all, trying to connect two 400D's in act/pas HA mode.  Running fresh 5.53 code, no real config other than setting port 7/8 on both units as an MLAG with one vlan interface under each for management.  Log into web interface, other than setting a group name, no changes to default HA config, click apply, unit one is good, click apply, unit two immediately kernel panics and is now stuck in reset loop when watchdog detects the panic.  Anyone run into this?  Is 5.53 code too new?  

kernel BUG at include/linux/skbuff.h:1704! invalid opcode: 0000 [#1] SMP Modules linked in: fproxy(O) fwbrnd(O) ha(O) log_msgid(O) wproxy(O) tproxy(O) tp_v6_defrag(O) antidos(O) vserver_filter(O) intf_filter(O) bridge_mac(O) ti_bridge(O) share_ip(O) miglog(O) admin_socket(O) CPU: 0 PID: 0 Comm: swapper/0 Tainted: G O 3.18.25 #1 Hardware name: GIGABYTE GS-6LPCE1/GA-6LPCE1, BIOS R04d_HT 12/29/2015 task: ffffffff80a13480 ti: ffffffff80a00000 task.ti: ffffffff80a00000 RIP: 0010:[<ffffffff80662075>] [<ffffffff80662075>] skb_pull+0x25/0x30 RSP: 0018:ffff88020fc03d40 EFLAGS: 00010297 RAX: 0000000000000174 RBX: ffff8802020f2000 RCX: 0000000000000005 RDX: 000000000000000c RSI: 0000000000000004 RDI: ffff8802020f2000 RBP: ffff8800024aff00 R08: 0000000000000072 R09: 0000000000000000 R10: c8fc505c8d407235 R11: 8d4072355b5c8d40 R12: ffff88020070e440 R13: ffff88020070e44e R14: ffffffffa01ac5e0 R15: 0000000000009488 FS: 0000000000000000(0000) GS:ffff88020fc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000000dcb8e10 CR3: 0000000200d52000 CR4: 00000000001407f0 Stack: ffffffffa01a9b49 0000000000000000 0000000000000000 0000000000000499 0000000100000000 0000000200000002 ffff8802020f2000 ffffffff80a74ab8 ffff880201808000 ffffffff80a74ae0 ffffffff8066dc36 0000000000000000 Call Trace: <IRQ> [<ffffffffa01a9b49>] ? l2ep_rcv+0xe9/0x270 [ha] [<ffffffff8066dc36>] ? __netif_receive_skb_core+0x416/0x5b0 [<ffffffff8066f8b4>] ? netif_receive_skb_internal+0x24/0x80 [<ffffffff8066ffc8>] ? napi_gro_receive+0x78/0xb0 [<ffffffff805a4323>] ? igb_poll+0x613/0xe20 [<ffffffff80670801>] ? net_rx_action+0x81/0x130 [<ffffffff8023cf35>] ? __do_softirq+0xd5/0x1e0 [<ffffffff8023d1f5>] ? irq_exit+0x55/0x60 [<ffffffff80203f4d>] ? do_IRQ+0x4d/0xe0 [<ffffffff80758b2a>] ? common_interrupt+0x6a/0x6a <EOI> [<ffffffff8020a9b8>] ? mwait_idle+0x58/0x90 [<ffffffff80262cf7>] ? cpu_startup_entry+0x1a7/0x280 [<ffffffff80a8deed>] ? start_kernel+0x3c7/0x3d2 [<ffffffff80a8d931>] ? set_init_arg+0x4e/0x4e Code: 84 00 00 00 00 00 8b 47 78 39 c6 77 1b 29 f0 3b 47 7c 89 47 78 72 14 89 f0 48 03 87 40 01 00 00 48 89 87 40 01 00 00 c3 31 c0 c3 <0f> 0b 66 0f 1f 84 00 00 00 00 00 39 77 78 76 20 8b 47 7c 85 c0 RIP [<ffffffff80662075>] skb_pull+0x25/0x30 RSP <ffff88020fc03d40> ---[ end trace 96f82648c6fe7917 ]--- Kernel panic - not syncing: Fatal exception in interrupt Kernel Offset: 0x0 from 0xffffffff80200000 (relocation range: 0xffffffff80000000-0xffffffff9fffffff) Rebooting in 5 seconds.. ACPI MEMORY or I/O RESET_REG.

[ispcolohost]

Just FYI, this was a firmware bug, I received a pre-release that resolved it, FWB_400D-v500-build0732, and the latest release code, 5.5.4 build 0739, no longer has the issue.