I am also interested in the Crucial SSD 5184 hour thing. Here are the options as I see them:
* related to 5124 hours = 2^64 picoseconds
Then how to account for the extra 60 hours? Maybe there is some rounding error involved with the arithmetic? Maybe initialized at -60 hours and somehow the first rollover did not trigger any bad behavior? Maybe it IS 5124 hours and the formatting is incorrect?
* NOT related to 5124 hours
Counting picoseconds is ridiculously precise for this scenario, so ignore the fact that it is close to 5124 hours. What other frequencies and limits could break at 5184 hours?
I would love know the EXACT time that the trouble begins. Is it EXACTLY 5124 hours? How many minutes, seconds, etc? But of course, I would love to know the root cause.
bostick•7mo ago
* related to 5124 hours = 2^64 picoseconds
Then how to account for the extra 60 hours? Maybe there is some rounding error involved with the arithmetic? Maybe initialized at -60 hours and somehow the first rollover did not trigger any bad behavior? Maybe it IS 5124 hours and the formatting is incorrect?
* NOT related to 5124 hours
Counting picoseconds is ridiculously precise for this scenario, so ignore the fact that it is close to 5124 hours. What other frequencies and limits could break at 5184 hours?
I would love know the EXACT time that the trouble begins. Is it EXACTLY 5124 hours? How many minutes, seconds, etc? But of course, I would love to know the root cause.
I love tracking down date / time bugs. See:
What happened on December 13, 2024? [1]
[1] https://bostick.github.io/blog/2025/04/what-happened/