Comment 4 for bug 1658016

Just tried the mainstream kernel "4.10.0-041000rc5-lowlatency" as mentioned above and I do confirm the very same problem exists there too.

Just to give a hint - this regression was introduced approximately in the first two weeks of 2017, so it shouldn't be that difficult to trace back the change, which could then point to the actual root cause.