Still not able to reproduce this with 4.6 kernel series. It is very likely that this issue is already fixed there. Any chance this could be backported to the xenial kernel as this is an LTS release?
Still not able to reproduce this with 4.6 kernel series.
It is very likely that this issue is already fixed there.
Any chance this could be backported to the xenial kernel as this is an LTS release?