Hide Forgot
Created attachment 497307 [details] Screenshot Description of problem: When use crashkernel=512M-4G:128M,4G-:256M, system-config-kdump can't recognize this. [root@amd-dinar-02 ~]# cat /boot/grub/grub.conf # 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/mapper/vg_amddinar02-lv_root # initrd /initrd-[generic-]version.img #boot=/dev/sda default=0 timeout=5 serial --port=0x03f8 --speed=115200 terminal --timeout=5 serial console title Red Hat Enterprise Linux (2.6.32-131.0.13.el6.x86_64) root (hd0,0) kernel /vmlinuz-2.6.32-131.0.13.el6.x86_64 root=/dev/mapper/vg_amddinar02-lv_root ro rd_LVM_LV=vg_amddinar02/lv_root rd_LVM_LV=vg_amddinar02/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us console=ttyS0,115200n81 crashkernel=512M-4G:128M,4G-:256M initrd /initramfs-2.6.32-131.0.13.el6.x86_64.img [root@amd-dinar-02 ~]# cat /proc/cmdline root=/dev/mapper/vg_amddinar02-lv_root ro rd_LVM_LV=vg_amddinar02/lv_root rd_LVM_LV=vg_amddinar02/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us console=ttyS0,115200n81 crashkernel=512M-4G:128M,4G-:256M [root@amd-dinar-02 ~]# cat /sys/kernel/kexec_crash_size 268435456 [root@amd-dinar-02 ~]# service kdump status Kdump is operational [root@amd-dinar-02 ~]# system-config-kdump Version-Release number of selected component (if applicable): kexec-tools-2.0.0-188.el6.x86_64 system-config-kdump-2.0.2.2-2.el6.noarch kernel-2.6.32-131.0.13.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.Install RHEL6.1-20110503.0 2.Install system-config-kdump 3. Actual results: Not support Expected results: This kind of syntax should be supported Additional info:
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
*** This bug has been marked as a duplicate of bug 676777 ***