It is a firmware bug, exist in firmware 4.1 too.
I will forward to firmware team, thank you!