cancel
Showing results for 
Search instead for 
Did you mean: 

GT-AXE11000 : Normal Reboot or something else?

JM492
Level 7
Hello,

I recently acquired the GT-AXE11000 and I find it to be a great router. While I was doing some web browsing, I noticed I lost my internet connection for a few seconds (around half a minute) and it came back. Obviously it was not a huge deal, but I always like to check these kinds of things just in case. I checked the system logs to see what it was all about and this is is what I found happened at that time:

May 4 22:38:51 wlceventd: wlceventd_proc_event(491): eth7: Deauth_ind 56:A6:8C:72:15:5F, status: 0, reason: Unspecified reason (1), rssi:-58
May 4 22:38:51 wlceventd: wlceventd_proc_event(527): eth7: Auth 56:A6:8C:72:15:5F, status: Successful (0), rssi:-58
May 4 22:38:51 wlceventd: wlceventd_proc_event(537): eth7: ReAssoc 56:A6:8C:72:15:5F, status: Successful (0), rssi:-58
May 4 22:56:26 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xe832 (36/160)
May 4 22:56:26 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
May 4 22:56:26 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xe832 (36/160)
May 4 22:56:26 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xe932 (40/160)
May 4 22:56:26 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
May 4 22:56:26 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xe932 (40/160)
May 4 22:56:26 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xea32 (44/160)
May 4 22:56:26 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
May 4 22:56:26 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xea32 (44/160)
May 4 22:56:26 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xeb32 (48/160)
May 4 22:56:26 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
May 4 22:56:26 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xeb32 (48/160)
May 4 23:13:49 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xe832 (36/160)
May 4 23:13:49 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
May 4 23:13:49 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xe832 (36/160)
May 4 23:13:49 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xe932 (40/160)
May 4 23:13:49 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
May 4 23:13:49 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xe932 (40/160)
May 4 23:13:49 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xea32 (44/160)
May 4 23:13:49 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
May 4 23:13:49 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xea32 (44/160)
May 4 23:13:49 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xeb32 (48/160)
May 4 23:13:49 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
May 4 23:13:49 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xeb32 (48/160)
May 5 01:05:09 kernel: klogd started: BusyBox v1.24.1 (2022-02-17 15:29:22 CST)
May 5 01:05:09 kernel: Upload the firmware into the on-chip memory
May 5 01:05:09 kernel: ^M0%^M1%^M2%^M3%^M4%^M5%^M6%^M7%^M8%^M9%^M10%^M11%^M12%^M13%^M14%^M15%^M16%^M17%^M18%^M19%^M20%^M21%^M22%^M23%^M24%^M25%^M26%^M27%^M28%^M29%^M30%^M31%^M32%^M33%^M34%^M35%^M36%^M37%^M38%^M39%^M40%^M41%^M42%^M43%^M44%^M45%^M46%^M47%^M48%^M49%^M50%^M51%^M52%^M53%^M54%^M55%^M56%^M57%^M58%^M59%^M60%^M61%^M62%^M63%^M64%^M65%^M66%^M67%^M68%^M69%^M70%^M71%^M72%^M73%^M74%^M75%^M76%^M77%^M78%^M79%^M80%^M81%^M82%^M83%^M84%^M85%^M86%^M87%^M88%^M89%^M90%^M91%^M92%^M93%^M94%^M95%^M96%^M97%^M98%^M99%^M100%
May 5 01:05:09 kernel: Reset the processors to start execution of the code in the on-chip memory
May 5 01:05:09 kernel: Verify that the processors are running: OK
May 5 01:05:09 kernel: Verify that the firmware has been loaded with good CRC: OK
May 5 01:05:09 kernel: Firmware loading completed successfully
May 5 01:05:09 kernel: BCMENET: Enabling Software GSO for eth0
May 5 01:05:09 kernel: NOTE: Using Port Grouping for IMP ports : [ 0 --> 4 ] [ 1, 2 --> 5 ] [ 3, 7 --> 8 ]
May 5 01:05:09 kernel: LAG/Trunking enabled <0x08>
May 5 01:05:09 kernel: getrcal for res select 5, int 669, ext 644, ratio 123 ratio1 148, rcal 9
May 5 01:05:09 kernel: Setting SGMII Calibration value to 0x9
May 5 01:05:09 kernel: PLL_PON(8051): 0x0250; TX_PON(8067): 0x0048; RX_PON(80b2): 0x0980
May 5 01:05:09 kernel: eth0: Down <04:42:1A:4E:AC:90>
May 5 01:05:09 kernel: Chip Port 10, CrossBar Port 1, PHY_ID <0x0007f00c:0x0c: On-chip 1G GPHY> Cfg: ANG.1G; Down
May 5 01:05:09 kernel: eth1: Down <04:42:1A:4E:AC:90> PHY_ID <0x0007f008:0x08: On-chip 1G GPHY> Cfg: ANG.1G; Down
May 5 01:05:09 kernel: eth2: Down <04:42:1A:4E:AC:90> PHY_ID <0x0007f009:0x09: On-chip 1G GPHY> Cfg: ANG.1G; Down
May 5 01:05:09 kernel: eth3: Down <04:42:1A:4E:AC:90> PHY_ID <0x0007f00a:0x0a: On-chip 1G GPHY> Cfg: ANG.1G; Down
May 5 01:05:09 kernel: eth4: Down <04:42:1A:4E:AC:90> PHY_ID <0x0007f00b:0x0b: On-chip 1G GPHY> Cfg: ANG.1G; Down
May 5 01:05:09 kernel: eth5: Down <04:42:1A:4E:AC:90>
May 5 01:05:09 kernel: Chip Port 9, CrossBar Port 0, PHY_ID <0x06180006:0x06:External 2.5G SERDES> Cfg: ANG.2.5G; Down
May 5 01:05:09 kernel: PHY_ID <0x0388001e:0x1e:External Cascaded 10G EXT3> Cfg: ANG.2.5G; Down ===> Activate Deep Green Mode
May 5 01:05:09 kernel: bcmswlpbk0 (Ext switch port: 😎 (Logical Port: 😎 Virtual link DOWN
May 5 01:05:09 kernel: dgasp: kerSysRegisterDyingGaspHandler: bcmsw registered
May 5 01:05:09 kernel: bcm_enet_init:L2396 ENET system contructed and configured enet-kthrd thread
May 5 01:05:09 kernel: enet_kthread_handler:L295 Instantiating ENET thread
May 5 01:05:09 kernel: ^[[0;34m[NTC bitpool] idx_pool_init: 551:PktRnr[0]:Create Index Pool_Size = 16512^[[0m
May 5 01:05:09 kernel: ^[[0;34m[NTC bitpool] idx_pool_init: 551:L2L3-ucast:Create Index Pool_Size = 16384^[[0m
May 5 01:05:09 kernel: Initialized Runner Host Layer
May 5 01:05:09 kernel: Initialized Runner Unicast Layer
May 5 01:05:09 kernel: Initialized Runner L2 Unicast Layer
May 5 01:05:09 kernel: ^[[0;34m[NTC bitpool] idx_pool_init: 551:mcast:Create Index Pool_Size = 128^[[0m
May 5 01:05:09 kernel: Initialized Runner Multicast Layer
May 5 01:05:09 kernel: ^[[0;34m[NTC bitpool] idx_pool_init: 551:FHW[0]:Create Index Pool_Size = 16512^[[0m
May 5 01:05:09 kernel: Retrieve num_fhw_path=64
May 5 01:05:09 kernel: ^[[0;36;44mPathstats allocated 2048 bytes^[[0m
***Text Removed as it was too long***
May 5 01:05:16 acsd: eth6: selected channel spec: 0x1008 (8)
May 5 01:05:16 acsd: acs_set_chspec: 0x1008 (8) for reason APCS_INIT
May 5 01:05:16 wan: finish adding multi routes
May 5 01:05:16 acsd: eth7: Selecting 5g band ACS policy
May 5 01:05:17 miniupnpd[1931]: shutting down MiniUPnPd
May 5 01:05:18 miniupnpd: it is advised to use network interface name instead of 192.168.50.1/255.255.255.0
May 5 01:05:18 miniupnpd[2437]: HTTP listening on port 50026
May 5 01:05:18 miniupnpd[2437]: Listening for NAT-PMP/PCP traffic on port 5351
May 5 01:05:18 vpnserver1[2461]: OpenVPN 2.4.11 arm-buildroot-linux-gnueabi [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Feb 17 2022
May 5 01:05:18 vpnserver1[2461]: library versions: OpenSSL 1.1.1k 25 Mar 2021, LZO 2.03
May 5 01:05:18 vpnserver1[2462]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
May 5 01:05:18 vpnserver1[2462]: PLUGIN_INIT: POST /usr/lib/openvpn-plugin-auth-pam.so '[/usr/lib/openvpn-plugin-auth-pam.so] [openvpn]' intercepted=PLUGIN_AUTH_USER_PASS_VERIFY
May 5 01:05:18 vpnserver1[2462]: Diffie-Hellman initialized with 2048 bit key
May 5 01:05:18 vpnserver1[2462]: WARNING: Your certificate is not yet valid!
May 5 01:05:18 vpnserver1[2462]: TUN/TAP device tun21 opened
May 5 01:05:18 vpnserver1[2462]: TUN/TAP TX queue length set to 100
May 5 01:05:18 vpnserver1[2462]: /sbin/ifconfig tun21 10.8.0.1 pointopoint 10.8.0.2 mtu 1500
May 5 01:05:18 vpnserver1[2462]: /etc/openvpn/ovpn-up tun21 1500 1622 10.8.0.1 10.8.0.2 init
May 5 01:05:18 vpnserver1[2462]: /sbin/route add -net 10.8.0.0 netmask 255.255.255.0 gw 10.8.0.2
May 5 01:05:18 vpnserver1[2462]: Socket Buffers: R=[524288->524288] S=[524288->524288]
May 5 01:05:18 vpnserver1[2462]: setsockopt(IPV6_V6ONLY=0)
May 5 01:05:18 vpnserver1[2462]: UDPv6 link local (bound): [AF_INET6][undef]:1025
May 5 01:05:18 vpnserver1[2462]: UDPv6 link remote: [AF_UNSPEC]
May 5 01:05:18 vpnserver1[2462]: MULTI: multi_init called, r=256 v=256
May 5 01:05:18 vpnserver1[2462]: IFCONFIG POOL: base=10.8.0.4 size=62, ipv6=0
May 5 01:05:18 vpnserver1[2462]: Initialization Sequence Completed
May 5 01:05:19 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xe832 (36/160)
May 5 01:05:19 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xe832 (36/160)
May 5 01:05:19 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xe832 (36/160)
May 5 01:05:19 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xe932 (40/160)
May 5 01:05:19 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xe932 (40/160)
May 5 01:05:19 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xe932 (40/160)
May 5 01:05:19 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xea32 (44/160)
May 5 01:05:19 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xea32 (44/160)
May 5 01:05:19 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xea32 (44/160)
May 5 01:05:19 acsd: acs_candidate_score_intf(1133): eth7: intf check failed for chanspec: 0xeb32 (48/160)
May 5 01:05:19 acsd: acs_candidate_score_bgnoise(1602): eth7: bgnoise check failed for chanspec: 0xeb32 (48/160)
May 5 01:05:19 acsd: acs_candidate_score_txop(1860): eth7: txop check failed for chanspec: 0xeb32 (48/160)
May 5 01:05:19 acsd: eth7: selected channel spec: 0xeb32 (48/160)
May 5 01:05:19 acsd: eth7: Adjusted channel spec: 0xeb32 (48/160)
May 5 01:05:19 acsd: eth7: selected channel spec: 0xeb32 (48/160)
May 5 01:05:19 acsd: acs_set_chspec: 0xeb32 (48/160) for reason APCS_INIT
May 5 01:05:19 acsd: eth8: Selecting 6g band ACS policy
May 5 01:05:21 WAN Connection: WAN was restored.
May 5 01:05:22 kernel: SHN Release Version: 2.0.3
May 5 01:05:22 kernel: UDB Core Version: 0.2.20
May 5 01:05:22 kernel: sizeof forward pkt param = 280
May 5 01:05:22 BWDPI: fun bitmap = 4ff
May 5 01:05:22 ntp: start NTP update
May 4 23:17:31 rc_service: ntp 2420:notify_rc restart_diskmon
May 4 23:17:31 disk_monitor: Finish
May 4 23:17:31 disk monitor: be idle
May 4 23:17:31 BONDING: option disabled
May 4 23:17:32 roamast: ROAMING Start...
May 4 23:17:32 A.QoS: qos_count=0, qos_check=0
May 4 23:17:35 acsd: eth8: selected channel spec: 0x692f (6g37/160)
May 4 23:17:35 acsd: eth8: Adjusted channel spec: 0x692f (6g37/160)
May 4 23:17:35 acsd: eth8: selected channel spec: 0x692f (6g37/160)
May 4 23:17:35 acsd: acs_set_chspec: 0x692f (6g37/160) for reason APCS_INIT
May 4 23:17:35 dhcp client: bound 135.23.176.208/255.255.255.224 via 135.23.176.193 for 149851 seconds.
May 4 23:18:08 crond[1751]: time disparity of 2103732 minutes detected
May 4 23:19:14 wlceventd: wlceventd_proc_event(527): eth7: Auth 00:57:C1:DC:47:62, status: Successful (0), rssi:0
May 4 23:19:14 wlceventd: wlceventd_proc_event(556): eth7: Assoc 00:57:C1:DC:47:62, status: Successful (0), rssi:-41
May 4 23:19:18 kernel: FPM Pool 0: invalid token 0x01800000 freed
May 4 23:19:18 kernel: FPM Pool 1: invalid token 0x216a0000 freed
May 4 23:19:21 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7619)]periodic_check AM 4:14
May 4 23:19:21 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7658)]do webs_update
May 4 23:19:24 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7676)]retrieve firmware information
May 4 23:19:24 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7691)]fimrware update check first time
May 4 23:19:24 WATCHDOG: [FAUPGRADE][auto_firmware_check:(7722)]no need to upgrade firmware


I am wondering if this system log for this reboot is normal or is something else going on. I believe it is normal but I would not know just by looking at it as it is. I believe the firmware was updated by looking at the log but again I'm not sure. I would be extremely thankful for any help identifying what happened and if its something worth looking into more or is it safe. If the whole system log is required let me know. Thanks in advance.
1,592 Views
4 REPLIES 4

Saltgrass
Level 13
I see comments in the log that might indicate a Firmware update, do you have it set for auto updates?
Maximus Z790 Hero,
Intel i9-13900k
Intel BE200

Looks like the firmware was updated, from the sounds of it an automatic update. What time was the crash?

Saltgrass wrote:
I see comments in the log that might indicate a Firmware update, do you have it set for auto updates?



jzchen wrote:
Looks like the firmware was updated, from the sounds of it an automatic update. What time was the crash?



Hey,

I did not seem to have the 'Auto Firmware Upgrade' option on when this happened. The time of the crash was yesterday (2022 May 4th) at around 11:30 PM EST.

Yesterday, it did seem to have gotten an update but the timing seems inconsitent:



I did hear that updates for the signature happen by themselves regardless of the auto firmware upgrade option being on or off, so it could be that, and the timing could be from using another time zone that is not EST, but again I'm not sure.

Yeah, I understand I do vaguely remember the time zone was off when I first set up my AXE11000. The thing is the log is not something I understand. I was hoping to narrow down the time of the drop and then research what those lines around that time mean...

The first 3 lines are around 5/4 10:38 pm if I read the 24 hour clock right. Seems like a "Deauth" with unknown reason. I looked up -58 dbm and seems like a decent WiFi signal strength. (You were connected via WiFi?) And then within the same minute next 2 lines "look like" a reconnection to me. This lines up as you noted the drop was for about 30 seconds...

If I'm not mistaken, for whatever reason, the firmware was updated after the drop event. I checked, and it is the latest firmware. I'm not the only one reporting stable connections lately so I figure the update may have solved any issues your old firmware was causing....