On Tue, Jul 19, 2011 at 10:48 PM, David Cramblett wrote: > Thanks for the response. I did figured out the issue a few days ago. > This was a CentOS 5.6 system, and 2.6.18 was the newest kernel I could > get for that distribution. I'm not a kernel expert, but keep in mind that RHEL 2.6.18-238.12.1.el5 kernel is very different from the upstream 2.6.18. They make their systems ABI compatible throughout the lifetime of the major version(4.x, 5.x). So every major version of RHEL (es 5.x, 6.x) fixes the base kernel in rpm name and then increments only the "-" part after it. New features are typically not backported to current versions of the kernel, newer drivers are often back ported (with their bugs too ;-), assuming the driver existed in the RHEL kernel. For example RH EL 6.0 was at 2.6.32 when it landed. Now rh el 6.1 + updates has arrived at least at 2.6.32-131.2.1.el6.x86_64 but it is quite different from the original kernel.org 2.6.32. You could issue a command such as rpm -q --changelog kernel-2.6.18-238.12.1.el5 to see all the patches + backports eventually added to a particular kernel rpm. You can also download the source rpm and see inside the tgz files all the patches applied (until the RH EL strategy changes in this respect due to Oracle and Novell providing recompiled rpms for their products/support plans...) HIH, Gianluca -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
