Comment 8 for bug 1592597

Testing the latest upstream kernel will tell us if this bug is already fixed in mainline. If it is fixed, we can then work to identify the commit that fixes the bug.

An alternative would be to perform a kernel bisect, which will identify the commit that introduced the regression. However, that will require testing about 7 - 10 test kernels.

Is it not possible to test any test kernels on the affected system?