Created attachment 295271 [details] Good dmesg I started testing kernel 5.11 around rc5 and it has never booted. However the logs always seemed to be truncated, and I couldn't ssh into my system until today. However I compiled the latest git today andd ssh in and get useful information. Everything works great with 5.10.16, so I've attached dmesg_5.10.16_good.txt, Xorg.0.log_5.10.16_good.txt, and journalctl_5.10.16_good.txt to show what happens during a successful boot. And attached dmesg_5.11-git_fail.txt, Xorg.0.log_5.11-git_fail.txt, and journalctl_5.11-git_fail.txt to show what happens during the failed boot with 5.11 git. By the way, the journalctl log was produced with journalctl -b -k.
Created attachment 295273 [details] Good Xorg
Created attachment 295275 [details] Good journalctl
Created attachment 295277 [details] Bad dmesg
Created attachment 295279 [details] Bad Xorg
Created attachment 295281 [details] Bad journalctl
I forgot to include the full git kernel name. It's linux-git-5.11rc7.r141.g358feceebbf6
Can you bisect?
(In reply to Alex Deucher from comment #7) > Can you bisect? I can bisect, but I updated and compiled linux-mainline with the final 5.11 from the Arch AUR this morning and my system boots just fine. I did a couple of quick tests playing videos, running VMs, etc. and everything looks good. So you can close this bug. I've done some system updates since yesterday so later today I'm going to compile the same linux-git again, and if it fails compile the current linux-git. If that fails then I'm going to compare the linux-git and linux-mainline PKGBUILD files to see if the the error was caused by the linux-git build. I've used linux-git many times over the years and never had a problem with it but who knows. It's definitely worth checking out though. Thank you for your help and attention, and thanks to all the kernel devs for their awesome work. It is greatly appreciated.
Only reporters can close kernel bugs. Please close if this is not an issue.
(In reply to Alex Deucher from comment #9) > Only reporters can close kernel bugs. Please close if this is not an issue. I've closed it as invalid since I'm not sure what the issue was and there was no specific code fix I'm aware of.