High CPU and log filling with " kernel: vtss_phy_wait..."
Posted: Fri Oct 28, 2016 12:35 pm
I have a WISP Switch, 8 port, AC 150 watt switch. I noticed the CPU is runing constantly at >90%, and the log is packed with the following:
Oct 28 11:09:42 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 3
Oct 28 11:09:42 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 4
Oct 28 11:09:43 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 5
Oct 28 11:09:44 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 6
Oct 28 11:09:45 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 0
Oct 28 11:09:45 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 1
Oct 28 11:09:46 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 2
Oct 28 11:09:46 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 3
Oct 28 11:09:47 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 4
Oct 28 11:09:47 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 5
Oct 28 11:09:48 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 6
Oct 28 11:09:49 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 0
Oct 28 11:09:50 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 1
Oct 28 11:09:50 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 2
Oct 28 11:09:51 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 3
Oct 28 11:09:51 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 4
Oct 28 11:09:52 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 5
Oct 28 11:09:53 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 6
Oct 28 11:09:54 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 0
Oct 28 11:09:54 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 1
Oct 28 11:09:55 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 2
Oct 28 11:09:56 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 3
Oct 28 11:09:56 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 4
I dropped to the cmdline and ran top. "poe thread" is at the top of the CPU, taking most of the CPU (>85%). The firmware is 1.42, Board Rev F.
The switch as two AF-5x in it, four Rocket-M2, and is daisy-chained to another switch just like it. I'm not finding anything on the forums or Google that might offer a clue as to what it causing this. The switch uptime is a little over five days. I'm fairly sure the CPU may be due to the switch having to log all these errors/warnings. I turned off logging to see if that would help, but it didn't. (I know that wouldn't fix the underlying cause but thought it may help with the CPU...) Any thoughts?
Thanks
Sam
Oct 28 11:09:42 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 3
Oct 28 11:09:42 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 4
Oct 28 11:09:43 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 5
Oct 28 11:09:44 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 6
Oct 28 11:09:45 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 0
Oct 28 11:09:45 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 1
Oct 28 11:09:46 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 2
Oct 28 11:09:46 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 3
Oct 28 11:09:47 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 4
Oct 28 11:09:47 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 5
Oct 28 11:09:48 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 6
Oct 28 11:09:49 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 0
Oct 28 11:09:50 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 1
Oct 28 11:09:50 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 2
Oct 28 11:09:51 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 3
Oct 28 11:09:51 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 4
Oct 28 11:09:52 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 5
Oct 28 11:09:53 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 6
Oct 28 11:09:54 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 0
Oct 28 11:09:54 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 1
Oct 28 11:09:55 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 2
Oct 28 11:09:56 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 3
Oct 28 11:09:56 kernel: vtss_phy_wait_for_micro_complete:155 MCB timeout, port_no 4
I dropped to the cmdline and ran top. "poe thread" is at the top of the CPU, taking most of the CPU (>85%). The firmware is 1.42, Board Rev F.
The switch as two AF-5x in it, four Rocket-M2, and is daisy-chained to another switch just like it. I'm not finding anything on the forums or Google that might offer a clue as to what it causing this. The switch uptime is a little over five days. I'm fairly sure the CPU may be due to the switch having to log all these errors/warnings. I turned off logging to see if that would help, but it didn't. (I know that wouldn't fix the underlying cause but thought it may help with the CPU...) Any thoughts?
Thanks
Sam