One Hub Watchdog Resets (cause 0x3)

[#1]

On 4 Feb 2019 I arranged to renew my broadband/phone contract. Although I have had at least three years of totally trouble free service from my existing router (TP-Link TD 9980) I wanted to use a router with 802.11 ac capabilities. The PN service agent kindly arranged to ship a Plusnet Hub One to me.  This was successfully installed on 7 Feb with me just having to manually enter my user name and password.

The firmware was auto-updated on 9^th February.  Broadband and WIFI (on both 2.4G and 5G) performance has  been fine.  The main problem has been a number of unexplained router reboots due to watchdog resets (cause 0x3).  I could go back to my old router but I find the 5G wireless performance of the Hub One represents a significant improvement that I would like to keep. 

21:06:34, 13 Feb.	( 32.700000) System up, firmware version: 4.7.5.1.83.8.263
21:06:18, 13 Feb.	( 17.370000) System start
21:06:18, 13 Feb.	( 17.370000) Boot reason: watchdog reset (cause: 0x3)
09:39:10, 10 Feb.	( 32.640000) System up, firmware version: 4.7.5.1.83.8.263
09:38:55, 10 Feb.	( 17.710000) System start
09:38:55, 10 Feb.	( 17.710000) Boot reason: watchdog reset (cause: 0x3)
09:03:35, 10 Feb.	( 31.850000) System up, firmware version: 4.7.5.1.83.8.263
09:03:20, 10 Feb.	( 17.540000) System start
00:08:46, 09 Feb.	( 32.770000) System up, firmware version: 4.7.5.1.83.8.263
00:08:32, 09 Feb.	( 18.390000) System start TR069
09:28:20, 07 Feb.	( 29.020000) System up, firmware version: 4.7.5.1.83.8.259
09:28:05, 07 Feb.	( 13.990000) System start from GUI
09:07:38, 07 Feb.	( 28.910000) System up, firmware version: 4.7.5.1.83.8.259
09:07:24, 07 Feb.	( 14.600000) System start

Google searches have not yielded any meaningful information other that to suggest that the watchdog resets are linked to firmware issues on both on the PlusNet router( and its BT Home Hub equivalent) . In particular I am unable to find any information on reset cause 0x3. More drastic solutions propose using an alternative make of router.

I would be grateful if @bobpullen or anyone could assist is resolving this issue.

TIA

Chris

[#2]

Hi @chrisjbzero,

I'm sorry to hear that you're experiencing this issue with the connection. Having looked at your account today, I can't see anything that would explain these drops and at this stage it's hard to say if they're anomalous or indicative of another issue.

If this does occur again, it may be worth temporarily setting the other router up to see if this resolves the issue or not.

[#3]

The Hub One has experienced two more resets since the OP.  I wonder if anyone knows what triggers resets with cause value 0x3?

[#4]

---

@chrisjbzero wrote:

I wonder if anyone knows what triggers resets with cause value 0x3?

Possible causes:-

0x0: normal watchdog reset
0x1: watchdog reset caused by wireless PCI failure
0x2: watchdog reset caused by kernel not responding to interrupts
0x3: Returned if both bits 0x1 and 0x2 are set.

I'm not seeing any reference to the crash in the logs I've just extracted from your device, but that could be because they've since been rotated/cleared. When was the last time it happened?

Anyway, looks like it could be a hardware failure. I've arranged for a replacement device to be shipped. Should hopefully arrive with you tomorrow. Please let me know how you get on with it.

[#5]

Thanks @bobpullen for the explanation of the reset codes - Interesting.  I'm not sure why you cannot see the log data.  Anyway I reproduce below the current data for the Boot log file which provides timing information.  Examination of the All log shows that there is nothing at all being logged  in the 2 hours or so prior to the latest reset.

22:10:47, 14 Feb.	( 33.290000) System up, firmware version: 4.7.5.1.83.8.263
22:10:31, 14 Feb.	( 17.710000) System start
22:10:31, 14 Feb.	( 17.710000) Boot reason: watchdog reset (cause: 0x3)
19:29:39, 14 Feb.	( 31.410000) System up, firmware version: 4.7.5.1.83.8.263
19:29:25, 14 Feb.	( 17.250000) System start
19:29:25, 14 Feb.	( 17.250000) Boot reason: watchdog reset (cause: 0x3)
13:49:25, 14 Feb.	( 32.830000) System up, firmware version: 4.7.5.1.83.8.263
13:49:09, 14 Feb.	( 17.460000) System start
13:49:09, 14 Feb.	( 17.450000) Boot reason: watchdog reset (cause: 0x3)
21:06:34, 13 Feb.	( 32.700000) System up, firmware version: 4.7.5.1.83.8.263
21:06:18, 13 Feb.	( 17.370000) System start
21:06:18, 13 Feb.	( 17.370000) Boot reason: watchdog reset (cause: 0x3)
09:39:10, 10 Feb.	( 32.640000) System up, firmware version: 4.7.5.1.83.8.263
09:38:55, 10 Feb.	( 17.710000) System start
09:38:55, 10 Feb.	( 17.710000) Boot reason: watchdog reset (cause: 0x3)
09:03:35, 10 Feb.	( 31.850000) System up, firmware version: 4.7.5.1.83.8.263
09:03:20, 10 Feb.	( 17.540000) System start
00:08:46, 09 Feb.	( 32.770000) System up, firmware version: 4.7.5.1.83.8.263
00:08:32, 09 Feb.	( 18.390000) System start TR069
09:28:20, 07 Feb.	( 29.020000) System up, firmware version: 4.7.5.1.83.8.259
09:28:05, 07 Feb.	( 13.990000) System start from GUI
09:07:38, 07 Feb.	( 28.910000) System up, firmware version: 4.7.5.1.83.8.259
09:07:24, 07 Feb.	( 14.600000) System start

Also attached router Details:

1. Product name:	Plusnet Hub
2. Serial number:	+081441+NQ83931579
3. Firmware version:	Software version 4.7.5.1.83.8.263 Last updated 08/02/19
4. Board version:	Plusnet Hub One
5. DSL uptime:	0 days, 13:40:16
6. Data rate:	19999 / 74541
7. Maximum data rate:	20951 / 77964
8. Noise margin:	6.1 / 3.4
9. Line attenuation:	8.7 / 8.3
10. Signal attenuation:	8.7 / 8.3
11. Data sent/received:	34.5 MB / 468.2 MB
12. Broadband username:	XXXXXXXX@plusdsl.net
13. 2.4 GHz Wireless network/SSID:	XXXXXXXXXXXXX
14. 2.4 GHz Wireless connections:	Enabled (802.11 b/g/n (up to 144 Mb/s))
15. 2.4 GHz Wireless security:	WPA2
16. 2.4 GHz Wireless channel:	Automatic (Smart Wireless)
17. 5 GHz Wireless network/SSID:	XXXXXXXXXXXXXX
18. 5 GHz Wireless connections:	Enabled (802.11 a/n/ac (up to 1300 Mb/s))
19. 5 GHz Wireless security:	WPA2
20. 5 GHz Wireless channel:	Automatic (Smart Wireless)
21. Firewall:	Default
22. MAC Address:	XXXXXXXXXX:5a:a6
23. Modulation:	G.993.2 Annex B
24. Software variant:	AA
25. Boot loader:	1.0.0

Should  you need any other log file data I'm happy to provide.

Also many thanks indeed for arranging provision of a replacement router.  I'll report back.

Regards

Chris

[#6]

Thanks Chris,

I can see reference in the system start logs, but the crash dumps are empty. What devices do you have connected to the router by the way? I don't suppose you have a NAS/storage appliance?

[#7]

 Hi @bobpullen,  Ah, I understand the point your making now about not seeing crash dumps.  Sorry for the confusion on my part.

Connection configuration is as follows:

Port 1 - not connected

Port 2 - Ethernet connected to Netgear Stora (NAS) but the NAS is only powered up when manual backups are taken.  The NAS has been off since the Hub One has been installed.

Port 3 - Ethernet connected to  Devolo Dlan 200 AVsmart+ -> Devolo Dlan 200 AVsmart+ -> XyXel NGB4604 router(acting as AP with DHCP server off).  ZyXel has two Ethernet connections to Humax HDR110s freesat recorder and Panasonic TX 50 TV.

Port 4- Ethernet connected to Windows 7 based Desktop computer.

Examination of the Wire Lan log only shows ports 3 and 4 as being in use.  Nevertheless given the above might there be a problem with connection of the unpowered NAS?  

Regards

Chris

[#8]

Thanks. We've seen the 0x3 errors coincide with large wi-fi transfers over 5GHz to a NAS device before, thus me asking. In circumstances it is known to cause voltage drops that lead to the crash you're describing. In those cases, it's a manufacturing tolerance issue and the hub has to be replaced. I'm kind of hoping the same applies here once you've had the chance to test with the replacement that's on its way to you.

[#9]

Hi Bob @bobpullen  ,

Update-

The replacement has been installed without any problems.  Early this morning the latest firmware (....263) auto installed and all is looking good so far.  

Regards

Chris

[#10]

Glad to hear it Chris.

Let me know if the situation deteriorates.

[#11 · Accepted solution]

Everything still looking good @chrisjbzero ?

[#12]

Hi @bobpullen, The router has been running now without any problems for 8 days. I am happy that the problem has been fixed with the replacement.  So, many thanks for all your help.

Regards

Chris