https://bugzilla.kernel.org/show_bug.cgi?id=212955 --- Comment #18 from Lucas Endres (jaffa225man@xxxxxxxxx) --- (In reply to Lucas Endres from comment #15) > Tonight, before I attempt anything that major, I'll build the commit just > before 51e6f07cb12e to see if it's working (although it probably already was > tested during one of the aforesaid bisect iterations). > > Hopefully, that will be enough to prove that the glitch-causing commit was > 51e6f07cb12e, or prove to me that you're right and I'll have to spend many > more days at this. Well, thanks Alan, you've been proven correct, as neither it or its prior commit worked. So I'm back to the drawing board, but have begun with my closest logged and tested commits. I've only just begun to compile the first bisect suggestion, although it hasn't started to estimate how many commits I'll need to test yet: git bisect reset Updating files: 100% (12637/12637), done. Previous HEAD position was bf05bf16c7 Linux 5.12-rc8 Switched to branch 'master' Your branch is up to date with 'origin/master'. git bisect start git bisect bad b208108638c4bd3215792415944467c36f5dfd97 # May 3rd git bisect good 698f99ed5e06946764c3be035ce9d62a2691e08c # April 29 Bisecting: a merge base must be tested [6daa755f813e6aa0bcc97e352666e072b1baac25] Merge tag 's390-5.13-1' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux # April 27 so prior to known-good for to test a merge base?... I'm building it anyway. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
