Oxide has published my doc on power supply glitch mitigation on our servers, which required some reverse engineering of a vendor fix (that wasn't quite right).

https://rfd.shared.oxide.computer/rfd/630

To me, the most interesting part was this: because of where in our stack the mitigation gets applied, we decided _not_ to persist it in flash/eeprom on the IBC, because this implies a power cycle. We don't power cycle fully. So, we defined a way to test for its presence and re-apply it if required at each update (or power-on).

This implies that the customer gets the mitigation immediately upon updating our firmware, and that we can adjust the mitigation in any future update if we learn more.