I can confirm that the bug is gone with "linux-image-4.9.0-5-amd64", tested with a system which was affected before. -asc