I have tried to upgrade kernel from 2.6.18 to 3.1.6 in RHEL 5. I followed http://linuxgazette.net/111/krishnakumar.html link to do it. While compiling and installing i did not get any error. But while reboot i get an error displayed .
The error is
insmod: error inserting /lib/dm-region hash.ko.

From this i have tried many links to upgrade kernel, but i am unable to upgrade. I face the same error. I am doing some mistake, but i am not able to trace it. It would be helpful if some one provides a doc for upgrading kernel in CentOS or Red Hat.

Kindly provide some links to follow

Are you compiling the kernel yourself ? Or are you trying to install a compiled one?
This is an helpful info for those that want to compile their own kernel:
http://kernel.org/doc/makehelp.txt
http://swift.siphos.be/linux_sea/ch07.html#idp34363984

Regards

Yes i am configuring, compiling and installing from source. I have been using Linux for around 2 years, but i have never tried to upgrade kernel from source. Upgrading using rpm works fine, but i wish to upgrade from source. Will follow the links which u gave. Will update my output

It is a tricky thing and sometimes you have to go through all it again when your kernel doesnt work, try and error thing. Remember to keep at least one good kernel installed so you can boot your machine.
I been playing with kernels for quite while. Every time i compile i save the config file for that round, if kernel doesnt boot it is because something necessary is missing. Sometimes you will recompile your kernel 3,4,5 or more times to get it well tunned, the list of things in the config file is huge and it is easy to miss something.
What i do is to edit every section at a time making sure everything is right before go to the next section.
Take your time do not rush.
This is one interesting reading about kernel: http://kmandla.wordpress.com/2010/07...2-6-34-kernel/

Make sure to include all hardware in your machine, this will give detailed info:
That error your getting is about a driver, or it is a missing hardware or the wrong driver for some hardware.
http://lxr.free-electrons.com/source...-region-hash.c

Here another tread with similar problem:
http://www.linuxquestions.org/questi...kernel-801938/

Read as much as you can about kernel compiling in no time you will get it going.

Regards

If you encounter an error inserting a kernel module, there are pretty much just two possibilities:

1. The module isn't there.
2. The module hasn't been recompiled with the most recent kernel. (And if so, you are very fortunate that Linux detected the mismatch.)

First, go find that file. Find every single copy of it. Be sure that you know where Linux is going to look for any modules that it wishes to load, and be absolutely certain that every one of them is "fresh."

What I normally do is this:

1. Start a new page in your (paper...) service logbook and take detailed notes including date and time ...
2. Pull out your check-list of how to do this, make a copy and start checking off each step with a pencil as you do them. (The checklist goes back into the notebook.)
3. Make a backup copy of the .config file in a very safe place. This copy should not be "hidden," and it should be very clearly named and dated, and you should then use chmod 400 to explicitly write-protect it. You will never delete it. If it is "wrong," you will merely rename it and maybe set it aside, but if you ever, once attempted to do a build using it (with or without a subsequent install), you will keep it forever. (diff is a marvelous tool, indeed.)
4. make distclean Now, make sure that every object-file and module file has thereby been scrubbed clean.
5. Copy (don't "move") the .config file from your safe-place back into the right place with the right name.
6. Repeat the make process. Verify that all of the files are present and accounted for.
7. Do the kernel-install step and check it. Explicitly review the contents of the boot-loader menu file (even if you have done it hundreds of times before) and check against the content of /boot.
8. With your Knoppix DVD at ready (and having recently exercised the recovery process using it ...), reboot.

Yes, it is a laborious, pedantic, step-by-step rote process, and carefully devised to be that way.

I see that you are changing major-versions of Linux ... from 2.xx.xx to 3.xx.xx ... therefore, special care is needed. A major-release change usually implies that some "deeper" subsystems have changed within the kernel.