Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm hoping someone can clarify what's going on here. I've installed RHEL 3 with the aforementioned kernel on a 64-bit dual core Xeon box. Booting the SMP kernel results in a panic with the "no em64t cpu support in this kernel" message. However, booting the uniprocessor kernel not only runs fine, but shows two processors running in both top and /proc/cpuinfo.
Though uname -r shows kernel 2.4.21-37EL running, uname -a shows 2.4.21-37EL #1 SMP. It seems like the regular kernel is running both cores just fine even though everything I've read suggests that one must run an SMP kernel to get them both running. I've even checked the grub config to make sure the images weren't reversed. ;-) Can anyone help explain this apparent discrepancy? What am I missing?
Well, I can accept that answer, but for the other evidence. Namely, the install placed the usual 2 kernels in the grub config, one explicitly labeled SMP, and one (the one I can boot) not. Also, uname -r doesn't report SMP. Not trying to be cheeky, just trying to get clear on this.
Thanks Lenard, I follow what you're saying. For now, I've just set the grub default to pick the apparent uniprocessor kernel. I'm just trying to figure out why there would be effectively two SMP kernels with only one labeled up-front as such, typically these installs provide both an SMP and a uniprocessor option, do they not? Or are the image names perhaps just switched? That seems a bit wacky for a commercial package.
syg00, yeah it still exists back there.
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Xeon(R) CPU 5160 @ 3.00GHz
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
runqueue : 0
stepping : 6
cpu MHz : 2992.498
cache size : 0 KB
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm ferr syscall lm sse3 monitor ds-cpl gv3 tm2
bogomips : 5976.88
clflush size : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Xeon(R) CPU 5160 @ 3.00GHz
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
runqueue : 1
stepping : 6
cpu MHz : 2992.498
cache size : 0 KB
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm ferr syscall lm sse3 monitor ds-cpl gv3 tm2
bogomips : 5976.88
clflush size : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790
Rep:
Well with RHEL5 Red Hat quit making non-smp kernels as all kernels are now smp. maybe this is now true for other versions of RHEL now also. The /proc/cpuinfo is showing that you are running an smp kernel. Maybe the grub entries are wrong, but only you have seen them. Any way since the default is set to boot to the good working kernel then you good to go.
As a suggestion you might want to remove the entry(ies) in grub.conf for the bad kernel(s), this way somebody cannot mistakenly select the wrong one.
Good idea, I probably will edit that out. Sorry though, I wasn't trying to be enigmatic. ;-) The grub.conf in question:
----------------------------------------------
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda6
# initrd /initrd-version.img
#boot=/dev/sda
default=1
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Enterprise Linux ES (2.4.21-37.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.4.21-37.ELsmp ro root=LABEL=/ hda=ide-scsi
initrd /initrd-2.4.21-37.ELsmp.img
title Red Hat Enterprise Linux ES-up (2.4.21-37.EL)
root (hd0,0)
kernel /vmlinuz-2.4.21-37.EL ro root=LABEL=/ hda=ide-scsi
initrd /initrd-2.4.21-37.EL.img
------------------------------------------------
I just assumed from the names that ELsmp and EL referred to an SMP and non-SMP kernel, respectively.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.