4 ms·
A few years ago, at my company, we would get random TPM crashes every few months on all our machines. You'd be working and the TPM would just disappear and the
by wvenable 9mo ago
A few years ago, at my company, we would get random TPM crashes every few months on all our machines. You'd be working and the TPM would just disappear and then any apps that rely on it for key retrieval would error out. Even worse, since the TPM chip is always running, neither a reboot nor a shutdown would fix it -- you literally had to pull the plug.
This went on for months. Then one day we had a power outage. Two months later, every single machine failed at the same time. I checked the logs and it was 49 days and few hours since that outage. It didn't take me too long to figure out what the underlying programming error inside the TPM was. At least we could then describe exactly what the problem was to our PC vendor.
- spuz 9mo agoSo what was the programming error in the TPM?
- jcurtis 9mo ago49 days is a bit under 2^32 milliseconds... So unsigned int overflow?
- swinglock 9mo agoSomething breaking after 49.7 days is a classic. Someone counted milliseconds since start with a 32 bit unsigned int and some code assumed it couldn't wrap.
- deleted 9mo ago[deleted]
- blell 9mo agohttps://news.ycombinator.com/item?id=28340101 https://news.ycombinator.com/item?id=28340101
- deleted 9mo ago[deleted]