cancel
Showing results for 
Search instead for 
Did you mean: 

lan and wifi drop outs

tige
Tuning in

I have been having trouble  both with wifi and lan connections, its been happening for approx 12 months now, i had an engineer out out and he did some tests, he then fitted some thing to the black cable, and told me it was fixed, for a while it seemed ok, but over the last month or so it has gotten worse, ive been checking the logs and the same ones appear regularly, its my understanding from reading the posts in this forum there is a problem with the cpu on the mb. here are my logs from today. 

Router status

Network Log

Time Priority Description
06/05/2022 06:17:26noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/05/2022 16:12:29noticeNOTICE 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/05/2022 14:26:39noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/05/2022 07:58:35noticeNOTICE 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;
01/01/1970 00:01:40criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/05/2022 06:44:56noticeNOTICE 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/05/2022 06:44:4noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/05/2022 23:56:23criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/05/2022 15:29:23noticeNOTICE 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;
03/05/2022 10:42:13noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:41criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 03:48:22ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 01:41:46criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2022 15:15:21noticeNOTICE 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;
01/01/1970 00:01:44criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2022 11:52:5Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/04/2022 08:50:4noticeNOTICE 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;
27/04/2022 17:03:9ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/04/2022 21:04:44criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/04/2022 03:21:28noticeSW download Successful - Via NMS

I also keep getting a message from the hub when trying to log in saying that some one is already logged in and only one session at at time, i have to restart the hub and wait to log in.

1 ACCEPTED SOLUTION

Accepted Solutions

"NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism"

No, you should not have these entries in your logs.

This is you hub restarting, very possibly due to overheating.

The first thing they should try is to replace the hub to see if it stops.

And no, some pods will not stop it restarting for the love of god.

See where this Helpful Answer was posted

43 REPLIES 43

Akua_A
Forum Team
Forum Team

Hi @tige.

Welcome back to our community forums and thank you for your first posts.

Sorry to hear about the issues you have been having with your service. We can understand this is not ideal and we want to best help. I have been able to access your service and I can see there may be some issues with your downstream power levels. This will need a technician visit to be able to resolve this. For this reason, I have sent you a private message. Please lookout for the purple envelope and provide a response when you can. 

Thanks, 

Akua_A
Forum Team

New around here? Check out the do's and don'ts, in our Community FAQs


Akua_A
Forum Team
Forum Team

Glad to hear this @tige.

Please let me know how the appointment goes and if you need any further help.

Thanks,

Akua_A
Forum Team

New around here? Check out the do's and don'ts, in our Community FAQs


Still getting some problems the chat replaced a cable, its like alays its only short lived. this as from yesterday after the visit.

13/05/2022 21:02:46 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Refresh data
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 202750000 6 38 256 qam 9
2 210750000 5.8 37 256 qam 10
3 218750000 5.5 38 256 qam 11
4 226750000 5.4 37 256 qam 12
5 234750000 4.9 37 256 qam 13
6 242750000 4.5 37 256 qam 14
7 250750000 4 37 256 qam 15
8 258750000 4.4 37 256 qam 16
9 266750000 4.5 37 256 qam 17
10 274750000 4.5 37 256 qam 18
11 282750000 4.3 37 256 qam 19
12 290750000 4.1 37 256 qam 20
13 298750000 4.3 37 256 qam 21
14 306750000 4.1 38 256 qam 22
15 314750000 4.4 38 256 qam 23
16 322750000 4.6 38 256 qam 24
17 330750000 4.8 38 256 qam 25
18 338750000 4.9 37 256 qam 26
19 346750000 4.8 38 256 qam 27
20 354750000 4.6 37 256 qam 28
21 362750000 4.6 38 256 qam 29
22 370750000 5 38 256 qam 30
23 378750000 5.4 38 256 qam 31
24 386750000 5.3 38 256 qam 32


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.6 9920 148
2 Locked 37.6 8497 54
3 Locked 38.9 7141 26
4 Locked 37.6 6045 13
5 Locked 37.6 4859 12
6 Locked 37.6 4190 11
7 Locked 37.6 4476 0
8 Locked 37.6 3047 11
9 Locked 37.6 2512 10
10 Locked 37.6 2144 12
11 Locked 37.6 1679 10
12 Locked 37.6 1490 16
13 Locked 37.6 1300 10
14 Locked 38.2 1007 2
15 Locked 38.6 864 12
16 Locked 38.6 712 13
17 Locked 38.6 674 1
18 Locked 37.6 569 5
19 Locked 38.6 485 12
20 Locked 37.6 487 0
21 Locked 38.6 380 0
22 Locked 38.9 336 2
23 Locked 38.6 314 5
24 Locked 38.6 358 0

Sorry to heat the issue is ongoing @tige.

Are you able to run a broadband quality monitor over the next 24hrs so we can better assess what is going on? https://www.thinkbroadband.com/broadband/monitoring/quality

Thanks,

Akua_A
Forum Team

New around here? Check out the do's and don'ts, in our Community FAQs


Refresh data
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 202750000 5.6 37 256 qam 9
2 210750000 5.5 37 256 qam 10
3 218750000 5.3 38 256 qam 11
4 226750000 5 37 256 qam 12
5 234750000 4.6 37 256 qam 13
6 242750000 4.1 37 256 qam 14
7 250750000 4 37 256 qam 15
8 258750000 4.3 37 256 qam 16
9 266750000 4.3 37 256 qam 17
10 274750000 4.3 37 256 qam 18
11 282750000 4 37 256 qam 19
12 290750000 4 37 256 qam 20
13 298750000 4 37 256 qam 21
14 306750000 4 37 256 qam 22
15 314750000 4.3 38 256 qam 23
16 322750000 4.5 38 256 qam 24
17 330750000 4.5 38 256 qam 25
18 338750000 4.6 37 256 qam 26
19 346750000 4.5 38 256 qam 27
20 354750000 4.5 37 256 qam 28
21 362750000 4.5 38 256 qam 29
22 370750000 4.9 38 256 qam 30
23 378750000 5 38 256 qam 31
24 386750000 5.1 38 256 qam 32

Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 46200000 43 5120 64 qam 1
2 39400000 42.5 5120 64 qam 2
3 25800000 42.2 5120 16 qam 4
4 32600000 42 5120 64 qam 3


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 1 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0

It just annoys me that they have been out twice now and not solved the problem.

16/05/2022 10:28:22 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/05/2022 15:32: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;
14/05/2022 15:58:47 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/05/2022 15:47:15 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;
13/05/2022 21:02:46 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;