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.
Created attachment 514790[details]
Serial conole log from failed kdump
Description of problem:
Configuration:
- BL460c G6
- Red Hat 6.1 x86
- Kernel version
- 84 luns and 564 paths
Version-Release number of selected component (if applicable):
kernel-2.6.32-131.0.15.el6.i686
system-config-kdump-2.0.2.2-2.el6.noarch
How reproducible:
About 1 in 3 times it fails to kdump properly.
Steps to Reproduce:
1. Assign a high lun/path count to the system
2. trigger a kdump by running: echo "c" > /pro/sysrq-trigger
Actual results:
kdump kernel throws memory errors and then panics
Expected results:
kdump should dump a core file and reboot the system
Additional info:
kdump is configured for multi-path. If I remove the extra paths it does create a dump file on the multipath device. At this point, I have found out the customer I am performing this test for isn't going to support Red Hat 6.1 x86 so I will drop testing kdump on this OS.
Created attachment 514790 [details] Serial conole log from failed kdump Description of problem: Configuration: - BL460c G6 - Red Hat 6.1 x86 - Kernel version - 84 luns and 564 paths Version-Release number of selected component (if applicable): kernel-2.6.32-131.0.15.el6.i686 system-config-kdump-2.0.2.2-2.el6.noarch How reproducible: About 1 in 3 times it fails to kdump properly. Steps to Reproduce: 1. Assign a high lun/path count to the system 2. trigger a kdump by running: echo "c" > /pro/sysrq-trigger Actual results: kdump kernel throws memory errors and then panics Expected results: kdump should dump a core file and reboot the system Additional info: