Comment 8 for bug 1713751

The problem no longer seems to be occurring anymore even with the 4.10.0-33-generic kernel. Since 2017-09-11 all of the affected machines have been getting automatic package updates and I'm guessing some non-kernel package has changed something that prevents the problem.

I would like to know what fixed it and I could start reverting those package updates or start over with an old install, but for now as long as it is fixed it might not be worth investigating further.