News for hackers. Stuff that matters.
Re:Airbus A320 Fly by wire corrupted by radiation in flight by t0mas88 on Friday November 28, 2025 @04:45PM (#46083043)
I've read the EASA emergency airworthiness directive, it's only a software change.
Re:Airbus A320 Fly by wire corrupted by radiation in flight by lysace on Friday November 28, 2025 @04:48PM (#46083065)
A software change that remedies solar radiation issues? Cool.
Re:Airbus A320 Fly by wire corrupted by radiation in flight by butvacuum on Friday November 28, 2025 @05:14PM (#46083250)
Easy enough to imagine. Something improperly was judged to not need concencus, running the calculation twice, or some other software mitigation. Revise process to include mitigation.
Re:Airbus A320 Fly by wire corrupted by radiation in flight by lysace on Friday November 28, 2025 @06:08PM (#46083611)
"just run the calculation twice. surely the darned solar radiation will take care not to hit random parts of the memory or any critical registers in the cpu"
Re:Airbus A320 Fly by wire corrupted by radiation in flight by anonymars on Friday November 28, 2025 @06:16PM (#46083667)
What experience do you have with firmware that you're basing all this on?
Re:Airbus A320 Fly by wire corrupted by radiation in flight by lysace on Friday November 28, 2025 @06:18PM (#46083674)
It's okay to not be nationalistic all of the time. Airbus will survive this extreme edge case. None of these comments matter in the bigger picture.
Re:Airbus A320 Fly by wire corrupted by radiation in flight by jaennaet on Friday November 28, 2025 @06:41PM (#46083852)
Based on your ad hominem of a reply I suppose it's safe to assume you don't have the experience, then
Re:Airbus A320 Fly by wire corrupted by radiation in flight by mirekrusin on Friday November 28, 2025 @05:13PM (#46083244)
Instead of 3 copies make 7 for majority vote?
Re:Airbus A320 Fly by wire corrupted by radiation in flight by butvacuum on Saturday November 29, 2025 @03:17PM (#46090398)
Best explanation I've seen (and claims to be from a published but not public report on it), is that their 3 way consensus didn't smooth over repeated wildly wrong outputs correctly. Concestency problem strikes again.