this is a classic example of what i call the steve k theory of bugivity which states that if you spot your system doing something that it shouldnt be then it is probably also NOT doing something it should be
This original story was oh- so familiar. The coincidence of an asynchronous interrupt event with the mixing/stirring of the background threads producing a "finger-in-the-fan-blades" scenario. You can get away with it for a while, but eventually the finger gets lopped off. Although this was a software bug and easily fixed once found, I've seen similar issues with hardware. Getting a chip vendor to believe you when "no one else is seeing this" is a problem.
This is another instance of the #1 old adage of troubleshooting: Fix the obvious.
Even though the printer error did not cause the failure, it was an indicator of the root cause. If this obvious error was fixed, the failure would not happen.
@GJS - wouldn't that be assuming that the IR beacon is still capable of transmitting? Though if I'm the guy in the wilderness I'd be grateful for any darn device to Tx/point/wave about - on any darn wavelength! :-)
Someone actually has to be looking in your area, so is there something special about MWIR you can share? (Compared to a standard RF rescue beacon, that is.)
Apart from a good hunt one other thing stands out. As my Grandmother used to say, "don't put all your eggs in one basket". An MWIR signalling device capable of being seen from a satellite would be fantastic for aircraft, ships and anyone going to “lonely places”. Better than EPIRB, as the bolometer on the rescue helicopters can see the beacon before the distressed craft is visible. :)
Expat is certainly correct on all points! Just because a bug is not seen to produce a catastrophic failure, it only means that the end user is not watching. Worse yet, it applies to hardware as well as software.
This is an excellent article and it drives the point home that the symptom is not the bug and that the cause needs to be thoroughly investigated and resolved. I've seen rarely occurring bugs that were simply dismissed as "unrepeatable" and the product released to an unsuspecting customer, only to have it returned (under warranty) due to some other catastrophic manifestation.
This is still a far too common occurrence.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.