Sounds like a firmware bug, just like the original OP stated, now onto anyone else experience or having the same issue!?