I'm hopeful that doing the bisect over again will find a more relevant commit. While bisecting this time I ran into a weird scenario the I believe may have affected the previous attempts to do a bisect.
The short version of this is that when the computer has failed to boot a kernel (without noapic), all kernels seem to fail until I've successfully booted once with noapic. I have a feeling this has hampered many of my troubleshooting efforts. For a more detailed idea of what this looks like, this is what happened when I realized the problem: 1. I compiled, installed, and booted to 4.12.0-rc2 2. I rebooted and it worked, so I marked it as good and then powered off the computer 3. Later I powered on to resume the bisect but I wasn't paying attention at the Grub menu and accidentally booted 5.3 (without noapic), which failed 4. I then tried to boot 4.12.0-rc2 without noapic, and it wouldn't boot 5. I booted with 4.12.0-rc2 with noapic, and then rebooted and booted 4.12.0-rc2 without noapic, and once again it booted successfully -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808418 Title: Thinkpad T430u won't boot without noapic workaround To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
