I know there are multiple threads on this topic, but I can't find anything in those that helps me so here is my situation.
BT inifinity user with Home Hub 5 type A with firmware at version 184.108.40.206.220.127.116.11.11. Desktop connected via ethernet, laptop phones etc on wifi.
As of the last few days, hub is rebooting every 15-16 minutes. It did this a couple of weeks ago too and hub power reset cured it then. This time though I've tried the normal reset, a power reset and a revert to factory settings reset and none of these helps. I've done a quiet line check, including through the period when the hub resets and nothing heard. After the reboot is complete the down speed is about 46.9Mbps and up speed 7.4Mbps, not far off the line maximums.
I've done some analysis of the event log - this always records something like this:
|11:09:26, 22 Aug.||( 13.300000) System start|
|11:09:26, 22 Aug.||( 13.300000) Boot reason: watchdog reset|
|11:08:52, 22 Aug.||( 963.290000) PPP LCP Send Termination Request [User request]|
|11:08:51, 22 Aug.||( 961.760000) The system is going DOWN for reboot.|
|11:08:51, 22 Aug.||( 961.760000) OpenRG is going for reboot by IPC command|
|11:08:46, 22 Aug.||( 956.680000) OpenRG will go down for reboot in 5 seconds|
There is nothing in the log just prior to the "reboot in 5 seconds" messages that suggests anything was happening that might be triggering the reboot.
This is very much regular, not random . Using the "NTP sync success" event as an indicator of a completed reboot, the times to the following reboot start are almost constant - just over 12 mins every time:
|Reboot complete||Next reboot start||Up time|
|12:19:11||NTP synchronization success!||12:31:28||The system is going DOWN for reboot.||00:12:17|
|12:35:48||NTP synchronization success!||12:48:10||The system is going DOWN for reboot.||00:12:22|
|12:52:29||NTP synchronization success!||13:04:48||The system is going DOWN for reboot.||00:12:19|
|13:09:06||NTP synchronization success!||13:21:24||The system is going DOWN for reboot.||00:12:18|
|13:25:44||NTP synchronization success!||13:38:02||The system is going DOWN for reboot.||00:12:18|
|13:42:19||NTP synchronization success!||13:54:34||The system is going DOWN for reboot.||00:12:15|
|13:58:53||NTP synchronization success!||14:11:12||The system is going DOWN for reboot.||00:12:19|
|14:15:34||NTP synchronization success!||14:27:50||The system is going DOWN for reboot.||00:12:16|
|14:32:12||NTP synchronization success!||14:44:29||The system is going DOWN for reboot.||00:12:17|
|14:48:57||NTP synchronization success!||15:01:13||The system is going DOWN for reboot.||00:12:16|
|15:05:40||NTP synchronization success!||15:17:55||The system is going DOWN for reboot.||00:12:15|
|15:22:13||NTP synchronization success!||15:34:26||The system is going DOWN for reboot.||00:12:13|
|15:38:47||NTP synchronization success!||15:51:07||The system is going DOWN for reboot.||00:12:20|
This suggests to me that the hub is timing out in some way or I suppose it could be something from the exchange end forcing the reboot, but I would expect that to show up in the log. These are taken from the desktop, but the laptop shows the same results.
This perhaps confirms what is suggested on other threads that a recent firmware upgrade may be the cause, but if so is any happening to correct it, or should I be requesting a replacement hub? I recently renewed the contract for 12 months to get the Sport discount so I am in-contract.
Hi @tiptonian and thanks for posting.
I'll be happy to take a closer look at this for you if you wish. Just drop me over an email with your details. You'll get the contact the moderators link in my profile.