Quote:
Originally Posted by Ignitionnet
How do you propose software pushes hardware too hard during a reboot? If a router can't handle hitting 100% utilisation for a while without having a hardware failure that's a manufacturing issue.
|
Most devices don't spin up to 100% at reboot, they tend to stay quite underclocked until they're finished initialising, then they ramp up. For all we know, there's a bug causing a clock to get set too high so not 100% but maybe 110%. Pure, utter speculation though
Quote:
Originally Posted by Ignitionnet
Damage during reboot is more likely due to the voltage spike and trough when power is applied. There can be latency before regulators kick in.
There are a very few cases where software can harm hardware, however these usually need the software to go out of its way to damage the hardware or the hardware to have some quite provocative switches available to control it.
The examples that come to mind for me are Stuxnet, though that worked on PLCs operating industrial processes so quite different from a cable modem router, and software that could kill Android devices by messing around with voltage regulation.
I wouldn't have thought the router firmware would have any control at all over low level functions capable of harming hardware, that'd be looked after by whatever is in the motherboard, individual cards, and SoC's ROM/PLA?
If the required buttons and switches are exposed to the router firmware that would be an 'interesting' decision.
|
The point I'm ultimately getting at is that I don't think you can rule out software just because of the way the SHUB2AC's are dying. They do all seem to be dying suddenly from the various reports which is a little too consistent for my liking.