SR203 random resets and lots of UNKNOWN devices

[JimM1]

@Stevejp Your stats look ok, but as you say only been up 2 hrs, from your description you would only have 3 network connections on the hub, wan ap and switch, you did say you were going to try another switch, if this is not power related,, and not failed fw updates, then next step would be to ask sky for a 3rd hub to try. Cannot think of anything else that would now be causing your symptoms.

[Stevejp]

I have those three witn fixed IPs. Switched to the simple switch seemed to make no difference. Sky are adement that its one of my devices causing the router to reboot.........sounds iffy to me.

[JimM1]

@Stevejp You could try switch and ap in different ports on the hub, but would take some time to test, as I say, power related, or fw updates are the 2 reasons that reboots are requested, think my router is on 7.3.0400r if I remember but not at home to check. And have sr203, se210, xt8 and about 20 devices connected, all on dhcp but using the lan IP assigned instead of fixed IP assigned with zero issues. And hub is about 4 yrs old.

[Stevejp]

Jim.....newsy I can identify if its fw update related?   I'm currently on Firmware Version 7.02.0501.R

[JimM1]

@Stevejp you have older fw so it may be trying to update  7.03.0400r is the latest and unfortunate have to wait till sky pushes it to the router. At least you know what you have now.

[135791113]

Having the same issue for a few weeks now.  Some days it reboots 3 or 4 times, yesterday it was 13 times! Symptom is a full (random) reset of the sky SR203 hub.  By the time you get to it, it has one red light and is restarting.

Setup is SR203 hub with Ultrafast 160Mbs and BY ONT.  Netgear switch off each of the three spare ports.  Wi-Fi on both frequencies with the same SSID. Have 25 to 30 wireless connections (phones, tablets, Sonos, smart plugs, Amazon devices, printer, etc.) and about 15 wired connections (cameras, NAS, Sky Q, 3 Sky mini boxes, TV’s, play station, PC’s, etc.)

Been on to sky a few times, done the hub (SR203) hard reset, ONT power off, Hub PSU on UPS so moved to normal power, etc., etc. ...  and now even had a new hub from sky.  Still have the same issues.

Setup a log server on my NAS so I can keep a proper record.  Although there is a reasonable chance that if there is a crash, the reason will not be written as the hub has crashed.  I have seen Kernal errors every few days, but this does not seem to result in a reboot.  Kernel error I get starts:

