To find the issue a git-bisect is needed. This means you have to know which kernel version was fine for your and which version might be the first not working for you.
- current v4.8.x release is fine for you and has no issues
- you might assume it was introduced with v4.9-rc1 or earlier
Then you have to compile v4.9-rc1 once again to check if that version already has the issue. If yes, then we have the last good version and one bad version. git-bisect can then find the first bad version, which might be the introduction of the issue for your hardware.
What does this mean:
- you need some time to find the issue (depending on your hardware)
- you need to put some effort into it
- you might learn some new stuff
To have a small impression on what I’m talking you can take a look at this and the result. And yes, it takes some time.
We have great connections to the Linux foundation and with Greg Kroah Hartmann. If additional help is needed on the matter, don’t hesitate to write me an email.