A possible bug in firmware 2.0