3 ms·
Looks like it's a separate issue than the one found last year, where the FAA directed 787s must be powered off before 248 days of uptime to avoid an integer ove
by tristanj 10y ago
Looks like it's a separate issue than the one found last year, where the FAA directed 787s must be powered off before 248 days of uptime to avoid an integer overflow bug.
http://arstechnica.com/information-technology/2015/05/boeing-787-dreamliners-contain-a-potentially-catastrophic-software-bug/ http://arstechnica.com/information-technology/2015/05/boeing...
- justinsaccount 10y agoyeah, I'd say if they are saying you need to reboot every 22 days, the actual limit is at least 23.. Why cut things close? 22*3600*24 = 1900800 (x1000 for milliseconds) 23*3600*24 = 1987200 24*3600*24 = 2073600 25*3600*24 = 2160000 and, as it turns out 2^31 / 1000 = 2147483 If they are storing a time value as milliseconds in an signed 32 bit int, that would roll over every ~24:20:30
- qb45 10y agoHaha, I think you nailed it. Windows 95 had exactly the same bug, except that the counter was unsigned so it was taking 48 days to crash. I only hope these machines aren't flying some modified W95 kernel :)