Bug 510995
| Summary: | Problem of system-config-kdump (ex: crashkernel=0M@16M) | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Masaki MAENO <maeno.masaki> |
| Component: | system-config-kdump | Assignee: | Martin Milata <mmilata> |
| Status: | CLOSED CANTFIX | QA Contact: | BaseOS QE <qe-baseos-auto> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.3 | CC: | rrakus |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-03-12 14:01:09 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Can you please provide output of `system-config-kdump -d'? 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. 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. Masaki ping? Any update? (In reply to comment #5) > Masaki ping? Any update? I don't have any machine for test now. So, I don't confirm the problem by new packages. I updated the status. I am sorry, but it is now too late in the RHEL-5 release cycle. RHEL-5.10 (the next RHEL-5 minor release) is going to be the first production phase 2 [1] release of RHEL-5. Since phase 2 we'll be addressing only security and critical issues. Due to the lack of information I am closing the bug as CANTFIX. [1] https://access.redhat.com/support/policy/updates/errata/ |
Description of problem: In a certain SAN-boot machine, the setting of kdump doesn't become correct, even if we set kdump by 'system-config-kdump'. Version-Release number of selected component (if applicable): - RHEL5.3 (kernel-2.6.18-128.el5) - system-config-kdump-1.0.14-4.el5 Steps to Reproduce: 1. Set 128MB as 2nd-kernel (kdump-kernel) by system-config-kdump Actual results: /boot/grub/grub.conf ... kernel kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/sda1 \ rhgb quiet crashkernel=0M@16M ... Expected results: ... kernel kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/sda1 \ rhgb quiet crashkernel=128M@16M ...