[SOLVED] Trying to build smp kernel - but hitting brick wall
by 3rensho from LinuxQuestions.org on (#5PDTV)
I have been building generic kernels for a while and that is working fine. Decided to try the smp kernel since I have an 8 core processor and wanted to give it a go. Here's what I have done to try to accomplish that.
1) In a directory copied over the kernel-source.SlackBuild, kernel source .xz file, within this directory created the directory "kernel-configs" and copied the smp config file in there. Run the slackbuild and it produces kernel-source-5.14.2_skernel-modules.SlackBuildmp-noarch-1.txz in the /tmp directory. Install that and it deposits a linux-5.14.2 directory in /usr/src. Check the .config file therein and it is identical to the smp config file.
2) Run kernel-generic.SlackBuild in /usr/src and it produces kernel-generic-smp-5.14.2_smp-i686-1.txz in /tmp. Installing that puts a vmlinuz-generic-smp -> vmlinuz-generic-smp-5.14.2.smp in /boot along with link to System.map, etc..
3) Run kernel-headers.SlackBuild in /usr/src and that creates kernel-headers-5.14.2_smp-x86-1.txz in /tmp which I install.
4) Run kernel-modules.SlackBuild in /usr/src and it creates kernel-modules-smp-5.14.2_smp-i686-1.txz which is installed.
Go to /boot and run "mkinitrd -c -R -k vmlinuz-generic-smp-5.14.2-smp -m ext4" and the initrd files are created.
Run grub-mkconfig and the new kernel is picked up properly.
Reboot and end up with a kernel panic -
"modprobe binfmt-464c cannot be processed, kmod busy with 50 threads for more than 5 seconds."
"Kernel panic - not syncing: no working init found"
I've tried this several times with the same result. At this point I can't see what I'm doing wrong as all of the Slackbuilds run fine and everything looks great until I boot. Can someone who runs the smp kernel please have a look at what I have done and see where I messed up. Much appreciated.
1) In a directory copied over the kernel-source.SlackBuild, kernel source .xz file, within this directory created the directory "kernel-configs" and copied the smp config file in there. Run the slackbuild and it produces kernel-source-5.14.2_skernel-modules.SlackBuildmp-noarch-1.txz in the /tmp directory. Install that and it deposits a linux-5.14.2 directory in /usr/src. Check the .config file therein and it is identical to the smp config file.
2) Run kernel-generic.SlackBuild in /usr/src and it produces kernel-generic-smp-5.14.2_smp-i686-1.txz in /tmp. Installing that puts a vmlinuz-generic-smp -> vmlinuz-generic-smp-5.14.2.smp in /boot along with link to System.map, etc..
3) Run kernel-headers.SlackBuild in /usr/src and that creates kernel-headers-5.14.2_smp-x86-1.txz in /tmp which I install.
4) Run kernel-modules.SlackBuild in /usr/src and it creates kernel-modules-smp-5.14.2_smp-i686-1.txz which is installed.
Go to /boot and run "mkinitrd -c -R -k vmlinuz-generic-smp-5.14.2-smp -m ext4" and the initrd files are created.
Run grub-mkconfig and the new kernel is picked up properly.
Reboot and end up with a kernel panic -
"modprobe binfmt-464c cannot be processed, kmod busy with 50 threads for more than 5 seconds."
"Kernel panic - not syncing: no working init found"
I've tried this several times with the same result. At this point I can't see what I'm doing wrong as all of the Slackbuilds run fine and everything looks great until I boot. Can someone who runs the smp kernel please have a look at what I have done and see where I messed up. Much appreciated.