1

Many times after the kernel upgrade something has stopped working or started crashing. The very last one that provoked me to submit this question is vscode.

I need to run it with --disable-gpu now. I would like to find the root cause of this (and any other similar issue) by bisecting the kernel - starting at particular version that worked and then apply one patch a time (or set of patches) to see which caused this problem.

I would appreciate some good Ubuntu-specific howto on this topic - with possible script automating the task. Thanks.

Artur Meinild
  • 26,018
Martin
  • 11
  • 1
    That's called bisecting, not dissecting. – muru Oct 10 '23 at 10:48
  • This is a very primitive, obsolete, high effort, method to addres your problems. Address and solve individual, smaller problems. Been There, Done That. – waltinator Oct 10 '23 at 16:36
  • Bisecting the kernel is reasonably straight forward, but is tedious and takes time. While you ask for "Ubuntu-specific how to" it is best too use the upstream mainline git code and to bisect it. For git bisect how to see here. For how to get and compile mainline see here – Doug Smythies Oct 11 '23 at 00:21

0 Answers0