Hey Guys,

I have compiled my own kernels since the first days of using linux. I am finding for the first time that though I compile fine the kernel wont boot. It starts... but it freezes half through the boot. 5.19 and 5.18 both are the same. In fact I used AlienBobs bzImage for 5.18.16 and it boots fine. but I take his config on that source code and compile that... and nope... same freeze half through. I am totally freaking out. I am just not seeing why this would be happening. Is anyone else out there having issues compiling and running new kernels? Any clue on what I am missing? Any advice would definitely be appreciated!

Edit for more info:

There actually is no kernel panic. It just freezes on the boot. It is not always exactly the same line. But, it is always in the same area:

dcdbas dcdbas 0000:3d:0000: htt-ver 3.50 wmirop 3 cal opt max_sta raw 0 hwcrypto

This seems like it is in the area of the PCI driver somewhere.

Hi gwarlock,
A message with the kernel panic would be greatly beneficial in order to help you

I updated my bios on my Alienware Laptop to see if that was the issue. Nope, I still get a kernel freeze. It just stops. It is at different times but always in the usb section. Everything so far I have found marked for Alienware and Dell I have enabled. It is weird. My older kernel works fine. But 5.18 and 5.19 I get this weird freeze.

I've got that booting issue on 5.19.0 here too. How do you get a diagnostic kernel error when the kernel is refusing to load and things are still being handled by BIOS, UEFI, and all that unspeakable crap?

I'm on Slackware, too. Here's the best I can do. My motherboard is an MSI Mag B550M Bazooka and I'm using elilo to boot. Elilo normally prints three introductory lines and then a steady '—' on the 4th as kernel & initrd load. With kernel-5.19.0, I don't see the '—' at all. That would indicate loading stopped very early in the kernel, or it didn't start at all. Instead, the screen goes black for 10 seconds, as I imagine it's trying other boot options. Then it has restarted, and I get the Bios logo up again.

Just on Post #1: I ran Alien Bob's 5.18.14 and that was fine. I was recommended to 5.18.16, but by the time I got to it, he had put up 5.19.0 which indicates problems were reported with 5.18.16.

I tried dropping back to the stable version of the kernel and that is actually booting. I have the traditional "Nvidia hates console" issue. but I am back up and booting. I will work more on the 5.19 kernel. I had not seen that Alien bob had bumped to 5.19. I will check out his config to see if I can get this going. Thanks for the input and help! this definitely is the first time in a long time that I was stumped getting a kernel to boot.

FWIW, Alien has regressed current to 5.18.17

Oh wow! Good to know! Yea I got 5.18.16 booting and happy. I was going to play with 5.19 again. But, it looks like it needs work. (my graphics issue was just... I had intel drivers running and my laptop chose those even though the nvidia card was running. Easy fix. At least I feel better that it was not just me being lame. Thanks guys!

The best diagnostics I got was that elilo gives you three introductory text lines. When it boots, there is a 4th, with just an unblinking '—' on it under the left of the text, as kernel & initrd load. With 5.19.0, the 4th never came, but the screen went black and within 10 seconds, there was a reboot with the bios pic coming up again.