RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 816009 - move crashkernel auto reserve theshold to 2G
Summary: move crashkernel auto reserve theshold to 2G
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: system-config-kdump
Version: 6.3
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Roman Rakus
QA Contact: Guangze Bai
URL:
Whiteboard:
Depends On:
Blocks: 915729
TreeView+ depends on / blocked
 
Reported: 2012-04-25 03:36 UTC by Dave Young
Modified: 2015-02-08 21:59 UTC (History)
6 users (show)

Fixed In Version: system-config-kdump-2.0.5-6.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 13:39:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0824 0 normal SHIPPED_LIVE system-config-kdump bug fix and enhancement update 2012-06-19 20:49:27 UTC

Description Dave Young 2012-04-25 03:36:19 UTC 
Description of problem:

X86 kdump crashkernel=auto threshold changed from 4G to 2G, so system-config-kdump also need a change.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 2 Roman Rakus 2012-04-25 12:58:38 UTC 
(In reply to comment #0)
> Description of problem:
> 
> X86 kdump crashkernel=auto threshold changed from 4G to 2G, so
> system-config-kdump also need a change.
Thanks for information.
Is only x86 changed or also ppc (or any other)?
Comment 3 Dave Young 2012-04-26 03:21:36 UTC 
(In reply to comment #2)
> (In reply to comment #0)
> > Description of problem:
> > 
> > X86 kdump crashkernel=auto threshold changed from 4G to 2G, so
> > system-config-kdump also need a change.
> Thanks for information.
> Is only x86 changed or also ppc (or any other)?

Hi, only x86 changed.

BTW, for the total memsize, kernel usually report less than actual physical
memory module size. So we did same as kernel side in firstboot.py: roundup
totalsize to 128M when we compare with the threshold.

I guess this is also necessary for system-config-kdump?
Comment 4 IBM Bug Proxy 2012-04-27 12:30:25 UTC 
(In reply to comment #7)
> > Thanks for information.
> > Is only x86 changed or also ppc (or any other)?

For s390x we will use 4 GiB (see Red Hat bug #815599). Could you please adjust firstboot and system-config-kdump accordingly?
Comment 5 Roman Rakus 2012-05-02 11:08:46 UTC 
(In reply to comment #4)
> (In reply to comment #7)
> > > Thanks for information.
> > > Is only x86 changed or also ppc (or any other)?
> 
> For s390x we will use 4 GiB (see Red Hat bug #815599). Could you please adjust
> firstboot and system-config-kdump accordingly?

s-c-kdump yes. In this bug.
Comment 7 Roman Rakus 2012-05-02 15:14:57 UTC 
Fixed in system-config-kdump-2.0.5-6.el6.
Comment 10 Georg Markgraf 2012-05-03 15:03:14 UTC 
Roman, 
do you (or Dan) handle the adjustment in first boot via this bug or will you create a clone for first boot?
Comment 11 IBM Bug Proxy 2012-05-03 15:40:57 UTC 
(In reply to comment #12)
> Roman,
> do you (or Dan) handle the adjustment in first boot via this bug or will you
> create a clone for first boot?

The following RHBZ reflects firstboot:

Bug 805040 - firstboot contains kdump which is not support on s390x
Comment 18 IBM Bug Proxy 2012-06-11 08:30:35 UTC 
Hi

I verified this feature on RHEL6.3-RC1 and if system memory less than 4gb on system-config-kdump user is not able to use automatic configuration but if system memory is 4gb than it works

Regards
Praveen
Comment 20 errata-xmlrpc 2012-06-20 13:39:14 UTC 
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/RHBA-2012-0824.html
Comment 21 IBM Bug Proxy 2015-02-08 21:59:21 UTC 
------- Comment From michael.holzheu.com 2012-04-27 12:28 EDT-------

------- Comment From brueckner.com 2012-05-03 15:33 EDT-------

------- Comment From Praveen.Pandey.com 2012-06-11 08:21 EDT-------
Note You need to log in before you can comment on or make changes to this bug.