Wireless Access

 View Only
  • 1.  AP735 & AP725 reboots unexpectedly (AOS 10.8.0, 10.8.1)

    Posted Jul 24, 2026 12:17 AM

    We have 2 diffrent AP, AP735 & AP725 registed on our aruba central. Im currently using the New Central to manage our wireless environment. 


    AP735 is running AOS 10.8.1.0_95966, AP725 is running AOS 10.8.0.2_95847, both AP reboots randomly, not all. Only thing i can use as reference is the reason for last reboot which is "BUGSoftLockup: CPU#1 stuck for 23s! [wl0-scheduler:7047] PC: wlc_taf_delegate2_src_support_functions+0x213c8/" all have the "BUGSOftLockup" as a start but sometime it gives us diffrent description at the end for example, the below


    BUGSoftLockup: CPU#1 stuck for 23s! [wl0-scheduler:7047] PC: wlc_taf_delegate2_src_support_functions+0x213c8/

    BUGSoftLockup: CPU#0 stuck for 21s! [wl1-scheduler:7199] PC: wlc_taf_schedule+0x37c/0x2bf0 [wl] Warm-reset

    BUGSoftLockup: CPU#1 stuck for 24s! [wl0-scheduler:7198] PC: timer_start+0x1cc/0x7e0 [wl] Warm-reset


    i have looked at previous release notes and the "BUGSoftLockup" seems to be included in the resolved issue on 10.7.2.2 and 10.8.0, but im starting to wonder if its still ongoing?


    if anyone is familiar with this problem, please advice on how to fix


    thanks



  • 2.  RE: AP735 & AP725 reboots unexpectedly (AOS 10.8.0, 10.8.1)

    Posted Jul 24, 2026 01:55 AM

    I think it is best to open a TAC case this way they can track it. 



    ------------------------------
    If my post was useful accept solution and/or give kudos.
    Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
    ------------------------------



  • 3.  RE: AP735 & AP725 reboots unexpectedly (AOS 10.8.0, 10.8.1)

    Posted Aug 17, 2026 10:59 PM

    Agree a case is the way to go, and here's what to arm it with. Your soft lockups line up with two documented items in the 10.8 release notes. The AP-725 side matches a known issue in the 10.8.0.x notes: crashes with FTM enabled, both CPUs observed hanging for tens of seconds, worse as client counts climb. That CPU-stuck-then-warm-reset pattern is your wl-scheduler lockup, so if FTM or location services are enabled on the 725s, that's the first mitigation to test. On the 735 side, the 10.8.1.0 resolved list includes AOS-257032 for AP-735s crashing and restarting continuously, but you're crashing on 10.8.1.0 itself, so you're either on an unfixed variant or an adjacent scheduler defect.

    Practical path: bring everything to the latest 10.8.1.x on the portal, and open the case with the exact BUGSoftLockup strings plus AOS-257032 as the reference. Those wlc_taf symbols are the radio driver's airtime scheduler, which makes this a code defect, not a config problem. Also, this got posted twice with near-identical titles, worth deleting the copy so answers land in one place.



    ------------------------------
    Dustin Burns

    @Worldcom Exchange, Inc.


    If my post was useful accept solution and/or give kudos
    ------------------------------