XT8 Dropping Internet constantly, "tx pkt delay suddently jump"

[Cannikin]

Got the XT8 a month ago (end of Nov 2020) and have had nothing but trouble. The first few days it was dropping the internet multiple times per day (ethernet to the rest of the house was fine, wifi devices stayed connected, but no internet access). I installed the latest 386 beta 9.0.0.4.386_41157 and it seemed to calm down and stay stable for a couple of weeks.

Monday night the internet was dropping out again and I thought "here we go again" but this time was something different—the cable modem (Netgear CM1000) had all lights go off and then reconnect. It happened several times in the span of 30 minutes, and unplugging and plugging back in sometimes would restart it, sometimes not (the ethernet light would stay orange). Ran to Costco and got a CM1100 and the same thing started happening! I realized I was using the same power supply from the CM1000 and it dawned on me that that's what was going bad. Used the CM1100 power supply and everything was green and stable again.

But ever since replacing the modem, the ASUS is back to dropping the internet at least once a day. When it does, all lights on the CM1100 stay lit and the ethernet is blinking. Looking at the CM1100 admin page I don't see anything different than when the internet is working properly. I checked the ASUS logs and in the last two instances of the internet dropping I saw this message, which Google returns zero results for on the entire internet:

Dec 18 09:44:57 acsd: eth4 received event: tx pkt delay suddently jump

(Misspellings are in the logs)

Both times, this message was followed by several Disassoc messages within seconds:

Dec 18 09:45:00 wlceventd: wlceventd_proc_event(474): eth4: Deauth_ind 64:16:66:45:92:68, status: 0, reason: Unspecified reason (1)
Dec 18 09:45:00 wlceventd: wlceventd_proc_event(510): eth4: Auth 64:16:66:45:92:68, status: Successful (0)
Dec 18 09:45:00 wlceventd: wlceventd_proc_event(539): eth4: Assoc 64:16:66:45:92:68, status: Successful (0)
Dec 18 09:45:05 wlceventd: wlceventd_proc_event(491): eth4: Disassoc 24:F5:A2:FB:F7:EB, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 18 09:45:05 wlceventd: wlceventd_proc_event(491): eth4: Disassoc 24:F5:A2:FB:F7:EB, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 18 09:45:05 wlceventd: wlceventd_proc_event(491): eth4: Disassoc 24:F5:A2:FD:91:89, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 18 09:45:05 wlceventd: wlceventd_proc_event(491): eth4: Disassoc 24:F5:A2:FD:91:89, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 18 09:45:05 wlceventd: wlceventd_proc_event(474): eth4: Deauth_ind 18:B4:30:06:1A:AE, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 18 09:45:06 wlceventd: wlceventd_proc_event(474): eth4: Deauth_ind B4:181:E2:5B:0C, status: 0, reason: Unspecified reason (1)
Dec 18 09:45:06 wlceventd: wlceventd_proc_event(510): eth4: Auth B4:181:E2:5B:0C, status: Successful (0)
Dec 18 09:45:06 wlceventd: wlceventd_proc_event(539): eth4: Assoc B4:181:E2:5B:0C, status: Successful (0)
Dec 18 09:45:06 wlceventd: wlceventd_proc_event(491): eth4: Disassoc 30:23:03:01:AD:57, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 18 09:45:06 wlceventd: wlceventd_proc_event(491): eth4: Disassoc 30:23:03:01:AD:57, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 18 09:45:06 roamast: [EXAP]Deauth old sta in 0 0: 30:23:03:01:AD:57
Dec 18 09:45:06 roamast: eth4: disconnect weak signal strength station [30:23:03:01:ad:57]
Dec 18 09:45:06 roamast: eth4: remove client [30:23:03:01:ad:57] from monitor list

Just restarting the ASUS doesn't seem to help, internet stays disconnected until I restart the CM1100. The last couple of outages I restarted the CM1100 *only* and the internet comes back up in a few minutes.

Everyone raves about the CM1100, and the ASUS was experiencing internet drops before that, and there are tons of complaints on here about the ASUS dropping internet, so I'm inclined to think that's the culprit. Am I crazy?

I've got a TP-Link AX3000 coming today, so I'm going to swap them out for a few days and see what happens. If the internet stays stable then I guess I know who the culprit is. If it's still dropping then I'll try putting the original CM1000 back in place.

It's a shame, I really like having a separate node (connected by ethernet backhaul) in the kitchen where 5ghz is a little spotty. But not having the internet at all is definitely worse.

 

[MoneyMan]

Got the XT8 a month ago (end of Nov 2020) and have had nothing but trouble. The first few days it was dropping the internet multiple times per day (ethernet to the rest of the house was fine, wifi devices stayed connected, but no internet access). I installed the latest 386 beta 9.0.0.4.386_41157 and it seemed to calm down and stay stable for a couple of weeks.

