Live data from Hacker News

Reverse Engineer’s Perspective on the Boeing 787 ‘51 days’ Directive

ioactive.com

11–20 of 58 posts

Re: Reverse Engineer’s Perspective on the Boeing 787 ‘51 days’ Directive

#11
post #8

Fascinating analysis. I know planes get used a lot, but I'm surprised that they go for such a long time without ever being powered down.

51 days seems to be approximately how often my mac dies in kernel panic or starting to be bugged by persistent software problems that go away with a restart.

I’m at 356 days of uptime on my MacBook Pro. ¯\_(ツ)_/¯

Re: Reverse Engineer’s Perspective on the Boeing 787 ‘51 days’ Directive

#12
post #8

Fascinating analysis. I know planes get used a lot, but I'm surprised that they go for such a long time without ever being powered down.

51 days seems to be approximately how often my mac dies in kernel panic or starting to be bugged by persistent software problems that go away with a restart.

[deleted]

Re: Reverse Engineer’s Perspective on the Boeing 787 ‘51 days’ Directive

#14
post #8

Earlier quoted context omitted.

51 days seems to be approximately how often my mac dies in kernel panic or starting to be bugged by persistent software problems that go away with a restart.

I’m at 356 days of uptime on my MacBook Pro. ¯\_(ツ)_/¯

Awww ya jinxed it. And only nine days from retirement.

Re: Reverse Engineer’s Perspective on the Boeing 787 ‘51 days’ Directive

#16
post #10

For example, let’s imagine that the timestamp set by the transmitting ES is close to its wrap-around value. After performing the required calculation, the receiving ES obtains a timestamp that has already wrapped-around, so it would look like the message had been received before it was actually sent. Isn't it surprising that modulo arithmetic, as already employed successfully in TCP sequence numbers and the like, sti…

To address the second part: > and yet the plane appears to have no mechanical backup instruments[?] This is unlikely in a modern aircraft because mechanical instruments to back up e.g., the artificial horizon / attitude indicator or directional gyro (DG) / heading indicator are: 1) Mechanically complex - the attitude indicator and DG make use of gyroscopes which rotate at up to 24,000 RPM along with other mechanisms.…

I think backups for the electronic systems would not need the same level of redundancy as the primary systems (which presumably already have backups).

It's sort of like how you don't need RAID for your offsite backup disks, just some parity for bit-rot.

The mechanical instruments would be the (additional) redundancy. The additional weight/lines/service is indeed burdensome even without redundant mechanical systems.

Re: Reverse Engineer’s Perspective on the Boeing 787 ‘51 days’ Directive

#17
post #10

For example, let’s imagine that the timestamp set by the transmitting ES is close to its wrap-around value. After performing the required calculation, the receiving ES obtains a timestamp that has already wrapped-around, so it would look like the message had been received before it was actually sent. Isn't it surprising that modulo arithmetic, as already employed successfully in TCP sequence numbers and the like, sti…

To address the second part: > and yet the plane appears to have no mechanical backup instruments[?] This is unlikely in a modern aircraft because mechanical instruments to back up e.g., the artificial horizon / attitude indicator or directional gyro (DG) / heading indicator are: 1) Mechanically complex - the attitude indicator and DG make use of gyroscopes which rotate at up to 24,000 RPM along with other mechanisms.…

Plus the pilot stress of having to adjust to using dramatically different instruments when already in a difficult situation.

It's just not a workable idea in general. There are checklists for stuff like instrument failure which can probably recover from a software bug like this.

Re: Reverse Engineer’s Perspective on the Boeing 787 ‘51 days’ Directive

#18
post #8

Earlier quoted context omitted.

51 days seems to be approximately how often my mac dies in kernel panic or starting to be bugged by persistent software problems that go away with a restart.

I’m at 356 days of uptime on my MacBook Pro. ¯\_(ツ)_/¯

Sadly I'm at 2 days, 12:41 myself. I don't get many kernel panics, but this most recent reboot was in fact a panic, coincidentally. Googled the error and it came up as something that happens with M1 Mac Minis while they're sleeping. But while my machine has a M1, it is an MBP and not a Mini. And it was not sleeping. Ah well.

Re: Reverse Engineer’s Perspective on the Boeing 787 ‘51 days’ Directive

#19
post #8

Earlier quoted context omitted.

51 days seems to be approximately how often my mac dies in kernel panic or starting to be bugged by persistent software problems that go away with a restart.

I’m at 356 days of uptime on my MacBook Pro. ¯\_(ツ)_/¯

So you never install security updates? Because all Apple updates require a reboot due to their SIP "update the frozen image offline" nonsense.
Post reply on HN