On Sat, 9 Jun 2018 22:46:58 +0300 Wirz <spam@xxxxxxxxxxxxx> wrote: > > Is is possible for you to create a git bisect to find the change that > > actually broke this? > > That would be really helpful. > > I can try that. What is the most efficient way to unload/recompile/load > a single module without rebooting the machine too often? And it'll be a > lot of hard resets ... A git bisect is really only possible in the full kernel tree. But it won't take a lot of steps to get a result, because you already narrowed it down to 4.14-4.15. It might take 10 iterations or so (git will tell you). Due to incremental builds that can be done pretty quickly. As the whole kernel is searched for a change, a reboot is usually needed after each iteration step. There are a couple of howtos on the web regarding git bisect: https://duckduckgo.com/?q=git+bisect+kernel -- Michael
Attachment:
pgpe3064qJJWu.pgp
Description: OpenPGP digital signature
