Floating latency issues

[Radiocat_FM]

Periodically I have some kind of high ping problem:

Spoiler

ping 8.8.8.8 -t screenshot

I couldn't identify any specific reasons why this starting to happen. Called automated number - no issues detected.

Please, help, as it is really uncomfortable to work during such service state.

BQM:

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1	427000000	4.6	40	256 qam	37
2	251000000	6	40	256 qam	15
3	259000000	5.8	38	256 qam	16
4	267000000	6.8	38	256 qam	17
5	275000000	7.3	40	256 qam	18
6	283000000	7.5	40	256 qam	19
7	291000000	6.9	40	256 qam	20
8	299000000	6.9	38	256 qam	21
9	307000000	6.5	40	256 qam	22
10	315000000	6.4	40	256 qam	23
11	323000000	5.9	40	256 qam	24
12	331000000	6.3	40	256 qam	25
13	339000000	5.8	40	256 qam	26
14	347000000	6	40	256 qam	27
15	355000000	5.3	40	256 qam	28
16	363000000	5.5	40	256 qam	29
17	371000000	5.1	40	256 qam	30
18	379000000	5.3	40	256 qam	31
19	387000000	4.6	40	256 qam	32
20	395000000	4.5	40	256 qam	33
21	403000000	4.4	40	256 qam	34
22	411000000	4.6	40	256 qam	35
23	419000000	4.5	40	256 qam	36
24	435000000	4.5	40	256 qam	38

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	40.9	31	0
2	Locked	40.3	117	0
3	Locked	38.9	37	0
4	Locked	38.6	88	0
5	Locked	40.3	49	0
6	Locked	40.3	27	0
7	Locked	40.9	100	0
8	Locked	38.9	28	0
9	Locked	40.3	178	0
10	Locked	40.9	59	0
11	Locked	40.3	149	0
12	Locked	40.3	12	0
13	Locked	40.3	72	0
14	Locked	40.3	49	0
15	Locked	40.3	50	0
16	Locked	40.9	60	0
17	Locked	40.3	24	0
18	Locked	40.9	103	0
19	Locked	40.3	43	0
20	Locked	40.9	23	0
21	Locked	40.9	29	0
22	Locked	40.9	102	0
23	Locked	40.3	281	0
24	Locked	40.9	20	0

 

[Radiocat_FM]

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1	49599991	36.5	5120	64 qam	1
2	23600000	35	5120	64 qam	5
3	30100000	34.5	5120	64 qam	4
4	36600000	34.5	5120	64 qam	3
5	43100026	35	5120	64 qam	2

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	5	0
2	ATDMA	0	0	1	0
3	ATDMA	0	0	3	0
4	ATDMA	0	0	4	0
5	ATDMA	0	0	1	0

[Radiocat_FM]

Network Log

Time Priority Description

04/01/2023 08:35:41	notice	NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/01/2023 06:48:2	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/01/2023 06:48:2	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/2023 23:08:36	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/12/2022 18:48:2	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/12/2022 18:48:2	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/12/2022 05:07:10	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/12/2022 01:35:3	notice	NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/12/2022 20:43:18	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/12/2022 06:48:1	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/12/2022 06:48:1	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/12/2022 10:54:24	notice	NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/12/2022 12:19:57	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/12/2022 04:24:17	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/12/2022 04:24:17	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/12/2022 22:39:48	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/12/2022 09:38:29	notice	NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/12/2022 04:42:11	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/12/2022 20:11:47	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/12/2022 20:11:47	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[legacy1]

Maybe when something does a download or upload your ping and all other traffic is single rate limited? look at getting a QoS/BWM router.

[Radiocat_FM]

Nah, no downloads at that time. There may be a youtube and netflix in addition to game activities for example, however that doesn't seem like a stress that creates ping issues to Googls dns.

[Radiocat_FM]

Now that seems strange.

Anyone knows if that is normal fpr Hub 3.0?

[carl_pearce]

---

@Radiocat_FM wrote:

Now that seems strange.

Anyone knows if that is normal fpr Hub 3.0?

---

Is that over wireless?

I'd never expect to see 'NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism', so could be a bad HUB.

[Radiocat_FM]

Yeah, its wi-fi connection. Tested from 2 devices at the same time. Both had packet losses

[jpeg1]

Ping times will always vary over WiFi, particularly when more than one device is connected.

The signal levels are all fine, I'd also suspect the Hub showing the ATOM problem. 

[Radiocat_FM]

Seems like ATOM is not a main problem. According to logs last ATOM issue was on 4th Jan, whereas I am getting same issue now, on 7th of Jan, not getting ATOM issues at all.

Time Priority Description

07/01/2023 03:02:47	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/01/2023 19:58:26	notice	NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

At the same time, something strange is happenong to BQM:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/0564536f30eca006751e58010c033cf1b65ef3a9

Though I have the internet. It just lags a lot...