One Hub Watchdog Resets (Cause 0x3)

williamjt97 — Wed, 03 Aug 2022 20:54:50 GMT

After my last post (11/09/21) I didn't have any disconnects for a shortwhile but they did come back after a bit. But recently they have ramped back up again in how many are happening per week.

When looking in the Event log for the router every time it's disconnecting the message that appears says

"Boot reason: watchdog reset (cause: 0x3)"

I have tried all the different fixes I could find from various online posts (turning firewall off, having the router be the only thing plugged into a dual wall socket, turn 5ghz wifi off, turn 2.4ghz wifi off, reset it, leave it turn off for an hour but sadly none of these have resolved the issue.

According to this post here the issue was with the router itself as a replacement one fixed their issue.

Event log:

21:29:34, 03 Aug. ( 109.980000) Admin login successful by 192.168.1.67 on HTTP 21:29:34, 03 Aug. IN: BLOCK [15] Default policy (TCP [20.54.37.64]:443->[146.90.122.88]:56644 on ppp3) 21:29:30, 03 Aug. BLOCKED 1 more packets (because of Default policy) 21:29:30, 03 Aug. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [104.98.228.241]:443->[146.90.122.88]:60722 on ppp3) 21:29:29, 03 Aug. IN: BLOCK [15] Default policy (TCP [20.54.37.64]:443->[146.90.122.88]:56644 on ppp3) 21:29:26, 03 Aug. ( 102.080000) New GUI session from IP 192.168.1.67 21:29:26, 03 Aug. BLOCKED 1 more packets (because of Default policy) 21:29:25, 03 Aug. IN: BLOCK [15] Default policy (TCP [20.54.37.64]:443->[146.90.122.88]:56644 on ppp3) 21:29:25, 03 Aug. BLOCKED 2 more packets (because of Default policy) 21:29:24, 03 Aug. IN: BLOCK [15] Default policy (TCP [20.54.37.64]:443->[146.90.122.88]:56644 on ppp3) 21:29:23, 03 Aug. IN: BLOCK [15] Default policy (TCP [31.192.111.224]:57812->[146.90.122.88]:5986 on ppp3) 21:29:23, 03 Aug. BLOCKED 1 more packets (because of Default policy) 21:29:22, 03 Aug. ( 97.790000) CWMP: session closed due to error: WGET TLS error 21:29:22, 03 Aug. IN: BLOCK [15] Default policy (TCP [135.92.6.73]:443->[146.90.122.88]:50772 on ppp3) 21:29:21, 03 Aug. ( 96.480000) NTP synchronization success! 21:29:19, 03 Aug. ( 94.420000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username 21:29:19, 03 Aug. ( 94.410000) CWMP: Session start now. Event code(s): '1 BOOT' 21:29:19, 03 Aug. IN: BLOCK [15] Default policy (TCP [54.236.161.4]:443->[146.90.122.88]:56854 on ppp3) 21:29:19, 03 Aug. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.67]:60722->[104.98.228.241]:443 on ppp3) 21:29:18, 03 Aug. ( 93.600000) NTP synchronization start 21:29:17, 03 Aug. ( 92.630000) WAN operating mode is VDSL 21:29:17, 03 Aug. ( 92.630000) Last WAN operating mode was VDSL 21:29:16, 03 Aug. ( 91.500000) PPP IPCP Receive Configuration ACK 21:29:16, 03 Aug. ( 91.500000) PPP IPCP Send Configuration Request 21:29:16, 03 Aug. ( 91.490000) PPP IPCP Receive Configuration NAK 21:29:16, 03 Aug. ( 91.490000) PPP IPCP Send Configuration ACK 21:29:16, 03 Aug. ( 91.480000) PPP IPCP Receive Configuration Request 21:29:16, 03 Aug. ( 91.480000) PPP IPCP Send Configuration Request 21:29:15, 03 Aug. ( 90.530000) PPPoE is up - Down Rate=79995Kbps, Up Rate=20000Kbps; SNR Margin Down=12.8dB, Up=12.7dB 21:29:15, 03 Aug. ( 90.520000) CHAP authentication successful 21:29:15, 03 Aug. ( 90.480000) CHAP Receive Challenge 21:29:15, 03 Aug. ( 90.480000) Starting CHAP authentication with peer 21:29:15, 03 Aug. ( 90.480000) PPP LCP Receive Configuration ACK 21:29:15, 03 Aug. ( 90.480000) PPP LCP Send Configuration Request 21:29:15, 03 Aug. ( 90.470000) PPP LCP Receive Configuration Reject 21:29:15, 03 Aug. ( 90.470000) PPP LCP Send Configuration ACK 21:29:15, 03 Aug. ( 90.470000) PPP LCP Receive Configuration Request 21:29:15, 03 Aug. ( 90.470000) PPP LCP Send Configuration Request 21:29:11, 03 Aug. ( 86.240000) PTM over DSL is up 21:28:55, 03 Aug. ( 70.970000) CWMP: session closed due to error: Could not resolve host 21:28:55, 03 Aug. ( 70.960000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username 21:28:55, 03 Aug. ( 70.960000) CWMP: Session start now. Event code(s): '1 BOOT,4 VALUE CHANGE' 21:28:25, 03 Aug. ( 40.690000) CWMP: session closed due to error: Could not resolve host 21:28:22, 03 Aug. ( 37.230000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username 21:28:22, 03 Aug. ( 37.220000) CWMP: Session start now. Event code(s): '1 BOOT,4 VALUE CHANGE' 21:28:21, 03 Aug. ( 36.950000) CWMP: Initializing transaction for event code 1 BOOT 21:28:20, 03 Aug. ( 35.780000) WiFi auto selected channel 48 21:28:20, 03 Aug. ( 35.780000) 36-95::40-95::44-95::48-93::52-93::56-94::60-93::64-93::100-94::104-94::108-96::112-96::116-96::120-97::124-97::128-98 21:28:20, 03 Aug. ( 35.780000) 5 GHz Wireless: Rescan, Reason: 'Power-up' 21:28:20, 03 Aug. ( 35.780000) WiFi auto selected channel 6 21:28:20, 03 Aug. ( 35.780000) 1-97::2-96::3-97::4-96::5-97::6-96::7-97::8-97::9-98::10-98::11-99::12-98::13-98 21:28:20, 03 Aug. ( 35.770000) 2.4 GHz Wireless: Rescan, Reason: 'Power-up' 21:28:20, 03 Aug. ( 35.770000) Wire Lan Port 4 up 21:28:20, 03 Aug. ( 35.070000) WAN Auto-sensing running. 21:28:16, 03 Aug. ( 31.350000) System up, firmware version: 4.7.5.1.83.8.289.1.3 21:28:14, 03 Aug. ( 29.030000) WPA2 mode selected 21:28:14, 03 Aug. ( 29.030000) WPS enabled 21:28:11, 03 Aug. ( 26.850000) WPA2 mode selected 21:28:11, 03 Aug. ( 26.850000) WPS enabled 21:28:02, 03 Aug. ( 17.800000) System start 21:28:02, 03 Aug. ( 17.800000) Boot reason: watchdog reset (cause: 0x3)

Before this section of the event log the last message was

19:30:28, 03 Aug. (451878.000000) NTP synchronization success!

2 hours before the disconnect.

The router will reboot itself, flash green then solid blue then flash orange then flask green to solid blue again, at this point the internet is working again.

While it's rebooting there is no noise or static on the landline just the normal dial tone.

Could this be looked into?

Thank-you.

Re: One Hub Watchdog Resets (Cause 0x3)

williamjt97 — Wed, 03 Aug 2022 21:06:12 GMT

After posting this it happened again, except this time the event log jumped to the future!

01:01:06, 30 Aug.	( 67.470000) Admin login successful by 192.168.1.67 on HTTP
01:00:40, 30 Aug.	( 40.860000) CWMP: session closed due to error: Could not resolve host
01:00:38, 30 Aug.	( 39.610000) New GUI session from IP 192.168.1.67
01:00:36, 30 Aug.	( 37.170000) CWMP: Server URL: https://pbthdm.bt.mo; Connecting as user: ACS username
01:00:36, 30 Aug.	( 37.170000) CWMP: Session start now. Event code(s): '1 BOOT,4 VALUE CHANGE'
01:00:36, 30 Aug.	( 36.890000) CWMP: Initializing transaction for event code 1 BOOT
01:00:34, 30 Aug.	( 35.660000) WiFi auto selected channel 48
01:00:34, 30 Aug.	( 35.660000) 36-95::40-95::44-94::48-94::52-93::56-93::60-93::64-93::100-95::104-96::108-96::112-96::116-96::120-97::124-96::128-98
01:00:34, 30 Aug.	( 35.650000) 5 GHz Wireless: Rescan, Reason: 'Power-up'
01:00:34, 30 Aug.	( 35.650000) WiFi auto selected channel 11
01:00:34, 30 Aug.	( 35.650000) 1-95::2-97::3-96::4-95::5-96::6-96::7-97::8-98::9-98::10-99::11-103::12-97::13-99
01:00:34, 30 Aug.	( 35.640000) 2.4 GHz Wireless: Rescan, Reason: 'Power-up'
01:00:34, 30 Aug.	( 35.640000) Wire Lan Port 4 up
01:00:33, 30 Aug.	( 34.660000) WAN Auto-sensing running.
01:00:30, 30 Aug.	( 31.160000) System up, firmware version: 4.7.5.1.83.8.289.1.3
01:00:28, 30 Aug.	( 28.900000) WPA2 mode selected
01:00:28, 30 Aug.	( 28.900000) WPS enabled
01:00:25, 30 Aug.	( 26.620000) WPA2 mode selected
01:00:25, 30 Aug.	( 26.620000) WPS enabled
01:00:16, 30 Aug.	( 17.600000) System start
01:00:16, 30 Aug.	( 17.600000) Boot reason: watchdog reset (cause: 0x3)

After refreshing the page log is now back at 3rd Aug and correct time.

Re: One Hub Watchdog Resets (Cause 0x3)

jab1 — Thu, 04 Aug 2022 06:14:20 GMT

@williamjt97 Sounds like a failing Hub - how long have you had it?

Re: One Hub Watchdog Resets (Cause 0x3)

williamjt97 — Thu, 04 Aug 2022 11:37:17 GMT

I've had it since July last year.

Re: One Hub Watchdog Resets (Cause 0x3)

jab1 — Thu, 04 Aug 2022 11:41:14 GMT

@williamjt97 OK, not that long, but from memory, there seemed to be a dodgy batch of Hubs at one point (can't remember when), this may be one.

A member of the Help Team will pick this up at some point, hopefully read the whole topic, and agree with me that it needs replacing.

Re: One Hub Watchdog Resets (Cause 0x3)

bobpullen — Thu, 04 Aug 2022 11:44:58 GMT

@williamjt97 - showing signs of a physical fault. I've arranged for a replacement hub to be shipped to you. Should turn up on Saturday all being well.

Re: One Hub Watchdog Resets (Cause 0x3)

williamjt97 — Thu, 04 Aug 2022 13:01:01 GMT

Thank-you very much, will let you know how it gets on.

Re: One Hub Watchdog Resets (Cause 0x3)

williamjt97 — Tue, 16 Aug 2022 11:09:47 GMT

I've had the router for a week now and has been working great. 0 crashes so far. Thank-you

topic Re: One Hub Watchdog Resets (Cause 0x3) in My Router

One Hub Watchdog Resets (Cause 0x3)

Re: One Hub Watchdog Resets (Cause 0x3)

Re: One Hub Watchdog Resets (Cause 0x3)

Re: One Hub Watchdog Resets (Cause 0x3)

Re: One Hub Watchdog Resets (Cause 0x3)

Re: One Hub Watchdog Resets (Cause 0x3)

Re: One Hub Watchdog Resets (Cause 0x3)

Re: One Hub Watchdog Resets (Cause 0x3)