Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Hello, I am using kernel 2.6.28-ARCH and I recompiled from the ABS repositories using directions in the wiki and a few posts found on the forums there. I added CONFIG_XEN=y because it is on an XEN vps and it would not boot at all before it would just give an elf error. Now it gets passed that and i get a screen full of ...well i cant read it so if someoen could tell me what i did wrong please that would be cool Not sure what i should even google out of this.
BUG: scheduling while atomic: kthreadd/2/0x00000002
Scheduling while atomic tends to lead to race conditions or bad locks -- this also appears to be a fairly recent thing in the kernel (people only started reporting this in the last few versions). 2.6.24 is the earliest I've seen it -- can you jump back a few versions & try again?
I'm not a skilled kernel hacker, but someone mentioned they suspected it was in the slub allocator -- are you using slub or slab?