Linux - KernelThis forum is for all discussion relating to the Linux kernel.
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.
Attempting to change to an SMP kernel on my Debian box to make use of both processors, I have run into an interesting issue where the SMP kernel is getting I/O and inode errors; The non-SMP kernel(s) I have installed all boot up fine, with no such errors at all in dmesg and fsck saying all is fine.
Selecting the SMP kernel generates a whole series of I/O errors as well as this one where it ends up hanging:
ext3_get_inode_loc: unable to read inode block - inode=96543, blcok=196633.
If someone could enlighten me as to how to proceed to determine why this is, and if it is likely a drive issue, a fs/ext3 issue or a kernel configuration issue I'd be mighty oblidged. Not sure how to proceed on this one to determine why the SMP kernel is generating errors the others are not.
You probably can't tell without an oops, and a *good* knowledge of the code.
That's a seriously old kernel - I'd try a SMP enabled liveCD, and see if you get the same issue. Then it might be worth reporting.
Can you get a later kernel (Sid ?) and just try that - I don't do Debian, so I don't know if it's (easily) do-able.
Really all you can do is try and isolate the failure - is it just this kernel, or if all kernels, what hardware do you have, that sort of thing.
I will try a later kernel, but it just occurred to me, I'm not in front of the box now, but I may have an Intel in one slot and an AMD in another, and I just wondered if that could be the issue, since there I am not using the K7 kernel.
I got to thinking that might be the cause of the race condition, although I understood you could mix and match processors without TOO much difficulty.
Also if anyone has any caveats for running a more recent kernel under Sarge let me know!
... but I may have an Intel in one slot and an AMD in another, and I just wondered if that could be the issue, since there I am not using the K7 kernel.
Whoa !!! I'm suprised that ever worked. I also can't imagine anyone will accept a problem report with that configuration.
From some limited exposure to Ubuntu, seems the Debian world uses the "686" nomenclature to indicate (at least) a SMP enabled kernel.
May be optimized for the 686 instruction set as well, I don't know. Check the Debian site.
If it is (probably likely), alarm bells should should be going off in your head.