This is reproducable with the latest upstream kernel as well (4.10), so this isn't a bug in the ubuntu kernel; it will require an upstream fix and backport that into xenial/yakkety.
This is reproducable with the latest upstream kernel as well (4.10), so this isn't a bug in the ubuntu kernel; it will require an upstream fix and backport that into xenial/yakkety.