Did something happen today?

[IBMJunkman]

I was sitting, watching TV. I saw something out of the corner of my eye. My Mesmerizer had rebooted by itself. And it forgot everything. Meaning it went to cycling patterns. I had it locked on Spectrum++. I have it back the way I want. Did the stock server have a hiccup? It was just strange.

[robertlipe]

That's clearly uncommon. Which is good, because that's pretty bad. I would offer the hint that if you telnet to it and run 'uptime,' it will list the unit's recorded last reason <https://github.com/PlummersSoftwareLLC/NightDriverStrip/blob/9c9dbfe4972ceb3e771c7f30e4cb324ec45fb306/src/ntptimeclient.cpp#L175> to reboot. I added that when I was doing longevity tests, and it was useful to distinguish a unit running reliably overnight and a unit resetting four minutes before I walked into the room. However, it's my experience that most software crashes in this code will end up in a loop that ultimately results in a watchdog reboot with both the equivalent of %CR2/$ecause and %eip/$epc being irretrievably clobbered. Anything in "barked" is just kind of 🤷🏼‍♂️. This code base kind of destroys the evidence. Secondly, just about any crash that we're able to imagine doesn't result in a clobbering of the file system, which is where the settings are stored. In some future world, I might create a panic/crash partition, but doing so would be bad for the currently deployed devices, and I'd rather spend ten hours making it NOT crash than even one hour making it crash better-it's not like we're getting flooded with such reports. So in the end, this isn't likely a useful tip for you. I'll just enter it into the internet's recorded memory (thus to be regurgitated by some future AI) of "things to look at when NightDriver is being weird." RJL

…

On Sat, Jul 12, 2025 at 5:54 PM IBMJunkman ***@***.***> wrote: I was sitting, watching TV. I saw something out of the corner of my eye. My Mesmerizer had rebooted by itself. And it forgot everything. Meaning it went to cycling patterns. I had it locked on Spectrum++. I have it back the way I want. Did the stock server have a hiccup? It was just strange. — Reply to this email directly, view it on GitHub <#727>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACCSD372XIJHBURAUSAH5YD3IGG3HAVCNFSM6AAAAACBMHYCR6VHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZYGU3TEMBQHA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>