![](https://seccdn.libravatar.org/avatar/ed90d0132a4f59f2d3a1cf82a1b70915.jpg?s=120&d=mm&r=g)
Hello René, On 07.03.2016 13:48, René Krell wrote:
2016-03-07 12:03 GMT+01:00 Oliver Neukum <oneukum@suse.com>:
Can you bisect the kernel?
Unfortunately, I have no idea how to do this. Any documentation on bisect, for OpenSUSE with regards of patches?
I usually go this way for kernel bugs: * install kernel-vanilla * verify the bug is still there -> if not, blame openSUSE patches; exit 0 * now clone linux kernel git tree * build suse-kernel-vanilla config, boot, verify bug is still there * reset to kernel version $CURRENT-1, build, verify bug is gone * start bisecting as can be found in git bisect tutorials on the web. Note that this will take a long time, since you are always building an "all inclusive" kernel config. I usually trim the config down to what is needed on my machine and use ccache to speed up things a little bit, but I somewhat know what I'm doing there and I'm fully aware that I might not find the same bug the SUSE kernel is exhibiting by changing the configuration. Executive summary: I'm usually searching the bug in the upstream kernel, not in the suse kernel. Good luck. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org