• Alert      - [000000b8] *pgd=(eight zeros ... replaced with this comment as eight zeros is a blocked string)
• Alert      - pgd = c0004000
• Alert      - Unable to handle kernel NULL pointer dereference at virtual address 000000b8
• Critical - Internal error: Oops: 17 [#1] PREEMPT SMP ARM
• Critical - Process bcmsw_rx (pid: 656, stack limit = 0xe3314190)
• Critical - …

HOWEVER, I seem to have determined a pattern … If I turn off all my Sky boxes, then the router is fine!  I know any issues with the Sky Q should not cause a problem with the hub, so that leads me to think it is still a hub load/hardware/memory/software issue … but it could be a faulty Sky Q box as that has been playing up a few times (but they always do!). 

• Not too keen on resetting/replacing the Sky Q box as I will lose all the recordings for the whole family!
• Still points to a hub issue but this is my second one.

Any ideas?  Anything in common with your setup?

Thanks.

[135791113]

Update … seems to have been fixed.

Changed the hub again and factory reset the network settings on my Sky Q and 3 mini hubs.

Sky came out and had never seen the issue before.  They agreed it seemed to be the Sky TV boxes doing something wrong that the hub could then not handle, and hence rebooted (crashed).

They changed the hub again for another SR203.  This is the third hub and should be identical .. it looks like it and the software is the current version, however, it seems to be logging more events to my log server, mainly DHCP related.  The last two hubs did not do this, and none of them (including the latest one), list these events in the log if you view it on the hub via the web interface.  The new hub is on software 7.02.0501.R

The engineer then factory reset the network connection on all my sky TV boxes (note no recordings were lost).

Before this was done my hub had increased to a average of two reboots an hour if my Sky Q boxes were on (even if they were on standby).  Now it has been stable with no reboot for four days and counting.

If you ask me, my money would be on a Wi-Fi mesh network issue and I was going to turn off wi-fi on all the sky TV boxes as my next test, however, I am just glad it seems to have gone.

Hope this update helps others … try the network reset of the sky TV boxes first.

John

[135791113]

... continuing my post in case it helps someone else ...

Rebooting issue came back a few days after doing a network reset on the Sky boxes and replacing the Hub. So, Sky have now changed my Sky Q box (so all recordings gone) and it has made no difference, the hub is still rebooting. I currently think it is something to do with the Mesh Wi-Fi but I need to start thinking about removing all the devices I have connected to see where the issue is coming from.

However, even if a device, or the Sky Q boxes are causing an issue ... the hub should be able to cope with it without rebooting!

When the engineer last came, he mentioned moving up to the new Sky Max (Wi-Fi 6) Hub, but the mesh wi-fi does not yet work with the Sky Q boxes. Maybe this is the way to go, no mesh and a better hub?

Thanks, John

[JimM1]

@135791113 If you really want to find your issue, then you have to be prepared to switch it all of on Network connected devices as 1st stage, and you are going to have to leave them all off as you monitor what is going on, plus decide what is your time scale for the re boot. Remote reboot can happen, are you sure that it is not that? Your FW was not at the latest so you know. 

[TimmyBGood]

---

@135791113 wrote:

When the engineer last came, he mentioned moving up to the new Sky Max (Wi-Fi 6) Hub, but the mesh wi-fi does not yet work with the Sky Q boxes. 

---

Sky will now offer Max to addresses with a main Q box and one Mini box.

[135791113]

@TimmyBGood , thanks ... I have a Sky Q 2TB plus 3 mini boxes.  Do you know if they only offering it if you have one mini?  Thanks John

[TimmyBGood]

---

@135791113 wrote:

 Do you know if they only offering it if you have one mini?  

---

Either just the main box by itself, or main box plus a maximum of one Mini box.

[135791113]

I am still having problems with my hub continually restarting, but only when my Sky Q boxes are turned on.

As I have setup a log server, I occasionally capture kernel errors before the hub restarts, e.g. 

• Alert      - [000000b8] *pgd= (eight zeros ... replaced with this comment as eight zeros is a blocked string)
• Alert      - pgd = c0004000
• Alert      - Unable to handle kernel NULL pointer dereference at virtual address 000000b8
• Critical - Internal error: Oops: 17 [#1] PREEMPT SMP ARM
• Critical - Process bcmsw_rx (pid: 656, stack limit = 0xe3314190)
• Critical - …

How can I get to the right person in Sky who could look up the error and tell me exactly what the issue is?

[135791113]

Problem identified, although not yet fully understood. 

I have identified the root cause as a clash between a Sony Bravia 2015 TV and the Sky Q 2TB box when connected via a Netgear switch (tested with both the simple GS308 or smart GS108E).  When both devices are connected (wired) via a switch to a single port on the Sky SR203 Hub, the hub would randomly reboot, sometimes up to twice an hour.

However, if the TV is connected directly to a separate port on the Sky Hub, then the hub would not reboot at all.  However, in the logs in the hub you can see the port the TV is connected to continually going down then up again.

So, there is some issue that the Hub can cope with if the two devices are connected via separate ports on the hub, but it cannot cope if the network traffic from both devices arrives on the same port.

I found it by trail an error, disconnecting individual devices and seeing what happens.  It took weeks, especially as the TV would go into a deep sleep if not used which took me down some blind alleys! i.e. I turned off my Sonos devices at the same time the TV (unknown to me) went into deep sleep … the problem went away so I thought it was Sonos but a week later the issue returned, and I had to start again.

I thought it may be a DHCP issue as I discovered the TV was giving itself an (APIPA) IP address of 169.254.246.141.  I have heard that the Sky TV boxes (I have a 2TB Sky Q and three mini boxes) run their own “hidden” network … maybe they use the 169.254.x.x range as well and the two were clashing?  Maybe the Sky Hub just does not like this range, but the issue only occurred when both the Sky Q and the TV were on, so I think it is more complicated than that.

However, I updated the TV to the newest software version, and it seemed to get a proper IP address via DHCP when wired, 192.168.0.21.  However, a day later the hub had the same Kernel errors and rebooted again! So maybe the 169.254.x.x address range was a red herring?

I think (as I have not tested for long enough) that if I give the TV a fixed IP address, or use DHCP via Wi-Fi instead of wired, then it may work OK.  I have not tested a reserved IP address on the Hub yet.

So, I have not identified the real reason but at the moment I am just keeping the TV off the network completely as it is a second TV used by the kids for a PlayStation and a Sky mini … so no real need for an internet connection.

I hope this helps someone

Regards, Johnathan