Red Hat Bugzilla – Bug 727892
kexec-tools: Warn a user to use maxcpus=1 instead of nr_cpus=1 for older kernels
Last modified: 2013-09-29 22:26:41 EDT
Description of problem: In RHEL 171 kernel we committed patches to make nr_cpus=1 command line option work in kdump kenrel. Now /etc/kdump.conf in kexec-tools package has been modified to use nr_cpus=1. But this change is not backward compatible. New kexec-tools will break with older kernels. So we need to do two things. - Put a warning to use maxcpus=1 if kernel version is older than 171 - Put a release not explaining the change in 6.2 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 517401 [details] Proposed patch
Tested with kexec-tools-2.0.0-204.el6: =================================================================== [root@intel-chiefriver-02 ~]# rpm -q kernel kexec-tools kernel-2.6.32-131.0.15.el6.x86_64 kexec-tools-2.0.0-204.el6.x86_64 [root@intel-chiefriver-02 ~]# touch /etc/kdump.conf [root@intel-chiefriver-02 ~]# service kdump restart Stopping kdump: [ OK ] Detected change(s) the following file(s): /etc/kdump.conf Rebuilding /boot/initrd-2.6.32-131.0.15.el6.x86_64kdump.img Your kernel is old, please use maxcpus=1 instead of nr_cpus[WARNING] Starting kdump: [ OK ] -------------------------------------------------------------------- [root@intel-chiefriver-02 ~]# uname -a Linux intel-chiefriver-02.lab.bos.redhat.com 2.6.32-202.el6.x86_64 #1 SMP Wed Sep 21 15:27:03 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux [root@intel-chiefriver-02 ~]# rpm -q kexec-tools kexec-tools-2.0.0-204.el6.x86_64 [root@intel-chiefriver-02 ~]# touch /etc/kdump.conf [root@intel-chiefriver-02 ~]# service kdump restart Stopping kdump: [ OK ] Detected change(s) the following file(s): /etc/kdump.conf Rebuilding /boot/initrd-2.6.32-202.el6.x86_64kdump.img Starting kdump: [ OK ] Change status to VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2011-1532.html