Boeing 737 Max software fix fails... again

Just when you thought it was safe to fly again...

It make me think that every time you add code to close a loop-hole, you open new, smaller loopholes around the boundaries.

Clifford Heath.

Reply to
Clifford Heath
Loading thread data ...

"To us, it sounds as though code in the MCAS update either forces the processor into a locked state, such as a tight unbreakable and uninterruptable infinite loop, or triggers an exception that can't be handled and the CPU halts. It is remotely possible the code encounters a design flaw in the unidentified microprocessor that causes the circuitry to freeze."

great news though the Register has managed to remote-diagnose the problems Boeing should hire them.

Reply to

That is a far from uncommon occurrence in complex systems, especially ones which operate in different "modes".

Whether that is what happened in this case is unclear.

Reply to
Tom Gardner

Especially when you are doing it in a hurry and in the full glare of bad publicity. I feel for them if they have uncovered a latent CPU defect.

Changing any complex piece of software you can get unwanted side effects. These vary from slight timing differences to full on lock ups.

Sometimes cosmetic faults are just not worth fixing... eg. the IBM FORTRAN G1 compiler of old which would print out


With a trailing nul because someone couldn't count and the process for fixing it was too arduous and expensive for a trivial cosmetic defect.

Martin Brown
Reply to
Martin Brown

Tom Gardner wrote in news:X3_QE.74180$

It also means that the fault that caused the crashes may have been twofold.

Reply to

The proximate cause maybe.

Underlying common causes could be different.

Reply to
Tom Gardner

the real story seems to be rather different

formatting link

Reply to
Lasse Langwadt Christensen

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.