(Only had hub 2 months) ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism

[McG_A_1]

Hi there, 

2 months ago, acquired a 'new' or possibly refurbished virgin media hub due to our old one basically on its last legs, since then no issues until yesterday.

Out of no where, net cut out and recognized the dreaded wifi light flickering, which i have encountered with previous hubs. 

This happened also an hour ago and I'm now dreading this is going to be continuous again. 

I know the cause of the hub doing this kernal / oops panic is the internal CPU restarting and also overloaded. 

My question is, why is this happening and what is possibly causing this after only 2 months?  for a CPU to be getting overloaded that quickly? 

please find attached,  the network logs and  also downstream  pre rs errors and post (the pre rs errors seem to show a few on different channels) 

Network log ----- 

26/09/2024 20:39:35 critical TLV-11 - Failed to set duplicate elements;CM-MAC=**********************;CMTS-MAC=**********************:ad;CM-QOS=1.1;CM-VER=3.0;
26/09/2024 20:36:2 notice NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**********************;CMTS-MAC=**********************:ad;CM-QOS=1.1;CM-VER=3.0;
25/09/2024 14:16:21 Warning! LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**********************;CMTS-MAC=**********************:ad;CM-QOS=1.1;CM-VER=3.0;
25/09/2024 14:07:54 notice NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**********************;CMTS-MAC=**********************:ad;CM-QOS=1.1;CM-VER=3.0;
25/09/2024 02:16:36 critical No Ranging Response received - T3 time-out;CM-MAC=**********************;CMTS-MAC=**********************:ad;CM-QOS=1.1;CM-VER=3.0;
24/09/2024 02:21:37 notice DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053+voc-b.cm modified;CM-MAC=**********************;CMTS-MAC=**********************:ad;CM-QOS=1.1;CM-VER=3.0;

---downstream printscreen could not copy and paste results---- 

Any help would be gratefully appreciated before i contact virgin media tomorrow to grab a new hub as can't keep continuously dealing with this  

Thanks 

A

[McG_A_1]

Update, decided to see if readjusting the co-axle cable would do any good and see if issues decreased and or performance improved,  Will still be contacting virgin after keeping a close monitor on the situation.

[Client62]

Try to Copy / Paste the text of the the Hub signal levels , that can work better than a screen shot.

Reports of the Intel ATOM CPU errors were common years ago, a Hub replacement may be the only option.

[jbrennand]

Re. the Atom Error message

See message 8 in here

https://community.virginmedia.com/t5/Networking-and-WiFi/NOTICE-ATOM-is-restarted-due-to-Kernel-oops...

[McG_A_1]

Phoned up virgin media, no help at all, basically refused to send out a new hub, if issue persists over weekend and into monday will be phoning again. 

not happy 

[Alex_RM]

Hi McG_A_1,

Thanks for posting and sorry to see you're having some connection issues. 

Can you confirm if the problem is over a wired or wireless connection, or both? Having a quick look from our side there are no immediate issues showing.

Alex_Rm

[jbrennand]

From an old post.... I cant comment on its "accuracy".

_______________

"The ATOM issue is well known and is due to a flaw in the Intel ATOM chip used in the Hub 3. The VM Forum Team know this full well but won’t admit it even though this flaw is fully in the public domain. Adduxi has explained the effect of the fault and VM should not be supplying this flawed to device to its customers.

So when the FT say they can’t see anything wrong in your stats, the Network Log shows something very wrong and I suspect that editorial policy prevents them from acknowledging the fact."

[McG_A_1]

Hi Alex, the issue seems to have stopped last Saturday, sorry my reply to you is late, i have been keeping a watch on the network logs and so far so good and all devices connected to the hub are wireless, i had a theory it could of been to many devices on the network overloading it.