Possibly due to NetBSD Variable Change?
This sounds oddly similar to other software issues I've encountered... NetBSD v5.0 changed the variable "hardclock_ticks" from an unsigned 64-bit integer to a signed 32-bit integer. The counter increments by 1 for every 10ms that pass, and when it reaches a value of 2147483647 (~248.55 days) the next increment sets the "negative" bit in the signed integer. If code doesn't properly handle the possibility of a negative value, then you get a software crash... which I'm sure would be just wonderful for an airliner.
Biting the hand that feeds IT
