/sbin/udevd stucks during boot

Message

avitase · Post by **avitase** » Sun Dec 16, 2018 4:20 pm

Hey,
I have the following problem with my laptop: when I try to boot my default kernel the boot process stops before I expect my login manager to show up and stucks with a black screen. From here on it is not possible to change to another tty, but I can still ssh into the machine. htop tells me, that /sbin/udevd is running @100% and usr/bin/sddm (my login manager) was launched already. What I don't quite understand yet is, that when booting the recovery kernel, everything works smoothly and I can even login via sddm and it seems that all kernel modules (e.g. the nvidia driver) are running properly. (what was the point of the recovery kernel again?) I don't know how to attack the problem. Can you help me out?

Maitreya · Post by **Maitreya** » Sun Dec 16, 2018 8:05 pm

If you want to debug your non recovery kernel you disable xdm on startup if that is causing the problem.

avitase · Post by **avitase** » Mon Dec 17, 2018 9:12 am

Thanks for your help. I disabled xdm and this indeed saves me from the black screen. But where to go from here? /sbin/udevd still stucks @100% CPU load...
What is the difference between my "normal" kernel and the kernel in recovery mode? Both of them are 4.14.83 kernels and I see no difference after booting, /sbin/udevd works fine for the latter though. Naively, I would have expected to see no / less kernel modules and / or only a subset of service booted, but even the nvidia driver is loaded.

Maitreya · Post by **Maitreya** » Mon Dec 17, 2018 12:46 pm

avitase wrote:Thanks for your help. I disabled xdm and this indeed saves me from the black screen. But where to go from here? /sbin/udevd still stucks @100% CPU load...
What is the difference between my "normal" kernel and the kernel in recovery mode? Both of them are 4.14.83 kernels and I see no difference after booting, /sbin/udevd works fine for the latter though. Naively, I would have expected to see no / less kernel modules and / or only a subset of service booted, but even the nvidia driver is loaded.

Any differences in building the kernel (like genkernel options)?
But you know at least now that there is something with the video driver as well.

avitase · Post by **avitase** » Mon Dec 17, 2018 12:53 pm

I cannot remember that I explicitly build this kernel in recovery mode. This always appear (automatically?) when I add my kernel to grub. I guess this is some default behavior?