I started the git bisect. It's over 10,000 commit difference and will take about 14 steps.
I'm documenting the process here. https://hackmd.io/UINQqeaTTOSRNv1yhFjVqw
I got about 5 steps in. But the last 3 kernel builds are erroring out. I mean they boot and daemons start, but before I get to a prompt, I get dropped into an emergency shell. The only apparent failure is something related to decompression. I strongly suspect the .config has something weird in it.
Anyone know how to build a simple and sane .config for each version of the kernel. As I'm bisecting, I some times go forward in time and backward in time. So I want it to have configuration options that make sense for the current version.
Also, I set bad to 6.6.15 and good to 6.7.12. But oddly, after setting a step as "skip", git bisect brought me to a 6.5.0 kernel! Specifically it was v6.5.0-rc7-01777-ge1133ac81176. The commit hash is e1133ac81176.
So something weird is going on, and I may reset. Also I'm going
to get myself an nvme ssd to hopefully speed up the build. Builds
are taking me 40 minutes.
ccache is not helping me speed up the build. Too many misses. I
used /dev/shm and that was fast, like 2 times faster. But in one
test, the guest VM crashed and I had to reboot the host. So I
lost that copy of the kernel. Has anyone used eatmydata. I mean
it would be nice to avoid syncing to my slow disk for every write.
Brian
-- Brian DeRocher