Newly compiled kernel won't boot

[azp]

I upgraded my kernel to the 4.13-version as per the ordinary steps: make olddefconfig, based on my already running kernel, and then make -j9 all && make modules_install firmware_install install && grub-mkconfig ...

To my surprise, the kernel didn't boot, it just gets stuck at "Booting 4.13.8". So I booted the old kernel, 4.12.10, and tried recompiling the new kernel again. It still didn't work. I then tried re-compiling the 4.12.10 kernel, and after installing that, surprisingly, it didn't boot anymore. So it seems that something is going wrong either with the compilation or the installation.

I'm not getting any output at all, just the kernel version and that it's about to boot, but nothing more happens. Normally I'm running with the 'quiet' flag, but even when removing that I'm not getting any debug output.

How can I debug what's going wrong? Any pointers?

GCC version is 6.4.0. I haven't changed any use flags for GCC compared to when the kernel booted successfully.
_________________
Weeks of coding can save you hours of planning.

[comprookie2000]

Did you try booting into single user mode?

I put a S instead of single on the kernel line for some reason, can't remember why.
_________________
http://dev.gentoo.org/~dabbott/

[eccerr0r]

Seems a bunch of people are complaining about EFI systems lately, including me? I'm not sure if your kernel is actually hanging or is it just not printing to the screen (and eventually completes boot?)

Curious, I vaguely recall that simply adding 'single' in the kernel command line no longer works, even for openrc which uses softlevel=sysinit or something like that to do an abbreviated boot sequence? I haven't tried in a long time but recalled at one point that specifying 'single' didn't work...
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

[azp]

I'm running with systemd on a non-UEFI system. Just a plain old BIOS.

The weird thing for me is that if I recompiled a properly booting kernel, it stopped booting successfully. I haven't tried checking for differences between them, before and after re-compile though. But I figured it must be GCC-related, or some basic package that the kernel is depending on. Like glibc?

I haven't tried single-user mode (hadn't heard of it before), perhaps I should see if it might get further.

As it is now, it's like it gets stuck unpacking the kernel or something, NOTHING happens after the grub boot line runs. I've tried waiting for hours, it never gets anywhere.

Is it possible that it has anything to do with the stack smash protector? I'm not sure if that has been enabled before or not? I'm running with only -O2 optimizations.

[mir3x]

Check manually grub.conf ?
Maybe it forgot to add init=systemdsomething
or something else.

Why u used 4.13.8 not 4.13.11 anyway ?
_________________
Sent from Windows

[azp]

Single user mode didn't help, it never gets that far. For extra testing, I tried adding it to the properly booting kernel, and there it worked as it should, i.e. I ended up in single user mode.
_________________
Weeks of coding can save you hours of planning.

[azp]

[mir3x]

Ok i got idea, add:
earlyprintk=vga
to boot params
( not sure if it should be 'vga', maybe 'keep', or'tty0')

earlyprintk=[ vga | serial ][,ttyS n [, baudrate ]][,keep]
_________________
Sent from Windows

[azp]

I've recompiled a new kernel (4.12.12) with an older working config (4.11.7), using olddefconfig, and suddenly it has started booting. I wonder if there was something wrong with a package or so before, when building the non-working kernels. I've made a diff of the config, and there are only three things changed:

[eccerr0r]

yes, most curious, also binutils needs to be added into the suspect lineup.

Were you using vanilla or gentoo-sources? Does the other work?
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

[azp]

[azp]