3 ms·
Previous: https://news.ycombinator.com/item?id=22761395 https://news.ycombinator.com/item?id=22761395 https://news.ycombinator.com/item?id=33233827 https://news
by Dylan16807 2y ago
Previous: https://news.ycombinator.com/item?id=22761395 https://news.ycombinator.com/item?id=22761395 https://news.ycombinator.com/item?id=33233827 https://news.ycombinator.com/item?id=33233827
More interesting, a root cause analysis: https://news.ycombinator.com/item?id=33239443 https://news.ycombinator.com/item?id=33239443 https://ioactive.com/reverse-engineers-perspective-on-the-boeing-787-51-days-airworthiness-directive/ https://ioactive.com/reverse-engineers-perspective-on-the-bo...
The 47 bit timestamp at 32MHz would explain the duration (Though not why it isn't 33MHz?).
- dang 2y agoThanks! Macroexpanded: Reverse Engineer’s Perspective on the Boeing 787 ‘51 days’ Directive - https://news.ycombinator.com/item?id=33239443 https://news.ycombinator.com/item?id=33239443 - Oct 2022 (55 comments) Boeing 787s must be rebooted every 51 days to prevent 'misleading data' (2020) - https://news.ycombinator.com/item?id=33233827 https://news.ycombinator.com/item?id=33233827 - Oct 2022 (140 comments) Boeing 787s must be turned off and on every 51 days (2020) - https://news.ycombinator.com/item?id=27117320 https://news.ycombinator.com/item?id=27117320 - May 2021 (42 comments) Boeing 787s must be turned off and on every 51 days - https://news.ycombinator.com/item?id=27111650 https://news.ycombinator.com/item?id=27111650 - May 2021 (4 comments) Boeing 787s must be turned off and on every 51 days to prevent 'misleading data' - https://news.ycombinator.com/item?id=22761395 https://news.ycombinator.com/item?id=22761395 - April 2020 (152 comments)
- gfv 2y agoI have a way simpler explanation. IEEE 754 double can only represent integers up to 2^53 without precision loss, so if you naively average two numbers greater than 2^52, you get an erroneous result. It just so happens that 2^52 nanoseconds is a little bit over 52 days. I've seen the same thing with AMD CPUs where they hang after ~1042 days which is 2^53 10-nanosecond intervals.
- withinboredom 2y agoThis is incorrect. Very incorrect and disastrously so. Drop 0.3 in here: https://www.h-schmidt.net/FloatConverter/IEEE754.html https://www.h-schmidt.net/FloatConverter/IEEE754.html You can also drop 524535643, an integer clearly less than 2^53 and is off by 5. This is even seen here: #include <stdio.h> int main() { float b = 524535643.0f; printf("%f", b); return 0; } output: 524535648.000000
- gfv 2y agoI was talking specifically about double-precision floats. Single-precision floats can represent every integer up to +-2^24.
- withinboredom 2y agoAh, missed that detail.
- DiggyJohnson 2y agoHow could their comment possibly be "incorrect and disastrously so" unless the FAA is citing this thread for their investigation?
- withinboredom 2y agoThe comment said IEEE754 doubles can represent integers to 2^52. But I missed the double or assumed float. Floats cannot do that and it would be disastrous to assume so. For that matter, doubles also have some pretty big issues when you do operations on them (loss of precision), but as long as you are purely doing integer operations, it “should” be fine. A practical example with non-integers: 35 + -34.99
- h_tbob 2y agoPlease email Boeing! Seriously they should have posted here for some help!
- ShroudedNight 2y agoHaving done exactly this math for GStreamer bindings in JavaScript (where the built in numeric types are double or nothing), this would also be my prime suspect.