我看TRAPLOG里有这样的日志,但是感觉像是重启后的 77 Sun Jun 23 20:35:40 2019 AP 'AP-1832-03', MAC: 70:d3:79:e6:67:40 disassoci ated previously due to AP Crash. Uptime: 0 days, 00 h 07 m 46 s . Reason: . 78 Sun Jun 23 20:35:29 2019 System 70:d3:79:e4:66:40 has Booted UP
看Crashfile也看不出什么原因.. AP AP-1832-03 crashed at Tue Jun 25 20:19:42 2019 UTC(BOOT_CNT 138) due to: kernel panic ============ image version ============ Active version: 8.9.111.0 Backup version: 8.9.100.0
重启前是这样的日志: Jun 25 11:24:34 kernel: [*06/25/2019 11:24:34.6336] DOT11_DRV[0]: set_channel Channel set to 11 Jun 25 11:24:34 kernel: [*06/25/2019 11:24:34.6336] DOT11_DRV[0]: Start Radio0 - Begin Jun 25 11:24:35 kernel: [*06/25/2019 11:24:34.9934] DOT11_DRV[0]: Start Radio0 - End Jun 25 12:19:31 kernel: [*06/25/2019 12:19:31.9132] systemd[1]: system_monitor.service holdoff time over, scheduling restart. Jun 25 12:19:31 kernel: [*06/25/2019 12:19:31.9431] systemd[1]: Started System Monitor service. Jun 25 12:19:31 kernel: [*06/25/2019 12:19:31.9431] systemd[1]: Starting System Monitor service... Jun 25 16:19:32 kernel: [*06/25/2019 16:19:32.0831] systemd[1]: system_monitor.service holdoff time over, scheduling restart. Jun 25 16:19:32 kernel: [*06/25/2019 16:19:32.1131] systemd[1]: Started System Monitor service. Jun 25 16:19:32 kernel: [*06/25/2019 16:19:32.1131] systemd[1]: Starting System Monitor service... Jun 25 20:19:32 kernel: [*06/25/2019 20:19:32.3330] systemd[1]: system_monitor.service holdoff time over, scheduling restart. Jun 25 20:19:32 kernel: [*06/25/2019 20:19:32.3630] systemd[1]: Started System Monitor service. Jun 25 20:19:32 kernel: [*06/25/2019 20:19:32.3630] systemd[1]: Starting System Monitor service...