FortiGate 60C always hang with kernel panic

[#1]

Do anyone have a problem that FortiGate 60C always hang? The unit can be reachable by pinging to the wan1 interface, but the console, web gui, telnet had no response. All VPN tunnel and internet access traffic also had no response too. Once I tried to keep the console turned on and just before the unit was hanged, I have seen the following error: Unable to handle kernel paging request at virtual address 6e6f698d mm = c0200bc0 pgd = c0004000 *pgd = 00000000, *pmd = 00000000 Internal error: Oops: 0 CPU: 0 pc : [<c003eea8>] lr : [<c012c5ec>] Not tainted sp : c01ffd88 ip : 00000000 fp : c4bd6000 r10: dc9b62e0 r9 : c4c91794 r8 : 0000f2c6 r7 : 00000001 r6 : 00000000 r5 : 00000000 r4 : c4c916e0 r3 : ce2908c0 r2 : ce2908c0 r1 : 00000000 r0 : 6e6f6974 Flags: Nzcv IRQs on FIQs on Mode SVC_32 Segment kernel Control: 3177 Table: 0000C000 DAC: 0000001D Process swapper (pid: 0, stack limit = 0xc01fe370) Stack: (0xc01ffd88 to 0xc0200000) fd80: c4c916e0 00000000 c012c770 c4c916e0 c0132128 ce29008c fda0: c01ffe50 c4c916e0 dbe44070 00000000 c0132154 c0139dc8 c0139dc8 c01ffddc fdc0: c026a5b0 00000001 dbda2c00 c01ffde0 00000000 c013a090 c01418b8 c026a5b0 fde0: cfa28980 cfa28980 dbda2c00 cfa28980 dbda2c00 c01ffe40 c0141b80 00204000 fe00: 00000000 00000002 00000000 00000000 00000001 00000000 00000000 000003e9 fe20: c01ffe58 c01ffe30 c0022264 c0021bbc d7c6d388 d817b800 d817b80c a0000093 fe40: d7be69fc 00000001 a0000013 c01ffe98 00000000 00000004 00000000 00000000 fe60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 fe80: 00000000 0000c6f2 00000000 00000000 00000000 c4c916e0 c4c916e0 dbe51400 fea0: dbe44070 0000005c dbe44080 dc9b62e0 dbe440e0 c0132258 c4bd6000 dc916500 fec0: dbda2570 dbda2400 dc9b6000 00000040 c01fff0c dbe44000 dc958c78 00000001 fee0: 00000000 c0901060 00000000 c01fff0c dbe44000 c01fff30 dbda2800 dbe44070 ff00: 00000040 00000000 dc916890 00000000 dbda28e4 dbda2800 c0200180 00a4c09a ff20: c024c658 ffffffff 00000001 c0132464 0000012c 00000001 c0200070 00000000 ff40: c024c200 60000093 c00295cc c01fffb8 00000000 40000000 c024c200 c01fff84 ff60: c001a080 c001a080 c12370c0 c01fffb8 00000000 40000000 c001a9e8 60000013 ff80: c00191a0 00000000 00000032 00000000 60000013 c001a9a8 c01fe000 00000000 ffa0: 00000000 c0016e20 00000000 00000001 00000000 20000013 c01fffcc c001a9dc ffc0: c001a9e8 60000013 ffffffff c001aa40 c024dad4 c025d88c c0008648 c023fec4 ffe0: c026cb94 c026cb94 c023fab4 c023fab0 c0200e50 66056261 00015e84 c0008080 Backtrace: not available Code: eb05a5c0 e1a00004 e8bd8010 c024db4c (e5d03019) Kernel panic: Aiee, killing interrupt handler! In interrupt handler - not syncing Init SSP ...OK Read SPI ...OK My firmware version is v4.0,build5263,100619 (MR1).

[edsouza_FTNT]

I think there is a newer build available, try to use 5269.

[#3]

Thank you for your reply. I find the new firmware 5272 and apply it to some sites. See what happens next.

[Oberon]

Trusts Fortinet maybe not his new MR2 Release, that there is no Build for the FGT-60C available!?

[#5]

After applying the firmware 5272, the devices are still rebooted. However, I have found that the devices has not hang for a week after I removed the SDHC card from the slot. Did everyone have the same issue?