Posted on 04/02/2020 9:41:53 AM PDT by dayglored
Are they using ANY Gate$ software?
The I.T. Crowd - great comedy!!
“Have you tried turning it off and on again??!?!?”
https://www.youtube.com/watch?v=nn2FB1P_Mn8
0118 999 881 99 9119 725....3.
Boeing will soon field a team of lesbian-Muslim-multiple abortion-African American studies majors from India to rewrite the codebase with JavaScript and nodeJS ...
Well that’s computers for ya.
Just to be safe, do it every 50 days.
“No kidding. I have datacenter network gear that stays up without a reboot for years. The only time it gets restarted is after applying a required security patch.
You wait years to put in security patches?
It’s McDonnell Douglas’ fault. They introduced beancounters and effed up Boeing’s focus on quality engineering. Beware mergers.
I worked on this exact system so I can shed a little light. the Arinc 664 protocol was developed 10+ years ago to be ‘deterministic ethernet’. The short short version is that with ‘normal’ ethernet you can’t 100% guarantee that data will not be ‘old’ when it gets where it is going. So fancy ethernet favor was cooked up that, when used right, allows you to be 100% sure that when you get your air speed data over the network it will not be ‘stale’. What this article is saying is the system was not designed or tested to be powered up that long. I can say from experience ( worked on that project) that we did not have a requirement to be powered up continuously for more than 51 days. There are actually a lot of systems on other aircraft that expect periodically power cycled. So it is an embarrassing glitch when exposed in a hit piece article but it is pretty understandable why the ‘bug’ occurs. I am not familiar with the details of the specific ‘bug’ and I have not worked for that company for many years.
It sounds like a moronic windows thing. Thank you, Gates.
sounds similar to the Y2K problem except it happens after every 51 days … i.e., counter overflows and similar extremely bad coding …Yes, that was my first thought as well. 51 days sounds about like the time span when a 32-bit millisec tick counter overflows. Looks like many idiot programmers still have problems handling overflow and modulo arithmetic correctly. Maybe that is what happens if they spend more and more time learning gender studies instead of math in college…
Haha...that was great :)
Great show - wish it were still going...
Well, without throwing any stones at you or your team personally, I gotta say as a computer systems engineer since (oh, god...) 1980 or so, any system that relies on power cycling to clear stale state information is poorly designed and/or poorly implemented. Whether it's memory leaks, system table size crashes, disk space filling up, or whatever, those conditions are symptoms of a problem that should be addressed by fixing the design, the implementation, or both.
In my opinion, any computer worthy of the "reliable" descriptor should be capable of running continuously forever, modulo patches to correct stability or security flaws that require a reboot.
Again, nothing personal. But assuming what you're saying is true, I find it disturbing.
No, but in general, better gear only gets patches released at very long intervals, because they did a good job prior to shipment, and most of the found problems got patched early on.
IMO, any critical system that still requires frequent system patches after a few years wasn't ready for prime time when it was released. After a couple years of operation, patches should only reflect things like changes in protocols (like dropping TLS 1.0/1.1 and requiring TLS 1.2), or patching for a vuln in a supported application.
Somebody at Boeing neglected to include a trash collection routine in the software. Or the H-1B programmers interpreted the requirement with something to do with trash cans in the lavatories.
I told them they shouldn’t use XP.
I saw mention of this bug quite some time ago. It has been known for a while now. Crappy software.
Windows?
Future Edit: Do not perform this procedure during flight.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.