Comment 11 for bug 1715368

Joseph Salisbury (jsalisbury) wrote :

We don't generally pull in a new version of a driver to fix a bug. There is a document that describes the SRU process[0].

For this bug, what we would want to do is find the specific commit in the newer driver that fixes the bug, then SRU it to the 16.04.03 kernel.

To identify the commit that fixes this, we would need to perform a "Reverse" kernel bisect[1], which is why I asked for the testing of various kernel versions in comment #6.

It looks like you tested those kernels per comment #9. Is it correct that the 4.5 kernel with version: 1.0.0 does not have the bug? If that is the case, we can bisect between 4.4 and 4.5.