Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
1. Feature Overview:
Feature Id: [67056]
a. Name of Feature: [6.1 FEAT] Dump on panic - Prevent reipl loop
b. Feature Description
This features provide tooling, via a configuration (time delay for activation of this trigger) to
discourage a configuration of dump&ipl on panic that may lead into an infinite panic-dump-ipl loop.
A new keyword DELAY_MINUTES is introduced in the dumpconf configuration file. Using this keyword the
activation of dumpconf can be delayed in order to prevent potential re-IPL loops.
2. Feature Details:
Sponsor: LTC zSeries BOE
Architectures: zSeries - 64 native,
Arch Specificity: purely arch specific code
Affects Kernel Modules: Field does not exist
Delivery Mechanism: Backport
Category: other
Request Type: Package - Feature from Upstream
d. Upstream Acceptance: Field does not exist
Sponsor Priority P1
f. Severity: ship issue
IBM Confidential: No
Code Contribution: IBM code
g. Component Version Target:---
3. Business Case
Improve serviceability of Linux kernel problems and prevent an infinite panic-dump-ipl loop-
4. Primary contact at Red Hat:
John Jarvis jjarvis
5. Primary contacts at Partner:
Project Management Contact:
Hans-Georg Markgraf, mgrf.com
Technical contact(s):
Gonzalo Muelas Serrano, gmuelas.com
Created attachment 463959[details]
s390-tools-rhel6-dumpconf-prevent-loop.patch
------- Comment on attachment From brueckner.ibm.com 2010-12-01 07:16 EDT-------
Summary: dumpconf: Prevent re-IPL loop for dump on panic.
Description: A new keyword DELAY_MINUTES is introduced in the dumpconf.
configuration file. Using this keyword the activation of dumpconf
can be delayed in order to prevent potential re-IPL loops.
This enhancement request was evaluated by the full Red Hat Enterprise Linux
team for inclusion in a Red Hat Enterprise Linux minor release. As a
result of this evaluation, Red Hat has tentatively approved inclusion of
this feature in the next Red Hat Enterprise Linux Update minor release.
While it is a goal to include this enhancement in the next minor release
of Red Hat Enterprise Linux, the enhancement is not yet committed for
inclusion in the next minor release pending the next phase of actual
code integration and successful Red Hat and partner testing.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0601.html
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0601.html