On Thu, Feb 14, 2019 at 09:16:23PM +0000, Michael Buch wrote: > Thanks for changing, on second thought though, I have my doubts about this > situation being possible. The cp times are millisecond increments since > boot and would only not increment from our perspective if we sampled at > submillisecond frequency. You can maximally > configure slstatus to 1ms so I dont think we need a check here > Did this happen to you?
Yes, as I wrote in my initial explanatory mail (https://lists.suckless.org/hackers/1902/16697.html) this happens regularly (but not always) after a suspend and resume cycle on OpenBSD. This causes slstatus to crash.
