I had a similar problem. Upgrading to 2.0.0.1 fiirmware looks like fixed it