It appears that the problem got fixed in the next kernel version (4.9.0-6-amd64) so this bug can be closed.
--jtg