Business Community > Wireless > EAP772 high CPU utilization
< Wireless

EAP772 high CPU utilization

EAP772 high CPU utilization

EAP772 high CPU utilization
EAP772 high CPU utilization
2025-11-25 02:08:08
Model: EAP772  
Hardware Version: V2
Firmware Version: 1.3.4

I've been seeing very high CPU utilization on my two EAP772 access points.  I've connected to the shell of one of the devices and run show process resource which shows software interrupts as the culprit.  Any idea what's going on here?

 

EAP#show process resource
show process resource
Mem: 384412K used, 500092K free, 0K shrd, 548992710272K buff, 4275684K cached
CPU: 0% usr 0% sys 0% nic 2% idle 0% io 0% irq 97% sirq
Load average: 4.65 4.23 3.28 5/166 17204
PID PPID USER STAT VSZ %VSZ %CPU COMMAND
15 2 root RW 0 0% 26% [ksoftirqd/1]
25 2 root RW 0 0% 26% [ksoftirqd/3]
20 2 root RW 0 0% 23% [ksoftirqd/2]
9 2 root SW 0 0% 12% [ksoftirqd/0]
402 1 root S 10480 1% 2% /usr/bin/ble_IoT
398 1 root S 5688 1% 2% /usr/bin/cloud-brd -c /etc/cloud_config.cfg
17204 17203 root R 1392 0% 2% top -b -n1
10 2 root IW 0 0% 2% [rcu_preempt]
4567 1 root S 10560 1% 0% /usr/bin/eap-cs
405 1 root S 10528 1% 0% /usr/bin/uclited
856 1 root S 6928 1% 0% hostapd -g /var/run/hostapd/global -B -P /var/run/hostapd-pid
4552 1 root S 6560 1% 0% /usr/bin/httpd_portal
538 1 root S 5980 1% 0% /sbin/radiusd -d /etc/raddb
404 1 root S 5372 1% 0% /usr/bin/afc
399 1 root S 5292 1% 0% /usr/bin/cloud-client
456 1 root S 4480 1% 0% /usr/bin/energysave
425 1 root S 4440 1% 0% /usr/bin/tpsyslogd
392 1 root S 4396 0% 0% /usr/bin/eap-mesh
16127 1 root S 4308 0% 0% rtty -I [redacted]
16407 16127 root S 4308 0% 0% rtty -I [redacted]
4557 1 root S 3844 0% 0% /usr/bin/tdpd
384 1 root S 2552 0% 0% /usr/bin/radius
385 1 root S 2196 0% 0% /usr/bin/auth-time
607 1 root S 2168 0% 0% /usr/sbin/snmpd -L -c /tmp/snmp/snmpd.conf
380 1 root S 1988 0% 0% /usr/bin/dhcp6c -fd br0
423 1 root S 1924 0% 0% /usr/bin/rfscan
453 1 root S 1892 0% 0% /usr/bin/client-state
403 1 root S 1844 0% 0% /usr/bin/ble
2063 1 root S 1824 0% 0% mcsd -d -C /tmp/mcs.conf
16409 16408 root S 1768 0% 0% /usr/bin/cliserverd_libcli -t 2 -d /dev/pts/1
202 1 root S 1704 0% 0% /sbin/cnssdaemon -s
457 1 root S 1660 0% 0% /usr/bin/cliserverd
467 1 root S 1652 0% 0% /usr/bin/detect
382 1 root S 1612 0% 0% /usr/bin/msg-center
4760 1 root S 1576 0% 0% /usr/bin/eap-monitor
393 1 root S 1572 0% 0% /usr/bin/gpiod
446 1 root S 1564 0% 0% /usr/bin/apscan
445 1 root S 1564 0% 0% /usr/bin/backgroundscan
428 1 root S 1560 0% 0% /usr/bin/rssift
454 1 root S 1524 0% 0% /usr/bin/channeldeploy
502 1 root S 1516 0% 0% /usr/bin/troubleshooting
391 1 root S 1476 0% 0% /usr/bin/tp_gre
449 1 root S 1468 0% 0% /usr/bin/wscheduler
577 1 root S 1388 0% 0% syslogd -C -l 7

