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

[temjin1997]

Hi, 

i've got the router restart several time. here is the logs that got from router

Time Priority Description
19/01/2023 18:08:25 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/01/2023 18:06:31 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;
19/01/2023 05:01:25 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/01/2023 08:56:11 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/01/2023 08:12: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;
17/01/2023 06:09:5 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/01/2023 18:44:21 notice DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/01/2023 18:44:21 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/01/2023 12:03:12 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/01/2023 20:23:38 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/01/2023 19:27:43 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/01/2023 06:44:22 notice DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/01/2023 06:44:22 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/01/2023 21:58:21 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/01/2023 17:47:44 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/01/2023 04:05:24 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/01/2023 18:44:20 notice DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/01/2023 18:44:20 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/01/2023 10:55:59 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/01/2023 00:04:24 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

What should i do to fix it? it's impacting my WFH. Hope if there have any  respond. 

Thanks, 

Jerry

[Adduxi]

See this thread. https://community.virginmedia.com/t5/Networking-and-WiFi/Router-Reboots/m-p/5202301

[temjin1997]

Thanks Adduxi, 

From the forum mentioned, Basically, the chip gets overloaded. I should be entitled to change up to a Hub 4.

Can Forum Team to send me a Hub 4?

[Molly_T]

Hi temjin1997! 👋 Welcome to the community - thank you for posting! 

Sorry to hear you are having issues with your hub rebooting itself. I'd like to offer some help! 

I've had a quick look and from what we can see, your hub has only had 3 disconnections over the past month. 2 Of those disconnections have happened in the past week, and the other was almost exactly a month ago. You should also be able to see this yourself here 👉samknows.com/realspeed. It also looks like the uptime on the hub is substantial, at over 29 days. (Uptime usually indicates the amount of time since the last reboot.) This is a little inconsistent with the information you have given in your post. 

Are you able to give a little more information as to why you believe the chip is getting overloaded? 

If you can also let us know how often the hub is rebooting from your end and if there is any pattern happening with these reboots? (Eg times of day, days of the week). 

I can appreciate this would be a concern when working from home, but we do also need to perform some checks ahead of sending a technician out to investigate further, and replace the router if needed. As the data we are seeing vs what you are reporting does not currently match, I'm also going to send you a PM to confirm a few account details so we can look into this further for you. You can find my PM in the top right corner of the page in your Inbox 📩. 

We can then return to this public thread with an update when possible. 

Thanks for your patience in the meantime! All the best. 🌞

[temjin1997]

Hi Molly, 

The web link showing Hub 3 have potential issue on getting overload 

https://www.ispreview.co.uk/index.php/2018/08/intel-coughs-to-puma-cpu-flaw-that-hit-virgin-media-hu... 

But, I am finding a way to solve my disconnection problem, not trying to technical discussion. 

If you can easy to solve my issue, i will follow the instruction.

You can show me why the logs showing that and how to solve it?

24/01/2023 08:50: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;
19/01/2023 18:06:31 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;
18/01/2023 08:12: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;

and why the DHCP renew warning?

16/01/2023 18:44:21 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

and why there have T3 time-out?

18/01/2023 08:56:11 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

and i would like to clarify my logs is grep from Virgin Media Hub3.0. I didn't show any inconsistent inforamtion there.

Thanks, 

Jerry

[Adduxi]

You can ignore the DHCP renew warnings on any VM Hub, it's just the way the WAN IP lease is given.