The root cause of this was a typo in a patch to the real time clock driver (oops!), the fix has been integrated into the recovery firmware in v0.8.7.