EAP#show softirqs
CPU0 CPU1 CPU2 CPU3
HI: 0 0 0 0
TIMER: 158144 175233 168434 168484
NET_TX: 452 0 0 446
NET_RX: 352050 282763 358638 382295
BLOCK: 0 0 0 0
IRQ_POLL: 0 0 0 0
TASKLET: 300312 3 254581 10
SCHED: 87368 61133 40304 89719
HRTIMER: 0 0 1 0
RCU: 109403 126668 136379 105140

EAP#show interrupts
CPU0 CPU1 CPU2 CPU3
4: 216710 224241 211754 234060 GIC-0 20 Level arch_timer
6: 0 0 0 0 GIC-0 39 Level arch_mem_timer
8: 0 0 0 0 GIC-0 195 Level edma_txcmpl_4
9: 0 0 0 0 GIC-0 196 Level edma_txcmpl_5
10: 0 0 0 0 GIC-0 197 Level edma_txcmpl_6
11: 0 0 0 0 GIC-0 198 Level edma_txcmpl_7
12: 4321 0 0 0 GIC-0 199 Level edma_txcmpl_8
13: 0 6358 0 0 GIC-0 200 Level edma_txcmpl_9
14: 0 0 2089 0 GIC-0 201 Level edma_txcmpl_10
15: 0 0 0 314 GIC-0 202 Level edma_txcmpl_11
16: 0 0 0 0 GIC-0 203 Level edma_txcmpl_12
17: 0 0 0 0 GIC-0 204 Level edma_txcmpl_13
18: 0 0 0 0 GIC-0 205 Level edma_txcmpl_14
19: 0 0 0 0 GIC-0 206 Level edma_txcmpl_15
20: 215355 0 0 0 GIC-0 171 Level edma_rxdesc_12
21: 0 134023 0 0 GIC-0 172 Level edma_rxdesc_13
22: 0 0 201489 0 GIC-0 173 Level edma_rxdesc_14
23: 0 0 0 237408 GIC-0 174 Level edma_rxdesc_15
24: 0 0 0 0 GIC-0 223 Level edma_misc
25: 0 0 5559 0 GIC-0 192 Level edma_ppeds_txcmpl_0
26: 8525 0 0 0 GIC-0 160 Level edma_ppeds_rxdesc_0
27: 0 0 208 0 GIC-0 184 Level edma_ppeds_rxfill_0
31: 0 0 0 0 GIC-0 35 Edge wdt_bark
33: 12 0 0 0 GIC-0 321 Level bam_dma
34: 927 0 0 0 GIC-0 322 Level msm_serial0
35: 63 0 0 0 GIC-0 323 Level msm_serial1
36: 252811 0 0 0 GIC-0 98 Level bam_dma
37: 0 0 0 0 GIC-0 139 Level eip_irq_ring_0
38: 0 0 0 0 GIC-0 140 Level eip_irq_ring_1
39: 0 0 0 0 GIC-0 141 Level eip_irq_ring_2
40: 0 0 0 0 GIC-0 142 Level eip_irq_ring_3
41: 1 0 0 0 GIC-0 443 Edge pcie-global
45: 5 0 0 0 GIC-0 454 Edge ce0
46: 87243 0 0 0 GIC-0 455 Edge ce1
47: 21500 0 0 0 GIC-0 456 Edge ce2
48: 3654 0 0 0 GIC-0 457 Edge ce3
50: 102 0 0 0 GIC-0 459 Edge ce5
54: 33262 0 0 0 GIC-0 463 Edge ce9
60: 10 0 0 0 GIC-0 576 Edge host2rxdma-monitor-ring1
61: 0 0 0 0 GIC-0 489 Edge reo2ost-exception
62: 2555 0 0 0 GIC-0 498 Edge wbm2host-rx-release
63: 84 0 0 0 GIC-0 529 Edge reo2host-status
64: 0 0 0 0 GIC-0 486 Edge reo2host-destination-ring4
65: 0 0 2179 0 GIC-0 485 Edge reo2host-destination-ring3
66: 0 8318 0 0 GIC-0 484 Edge reo2host-destination-ring2
67: 4631 0 0 0 GIC-0 483 Edge reo2host-destination-ring1
68: 0 0 0 0 GIC-0 520 Edge rxdma2host-monitor-destination-mac2, rxdma2host-monitor-destination-mac3
69: 0 0 0 56301 GIC-0 516 Edge rxdma2host-monitor-destination-mac1
70: 0 0 0 0 GIC-0 586 Edge host2rxdma-host-buf-ring-mac2, host2rxdma-host-buf-ring-mac3
71: 4 0 0 0 GIC-0 581 Edge host2rxdma-host-buf-ring-mac1
76: 0 0 0 4406 GIC-0 482 Edge wbm2host-tx-completions-ring4
77: 0 0 3495 0 GIC-0 481 Edge wbm2host-tx-completions-ring3
78: 0 8301 0 0 GIC-0 480 Edge wbm2host-tx-completions-ring2
79: 4455 0 0 0 GIC-0 479 Edge wbm2host-tx-completions-ring1
80: 0 0 0 0 GIC-0 575 Edge host2tx-monitor-ring1
81: 0 0 0 0 GIC-0 518 Edge txmon2host-monitor-destination-mac2
82: 0 0 0 0 GIC-0 514 Edge txmon2host-monitor-destination-mac1
83: 0 0 0 0 GIC-0 451 Edge umac_hw_reset_irq
84: 0 0 0 0 GIC-0 590 Edge rxdma2host-destination-ring-mac1, host2rxdma-monitor-ring3, rxdma2host-destination-ring-mac2, rxdma2host-destination-ring-mac3, ppdu-end-interrupts-mac1, rxdma2host-monitor-status-ring-mac1, host2rxdma-monitor-ring2, ppdu-end-interrupts-mac2, rxdma2host-monitor-status-ring-mac2, host2rxdma-monitor-ring3, ppdu-end-interrupts-mac3, rxdma2host-monitor-status-ring-mac3
85: 7 0 0 0 GIC-0 450 Edge smp2p
86: 0 0 0 0 GIC-0 453 Edge q6v5 wdog
87: 0 0 0 0 GIC-0 357 Edge tmc-etr
88: 0 0 0 0 GIC-0 352 Edge tsens_interrupt
89: 0 0 0 0 GIC-0 23 Level arm-pmu
90: 0 0 0 0 GIC-0 299 Edge tzerror
91: 0 0 0 0 smp2p 0 Edge q6v5 fatal
92: 1 0 0 0 smp2p 1 Edge q6v5 ready
93: 1 0 0 0 smp2p 2 Edge q6v5 handover
94: 0 0 0 0 smp2p 3 Edge q6v5 stop
95: 0 0 0 0 smp2p 8 Edge q6v5_wcss_userpd1_fatal
96: 1 0 0 0 smp2p 9 Edge q6v5_wcss_userpd1_ready
97: 1 0 0 0 smp2p 12 Edge q6v5_wcss_userpd1_spawn_ack
98: 0 0 0 0 smp2p 11 Edge q6v5_wcss_userpd1_stop_ack
99: 0 0 0 0 msmgpio 39 Edge gpiolib
100: 147 0 0 0 GIC-0 449 Edge glink-native
101: 4 0 0 0 MSI 134742016 Edge bhi
102: 90 0 0 0 MSI 134742017 Edge mhi, mhi
103: 0 0 0 0 MSI 134742018 Edge qdss
104: 236 0 56700 0 MSI 134742019 Edge pci1_wlan_ce_0, pci1_wlan_ce_7, pci1_wlan_ce_14
105: 301 0 173313 0 MSI 134742020 Edge pci1_wlan_ce_1
106: 209 0 41691 0 MSI 134742021 Edge pci1_wlan_ce_2
107: 3366 0 163 0 MSI 134742022 Edge pci1_wlan_ce_3
108: 121 0 0 0 MSI 134742023 Edge pci1_wlan_ce_5
109: 1737 0 0 0 MSI 134742024 Edge pci1_wlan_grp_dp_0
110: 0 1154 0 0 MSI 134742025 Edge pci1_wlan_grp_dp_1
111: 0 0 1295 0 MSI 134742026 Edge pci1_wlan_grp_dp_2
112: 0 0 0 1290 MSI 134742027 Edge pci1_wlan_grp_dp_3
113: 1798 0 0 0 MSI 134742028 Edge pci1_wlan_grp_dp_4
114: 0 1441 0 0 MSI 134742029 Edge pci1_wlan_grp_dp_5
115: 0 0 815 0 MSI 134742030 Edge pci1_wlan_grp_dp_6
116: 0 0 0 0 MSI 134742031 Edge pci1_wlan_grp_dp_7
117: 28670 0 0 0 MSI 134742032 Edge pci1_wlan_grp_dp_8
118: 502 0 0 0 MSI 134742033 Edge pci1_wlan_grp_dp_9
119: 0 0 0 0 MSI 134742034 Edge pci1_wlan_grp_dp_10
120: 125 0 0 0 MSI 134742035 Edge pci1_wlan_grp_dp_11
121: 235 0 11054 0 MSI 134742036 Edge pci1_ppe_wbm_rel
122: 0 0 14380 0 MSI 134742037 Edge pci1_reo2ppe
123: 222 0 22023 0 MSI 134742038 Edge pci1_ppe2tcl
124: 0 0 0 0 MSI 134742039 Edge umac_hw_reset_irq
IPI0: 42677 42761 20570 82203 Rescheduling interrupts
IPI1: 142 111 129 131 Function call interrupts
IPI2: 0 0 0 0 CPU stop interrupts
IPI3: 0 0 0 0 CPU stop (for crash dump) interrupts
IPI4: 0 0 0 0 Timer broadcast interrupts
IPI5: 0 0 0 0 IRQ work interrupts
IPI6: 0 0 0 0 CPU wake-up interrupts
Err: 0

 

  0      
 
  0      
 
