|
Issue Summary:
Users have reported that after upgrading from v7.2.10 to v7.2.11, or when running v7.4.7, the FortiGate-120G crashes the kernel with the 'NULL pointer dereference at virtual address 00000000000001c8' error message, resulting in device instability and inability to access the Network/Interface GUI or reboot the device, with the following error:
Unable to handle kernel NULL pointer dereference at virtual address 00000000000001c8
Internal error: Oops: 96000006 [#1] SMP
Modules linked in: linux_user_bde(O) linux_kernel_bde(O) filter4
...
Kernel panic - not syncing: Fatal exception in interrupt
SMP: stopping secondary CPUs
Kernel Offset: disabled
CPU features: 0x0,2a002238
Memory Limit: none
---[ end Kernel panic - not syncing: Fatal exception in interrupt ]---
Reproduction Conditions:
- The static route is added or removed on an interface associated with an IPsec VPN tunnel.
- The IPsec phase1 interface is modified or removed.
- VLAN interfaces configured over vlink interfaces are edited.
Impact:
- FortiGate enters a reboot loop approximately 3 minutes after boot.
- Access to the GUI and CLI becomes unresponsive.
- A power cycle is required to recover the unit.
Root Cause:
This issue is caused by a missing ethtool_ops pointer in the VLAN's lower device when interfaced with vlink or IPsec.
This leads to a NULL pointer dereference during system execution.
Debug builds confirmed that the crash can be avoided by adding a NULL pointer check, which results in safe error messages such as:
dev npu0_vlink1 has no ethtool_ops!
Workaround:
- Avoid modifying static routes or VPN interfaces on v7.2.11 and v7.4.7.
- Downgrade to v7.2.10, which has been confirmed as stable.
Solution to the issue:
- Issue already addressed in FortiOS version 7.4.9, 7.6.4 and 8.0.0.
Recommended actions:
- If experiencing this issue, collect the crash log and configuration.
- Open a ticket with TAC referencing this software issue.
Additional information:
- This issue was observed only on specific units; others with identical configurations were unaffected.
- The problem could not be reproduced in lab conditions but was consistently triggered in production.
Related articles:
Troubleshooting Tip: FortiGate-120G/121G high availability cluster out of sync after upgrading to v7...
Technical Tip: FortiGate 90G/91G/120G/121G HA cluster unable to upgrade due to the error 'Firmware i...
Technical Tip: HA issues after upgrade to v7.2.9 for FortiGate 120G/121G
Technical Tip: FortiGate-90G/91G and 120G/121G update to support additional speed options on interna...
|
