The issue seems not present when rolling back to 3.16.48-1 (this is one kernel version which was only present in jessie-proposed-update). Can someone confirm? If yes it has to be a change between 3.16.48-1 and 3.16.51-2. Regards, Salvatore