#1
Options
5 Reply
Re:EAP772 high CPU utilization
2025-11-25 20:36:55

Okay, a bit more on this.  The high CPU utilization started after I upgraded these APs to firmware 1.3.4.

If I allow the APs to communicate to the Internet on TCP/443 via the management VLAN then the CPU usage drops.

I am NOT using cloud management services, my controller is local.

If I'm not using cloud services why do the APs keep trying to connect to Internet-based endpoints?  Why do these communications attempts cause high CPU utilization on the APs?

  0  
  0  
#2
Options
Re:EAP772 high CPU utilization
2025-11-26 07:19:28

Hi  @ExplodingLemur 

 

Thanks for posting here.

Do you mean that your EAPs are not connected to the internet? This is a total internal network? Or is it just that the controller has not enabled cloud access? 

 

Please give us more details about the situation:

1. What's the CPU before this firmware update?

2. Which firmware did you use before?

3. What's the current CPU? Better with screenshots.

4. Apart from high CPU value, is there any other misbehavior, such as intermittent wireless connection, or will the EAP auto-reboot?

Wish you a happy life and smooth network usage!  >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#3
Options
Re:EAP772 high CPU utilization
2025-11-27 00:04:28

My firewall has a rule that prevents devices on the management VLAN from reaching the Internet.  My SSIDs are on other VLANs which are permitted to route to the Internet.  Additionally I do not have cloud access enabled.  My controller is dual-homed on the management VLAN as well as another VLAN which can reach the Internet.

 

