21–30 of 54 posts
Earlier quoted context omitted.
66 days + 12 hours are 5,745,600,000,000,000 ns. The log2 of this is 52.351... Javascript and some other languages only have integer precision up to 52 bits then they switch to floating point. Curious.
It's 32 bits of milliseconds, right? Hm, no, that would overflow much sooner (49.7 days).
1: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/971...
ouch
a pet peeve of mine, (along with people brigading on issues/threads e.g. posting them to unrelated news sites... op....) is woefully incorrect language. > at day 66 all our jobs started randomly failing if there's a definable pattern, you can call it unpredictabily, but you can't call it randomly.
Timestamps should NOT be compared like this. Exactly this is why time_before() or time_after() exist. https://elixir.bootlin.com/linux/v6.15.7/source/include/linu...
Earlier quoted context omitted.
Isn't 32bit counter 49 days? Assuming that one was counting milliseconds, at least. Only remember that because that's the limit for Windows 95…
100ns intervals. My favorite part of that story is how long after Windows 95 was released before anybody discovered the bug.
This is only very tangentially related, but I got flashbacks to a time where we had dozens of edge/IoT raspberry pi devices with completely unupgradeable kernels with a bug that would make the whole USB stack shut down after "roughly a week" (7-9 days) of uptime. Once it got shut down, the only way to fix it was to do a full restart, and, at the time, we couldn't really be restarting those devices (not even at night)…
This is only very tangentially related, but I got flashbacks to a time where we had dozens of edge/IoT raspberry pi devices with completely unupgradeable kernels with a bug that would make the whole USB stack shut down after "roughly a week" (7-9 days) of uptime. Once it got shut down, the only way to fix it was to do a full restart, and, at the time, we couldn't really be restarting those devices (not even at night)…
Wow, someone in the github comments[1] noticed that one of the bug numbers assigned internally for the issue matches to the day the number of days the driver would stay up. 1: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/971...
