4.4.0-64-generic does have this issue. So it would seem whatever the problem is was introduced with 4.4.0-66.generic
4.4.0-64-generic does have this issue. So it would seem whatever the problem is was introduced with 4.4.0-66.generic