The CPU utilization prior to the firmware update was around 10%.  I don't recall what the prior version was.  I'm attaching a graph from the controller showing CPU usage.

I was experiencing issues with clients being repeatedly disconnected from the APs.

File:
Screenshot 2025-11-26 at 16-01-41 Omada software controller.pngDownload
  0  
  0  
#4
Options
Re:EAP772 high CPU utilization
2025-11-27 09:26:42 - last edited 2025-11-27 09:33:03

  @ExplodingLemur 

 

Thanks for the information.

 

Would you please share with us more details about the situation?

1. The topology of the network, including the Omada devices and the firewall;

2. The involved configuration screenshots, including the mentioned firewall rules. and the VLAN configs.

 

I was experiencing issues with clients being repeatedly disconnected from the APs.

>>>Does this happens on all wireless clients? If allow the Internet for the management VLAN, will it persist?

Wish you a happy life and smooth network usage!  >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#5
Options
Re:EAP772 high CPU utilization
2025-12-02 05:44:47 - last edited 2025-12-02 06:03:38

  @ExplodingLemur 

 

How is the performance these days?

We are very concerned about your feedback. Has the issue been resolved? 
If not, would you please send us the information mentioned in my last reply for our further investigation?

 

One more question: do you happen to remember the firmware version before this update? Is it 1.3.2? Or an earlier version?

Wish you a happy life and smooth network usage!  >Omada US Enterprise Beta Program Launch< >Get the Latest Omada SDN Controller Releases Here< >Experience the Latest Omada EAP Firmware<
  0  
  0  
#6
Options

Information

Helpful: 0

Views: 408

Replies: 5

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.