Bug 461602

Summary: system-config-kdump shouldn't specify any offset
Product: [Fedora] Fedora Reporter: David Juran <djuran>
Component: system-config-kdumpAssignee: Roman Rakus <rrakus>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: rrakus, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-09-18 11:27:47 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:

Description David Juran 2008-09-09 12:17:59 UTC
Description of problem:
As discussed in bug 461001, with recent rawhide kernels, system-config-kdump shouldn't specify any offset when writing the configuration into grub.conf. I.e instead of specifying "crashkernel=128M@16M" it should only write "crashkernel=128M" This will let the kernel do the reservation at some suitable place where there is memory available, which may not be the case at the 16M offset 

Version-Release number of selected component (if applicable):
system-config-kdump-1.0.13-2.fc9

How reproducible:
Every time

Steps to Reproduce:
1. system-config-kdump -> activate kdump
2.
3.
  
Actual results:
in /etc/grub.conf it says "crashkernel=128M@16M"

Expected results:
crashkernel=128M

Comment 1 Roman Rakus 2008-09-16 14:46:27 UTC
Fized in rawhide: system-config-kdump-1.0.14-2.fc10