Monday night the internet was dropping out again and I thought "here we go again" but this time was something different—the cable modem (Netgear CM1000) had all lights go off and then reconnect. It happened several times in the span of 30 minutes, and unplugging and plugging back in sometimes would restart it, sometimes not (the ethernet light would stay orange). Ran to Costco and got a CM1100 and the same thing started happening! I realized I was using the same power supply from the CM1000 and it dawned on me that that's what was going bad. Used the CM1100 power supply and everything was green and stable again.

But ever since replacing the modem, the ASUS is back to dropping the internet at least once a day. When it does, all lights on the CM1100 stay lit and the ethernet is blinking. Looking at the CM1100 admin page I don't see anything different than when the internet is working properly. I checked the ASUS logs and in the last two instances of the internet dropping I saw this message, which Google returns zero results for on the entire internet:

Dec 18 09:44:57 acsd: eth4 received event: tx pkt delay suddently jump

(Misspellings are in the logs)

Both times, this message was followed by several Disassoc messages within seconds:

Dec 18 09:45:00 wlceventd: wlceventd_proc_event(474): eth4: Deauth_ind 64:16:66:45:92:68, status: 0, reason: Unspecified reason (1)
Dec 18 09:45:00 wlceventd: wlceventd_proc_event(510): eth4: Auth 64:16:66:45:92:68, status: Successful (0)
Dec 18 09:45:00 wlceventd: wlceventd_proc_event(539): eth4: Assoc 64:16:66:45:92:68, status: Successful (0)
Dec 18 09:45:05 wlceventd: wlceventd_proc_event(491): eth4: Disassoc 24:F5:A2:FB:F7:EB, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 18 09:45:05 wlceventd: wlceventd_proc_event(491): eth4: Disassoc 24:F5:A2:FB:F7:EB, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 18 09:45:05 wlceventd: wlceventd_proc_event(491): eth4: Disassoc 24:F5:A2:FD:91:89, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 18 09:45:05 wlceventd: wlceventd_proc_event(491): eth4: Disassoc 24:F5:A2:FD:91:89, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 18 09:45:05 wlceventd: wlceventd_proc_event(474): eth4: Deauth_ind 18:B4:30:06:1A:AE, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Dec 18 09:45:06 wlceventd: wlceventd_proc_event(474): eth4: Deauth_ind B4:181:E2:5B:0C, status: 0, reason: Unspecified reason (1)
Dec 18 09:45:06 wlceventd: wlceventd_proc_event(510): eth4: Auth B4:181:E2:5B:0C, status: Successful (0)
Dec 18 09:45:06 wlceventd: wlceventd_proc_event(539): eth4: Assoc B4:181:E2:5B:0C, status: Successful (0)
Dec 18 09:45:06 wlceventd: wlceventd_proc_event(491): eth4: Disassoc 30:23:03:01:AD:57, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 18 09:45:06 wlceventd: wlceventd_proc_event(491): eth4: Disassoc 30:23:03:01:AD:57, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Dec 18 09:45:06 roamast: [EXAP]Deauth old sta in 0 0: 30:23:03:01:AD:57
Dec 18 09:45:06 roamast: eth4: disconnect weak signal strength station [30:23:03:01:ad:57]
Dec 18 09:45:06 roamast: eth4: remove client [30:23:03:01:ad:57] from monitor list

Just restarting the ASUS doesn't seem to help, internet stays disconnected until I restart the CM1100. The last couple of outages I restarted the CM1100 *only* and the internet comes back up in a few minutes.

Everyone raves about the CM1100, and the ASUS was experiencing internet drops before that, and there are tons of complaints on here about the ASUS dropping internet, so I'm inclined to think that's the culprit. Am I crazy?

I've got a TP-Link AX3000 coming today, so I'm going to swap them out for a few days and see what happens. If the internet stays stable then I guess I know who the culprit is. If it's still dropping then I'll try putting the original CM1000 back in place.

It's a shame, I really like having a separate node (connected by ethernet backhaul) in the kitchen where 5ghz is a little spotty. But not having the internet at all is definitely worse.

HI Cannikin, did you manage to resolve your issues, I've just had the same error message, after several weeks of trying different things to make the XT8 (main plus node) work properly:

"Jan 30 03:15:33 acsd: eth4 received event: tx pkt delay suddently jump"

Followed by lots of:

"Jan 30 03:15:33 acsd: acs_candidate_score_busy(948): eth4: busy check failed for chanspec: 0x180a
Jan 30 03:15:33 acsd: acs_candidate_score_intf(1000): eth4: intf check failed for chanspec: 0x180a"

BTW, this is a great forum, have learnt an awful lot abut my new Asus kit, thank you all!

 

[thiggins]

Are all devices disconnecting?
What band are the devices on and what's their signal level?
Next time it happens, try pinging the router IP address. Unless you changed it, I think the ASUS default is 192.168.50.1.

 

[Cannikin]

Nope, I ended up returning them and getting a TP-Link AX3000. Not a single issue, it’s worked flawlessly.