Linux - KernelThis forum is for all discussion relating to the Linux kernel.
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.
Sometimes, especially when warm booting, the kernel only recognises 1 core (CPU 0).
Console messages flash up saying something like "No response from CPU 1" ... "No response from CPU 2"...
Normally 4 cores come up as expected but when it starts sulking like this it can take many reboots to correct.
Did you recompile the kernel yourself? If yes, did you set the compilation session for multiprocessors ?
When was the last time you check the disk health?
Does your system run normaly with live cds ?
More information is necessary to spot the problem, please provide as much as you can.
ukiuki:
It's a stock kernel with CONFIG_NR_CPUS=256.
Disks were fine yesterday.
Live CDs have been problematic sometimes (if kernel version is < 3.7.0 approx.). Newer ones seem OK. Most problematic ones will work with kernel param nolapic_timer.
TobiSGD:
Aha. Sounds like a good first step. I am just going outside to flash my bios and may be some time.
After 6 reboots failed to bring up all cores I added nolapic_timer to kernel params.
This worked immediately.
dmesg now lists various timer problems (eg: Could not switch to high resolution mode on CPU x) but high res. is not important to me.
The main thing is that core detection is instantaneous.
It's not a fix, more a workaround; it's clear there are a lot of issues around lapic timers, and AMD C1E it seems.
I'll mark this thread solved in a day or two after a few more boots.
What system and version are you running there?
And what about compile the kernel yourself to fix those problems,
it is clear so far that the stock kernel isn't handling it well.
And in the worse scenario have you grasp the possibility of a faulty hardware?
What system and version are you running there?
And what about compile the kernel yourself to fix those problems,
it is clear so far that the stock kernel isn't handling it well.
And in the worse scenario have you grasp the possibility of a faulty hardware?
It's Mint 15 KDE (other details as per first post).
I don't want to recompile the kernel at the moment as I have development in progress which depend on this particular kernel. I'll probably move to Mint 16 in a few months anyway.
Yes, faulty hardware is always a possibility; but, whether it boots all cores or not, it is a very stable system so I doubt that's the case here. I have seen references to problems with older kernels setting up AMD Athlon chipsets but nothing recent.
Update:
nolapic_timer was not the answer! So I have now reset the BIOS completely (shorted the reset pins on mobo) and am running with nmi_watchdog=0 as a kernel parameter. 3 boots and no failures so far!
I'm going to mark this thread as solved. After resetting the bios and setting nmi_watchdog=0 there hasn't been a single boot failure - must be about twenty boots by now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.