[SOLVED] Kernel 3.5.4 - uniprocessor system fails to boot with multi-processor option off
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Kernel 3.5.4 - uniprocessor system fails to boot with multi-processor option off
I've been carefully documenting what changes I make to my kernel since my last weird issue.
On a Pentium 3 933MHz, which I feel qualifies pretty solidly as a uniprocessor system, only boots if "Symmetric multi-processing support" is built into the kernel.
I straight up don't understand why.
My config is derived from the make i386defconfig command.
Most people do write code for multi-core systems now, you're right..but the option remains in the kernel for uniprocessor systems, which is why this confuses me. The option is there, my system is right for it, and yet it doesn't work. It could very well be there is some other part of the startup process that is looking for the multi-threaded code - even if it can only execute in one thread. I'd just like to know for sure.
I was using ext4 as my main filesystem, but I was also compiling without TLB huge pages...which I believe is a requirement of ext4, thus, none of my filesystems could mount properly.
My configs that worked with SMP on must also have had TLB huge pages on and I didn't realize it.
I've since fixed the issue, and moved to ext2 because I don't need journaling.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.