Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
There's no specific kernel forum, so I'm not sure if this is the right place to post this. Please let me know if it should be elsewhere. Hopefully there is someone who can point me in the right direction with this issue.
I have been running kernel 184.108.40.206 for some time now, patched with Ingo Molnar's Real-Time Preemption patch rt-13.
The machine is an Opteron-185 CPU running Xubuntu 9.04. The machine is a dedicated folding at home rig, running the current SMP client.
This week I decided it was long enough on teh old kernel and built a new one on 220.127.116.11, patched in the same way with the rt-23 kernel patch. I imported the same .config that was used in the prior version. On my first build, everything seemed to be OK until I started the folding client. Only one core engaged. I ran menuconfig again, checking to make sure that all SMP options were selected. AFAICT, all were ok. In the next two days I tried selecting several different options that I thought could be causing the problem, and built three more kernel attempts, each failing to run the SMP client with more than one core.
I tried another build using the 18.104.22.168 kernel, and DID NOT patch it with the RT patch. This build ran the client fine. So the problem lies with the RT kernel patch configuration, but where?
For brevity, the process was like this:
-start machine, loading kernel 22.214.171.124-rt13 patched: WU runs OK [running this way for months now]
-build new 126.96.36.199 vanilla [no patch];install new kernel
-reboot and load kernel 188.8.131.52 vanilla: WU runs OK
-patch 184.108.40.206 with rt23 and build; install new kernel
-reboot into kernel 220.127.116.11-rt23 patched; WU runs one core only.
It seems that I have failed to check some obscure option (perhaps a new one) in the new kernel build, breaking SMP somehow. Is there anyone out there with some idea where I can check for this option, perhaps with knowledge of the RT kernel?
To continue this saga, I have now experimented with both 2.6.30 and 2.6.31 with the same results. All vanilla kernel builds work fine; but every kernel version since 18.104.22.168, when patched with the RT patch, fail to run both cores using the very same .config file to build them.
I do not know how or where to report this, and it may be some sort of bug, not with the kernel itself, but with the Real Time kernel development. Can anyone point me in the right direction?