cancel
Showing results for 
Search instead for 
Did you mean: 

kernel panic “BB_WDOG_TRIGGERED"

Ermias
New Contributor

I have several R700 AP around our warehouse controlled by ZD3025.  All are experiencing kernel panic and reboot.  Is there a fix for this issue?

Here is an analysis of the syslog.

Why Specifically Did It Panic?

  1. Repeated “BB_WDOG_TRIGGERED” events
    These almost always point to a radio‐firmware or driver problem. It can happen if the firmware goes into an unexpected state—e.g. excessive retries, malformed frames, DFS scanning corner cases, or heavy interference—causing the baseband to lock up. The hardware issues repeated watchdog triggers, and eventually the driver or the kernel panics.

  2. “STA_VDEV_XRETRY” Warnings
    Alongside the watchdog triggers, there are also repeated messages of the form:

     
    FWLOG: [xxxxx] WAL_DBGID_STA_VDEV_XRETRY ( … )

    "XRETRY" typically means the driver tried sending frames to a station multiple times (excessive retries), which might feed into the same underlying radio or firmware meltdown.

  3. Driver/DFS Quirks
    You can also see the AP is blacklisting channels, switching channels, and encountering DFS events. That alone isn’t necessarily a panic cause, but in older or buggy builds, a combination of DFS scanning + heavy channel interference can aggravate or trigger the Wi‐Fi firmware to lock up.

  4. The AP’s log directly shows “Last Reboot Reason: kernel panic.”
    Once the firmware meltdown occurs, the kernel panic is effectively unstoppable (the AP can’t gracefully recover).

0 REPLIES 0