NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

donawalt's avatar
donawalt
Mentor
Jun 28, 2025

BUG: KERNEL CRASH in 9.13.1.2, Orbi 970

After being up about 28 hours, one of my 970 satellites did a restart. The bug log reports that the reason was a kernel crash.

 

It was at about 1:30 AM local time, so little or no action going on. The 970 is on a UPS. Here was the debug screen, and I included a link to the debug log zip file in my Dropbox, it was too big to attach; the debug log was run for about 3 minutes, this morning. Let me know if you need more info.

 

Debug log:

https://www.dropbox.com/scl/fi/3cjd4wkcwyv0bq8imqmx5/debuglog.zip?rlkey=himss1gtw5u0qk77wetafwyz3&dl=0 

 

Straq​ 

 

6 Replies

  • Will need to know what you did after FW was updated on the system.

    Updated manually or via AU?

    FW updated and you continued to use the system after the reboot?

    After FW updated, power cycled the system OFF then back ON and continue? 

    Factory reset and setup from scratch after FW was updated? 

     

     

    • FURRYe38's avatar
      FURRYe38
      Guru

      Would need some feedback on these questions:

      Will need to know what you did after FW was updated on the system.

      Updated manually or via AU?

      FW updated and you continued to use the system after the reboot?

      After FW updated, power cycled the system OFF then back ON and continue? 

      Factory reset and setup from scratch after FW was updated? 

      • donawalt's avatar
        donawalt
        Mentor

         

        Updated manually or via AU? Manually

        FW updated and you continued to use the system after the reboot? Reboot from update, then PC everything 

        After FW updated, power cycled the system OFF then back ON and continue? Yes

        Factory reset and setup from scratch after FW was updated? No

  • Unzip the debuglog and check the content of the file oopsdump.  Search for the strings : 

     

    Internal error: Oops

    Crash shutdown device

     

    You should have some evidences with the timestamps

  • I have seen your file in dropbox andn opened. I saw below crash evidences.

     

    I suggest that you create  NG Support ticket and request for escalation to 3rd Level with log file and those evidences : 

     

    bcnss[39]: ERR: Crash shutdown device QCN9224_PCI2 with driver_state 0x107 

    bmhi mhi2: CRASHED - [DID:DOMAIN:BUS:SLOT] - 1109:0003:01:00SUBSYSTEM=mhi DEVICE=+mhi:mhi2

      bmhi mhi2: Fatal error received from wcss software!

     

    cnss[38]: ERR: Crash shutdown device QCN9224_PCI1 with driver_state 0x107   

    bmhi mhi1: CRASHED - [DID:DOMAIN:BUS:SLOT] - 1109:0002:01:00SUBSYSTEM=mhi DEVICE=+mhi:mhi1   

    bmhi mhi1: Fatal error received from wcss software!

     

    ar_wal_mlo_ipc.c:2063 Assertion (!g_wal_mac_core_cfg.dbg.force_crash_on_partner_chip_crash_indication

  • Thanks Saner​ I was just getting to it when you posted again. I am in touch with Eng on this one actually, plus I do have  support ticket open since yesterday! I'll post here if any progress/milestones are achieved.