General
This is an internal fix to avoid FW coredump corruption. The coredump is one of important files to debug a FW crash issues, and the fix in this CDETS is to help on getting coredump properly for internal debugging purpose.
Symptom
If FW exceptions are fired in back-to-back manner, then the first coredump thread can be interrupted by the following coredump. Since the coredump thread is not protected, the consequences will be coredump corruption or sometimes no coredump collected. We have found in HG AP that a fatal FW error is followed by FW watchdog barking couple of seconds later. We have observed this symptom through system log.
Conditions
The problem happens when two or more FW asserts get called within couple of seconds.
Workaround
No workaround but fix.
Further Problem Description
NA
