# Log analysis

Source: [https://docs.qualcomm.com/doc/80-88500-4/topic/71_Log_analysis.html](https://docs.qualcomm.com/doc/80-88500-4/topic/71_Log_analysis.html)

The application processor kernel prints the error logs for analysis and
    debugging.

## Non-secure apps watchdog bark

On subsystems, the following log is displayed:

    NMI from appsCopy to clipboard

The following logs are printed by the application processor kernel:

    <6>[  26.924581] Watchdog Bark! Now = 26.924571
    <6>[  26.927638] Watchdog last pet at 14.628269
    <6>[  26.931719] cpu alive mask from last pet 0-3
    <0>[  26.935971] Kernel panic - not syncing: Apps watchdog Bark received!
    Copy to clipboard

## Non-secure apps watchdog bite

On subsystems, the following log is displayed:

    NMI from appsCopy to clipboard

When apps logs are extracted, the following is displayed:

    <6> apps watchdog biteCopy to clipboard

The following error is displayed on TrustZone (TZ) diag:

    Fatal Error: NON_SECURE_WDT
    Encountered fatal FIQ error, CPU: 0, FIQ: 33
    TZBSP_EC_MEM_DUMP_TRIGGER_S_WDOG_FROM_S_WORLD
    Copy to clipboard

## Secure watchdog bark

Secure watchdog bark is a non-fatal fast interrupt request (FIQ). Therefore, a log is not printed
        to either dmesg (displays kernel messages) or TZ diag.

## Secure watchdog bite

Since secure watchdog bite asserts PS\_HOLD directly without notifying HLOS or TZ, an error message is not displayed for dmesg or TZ diag.

## Watchdog bark from subsystem

For example, in case of modem peripheral subsystem (MPSS) watchdog bark, logs like the following
        are printed by the application processor kernel:

    SMSM: Modem SMSM state changed to SMSM_RESET.
    Fatal error on the modem.
     modem subsystem failure reason: dog.c:1225:Watchdog Bark timeout.
     subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = SYSTEM.
    Kernel panic - not syncing: subsys-restart: Resetting the SoC - modem crashed.
    Copy to clipboard

## Watchdog bite from subsystem

For example, in case of MPSS watch dog bite, the following logs are printed by the kernel.

    <3>[ 110.996166] Watchdog Bite received from modem software!
    <3>[ 111.000452] modem subsystem failure reason: SFR Init: WatchDog or kernel error suspected..
    <6>[ 111.008325] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = RELATED.
    <6>[ 111.020432] subsys-restart: subsystem_shutdown(): [ee055500]: Shutting down modem
    Copy to clipboard

**Parent Topic:** [Debug](https://docs.qualcomm.com/doc/80-88500-4/topic/58_Debug.html)

Last Published: Aug 18, 2023

[Previous Topic
Software errors](https://docs.qualcomm.com/bundle/publicresource/80-88500-4/topics/67_Software_errors.md) [Next Topic
Watchdog](https://docs.qualcomm.com/bundle/publicresource/80-88500-4/topics/68_Watchdog.md)