on 06-05-2022 07:47
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.
06/05/2022 06:17:26 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/05/2022 16:12: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; |
04/05/2022 14:26:39 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/05/2022 07:58:35 | 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; |
01/01/1970 00:01:40 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/05/2022 06:44:56 | 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/05/2022 06:44:4 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 23:56:23 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 15:29:23 | 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; |
03/05/2022 10:42:13 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:41 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/05/2022 03:48:22 | Error | DHCP 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:46 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/04/2022 15:15:21 | 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; |
01/01/1970 00:01:44 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/04/2022 11:52:5 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/04/2022 08:50:4 | 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; |
27/04/2022 17:03:9 | Error | DHCP 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:44 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/04/2022 03:21:28 | notice | SW 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.
Answered! Go to Answer
on 12-06-2022 10:22
"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.
on 09-05-2022 19:35
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,
on 10-05-2022 17:51
Glad to hear this @tige.
Please let me know how the appointment goes and if you need any further help.
Thanks,
on 14-05-2022 10:02
on 14-05-2022 10:03
on 16-05-2022 10:24
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,
on 16-05-2022 11:31
on 16-05-2022 11:32
on 16-05-2022 11:34
on 16-05-2022 11:35