Gen 6 Firewall Reboots due to tsfTaskLoc
03/26/2020 13 10839
This article explains troubleshooting scenarios where Gen 6 firewalls are rebooting due to "tsfTackLoc" found in the stack trace information from the tracelogs. This issue is observed in Gen 6 firewalls on firmware 184.108.40.206-26n.
This issue is caused by the Geo-IP and Botnet filter services on the firewall. The task refers to the Location Code which is common to both Geo-IP and Botnet Services.
The stack trace from the firewall looks similar to:
07/26/2016 19:12:16.048Reboot due to task suspension07/26/2016 19:12:16.048Task Trace tsfTaskLoc:
tsfTaskLoc 804837c8 ebbd8d10 60 STOP 804a8b1c ebbd8b20 ad0003 0
Stack trace of tsfTaskLoc:
0x812c74f4 -> ($13)
0x80483800 -> 0x80483790
0x80483344 -> 0x804831c0
0x804831f4 -> 0x804a7008
0x804a7020 -> 0x804a6f88
0x804a6fdc -> 0x804a8b50
0x804a8b2c -> 0x804a8b08
Tracelogs can be downloaded from the diag.html page. This is further explained in How to download trace Logs from Sonicwall Firewalls
A temporary workaround for this issue is to disable the Geo-IP and Botnet services. This prevents the Botnet Database from downloading.
A Hotfix is available for this issue and can be requested from Support. (DTS 176249)
The HF makes the Botnet feature use a separate memory zone.