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.
DescriptionDaniel Bristot de Oliveira
2016-11-18 08:42:30 UTC
Description of problem:
When running the kernel-rt-3.10.0-xxx (provided by MRG-RT product) on an RHEL6 in a system with EFI, the kdump does not work.
When the user hits sysrq + c, the system hangs without sending any information to the serial console.
Version-Release number of selected component (if applicable):
kernel-rt-3.10.0-229.rt56.147.el6rt.x86_64
kexec-tools-2.0.0-280.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Boot the system with efi enabled
2. Try to crash the system
3. System hangs
Actual results:
System hangs
Expected results:
kdump created
Additional info:
Workarounds:
There are two workarounds for the problem.
The first is to boot the system disabling EFI using the noefi kernel parameter.
The second is to umount debugfs before starting kdump service.
Daniel
Can you answer the question from QE why using 3.10 kernel with RHEL6 userspace? and Why not use RHEL7 user space?
Comment 10Daniel Bristot de Oliveira
2016-11-22 08:34:18 UTC
Hi Qiao,
The customer that faced the bug did the major part of the debugging. As they are very advanced users, I am quite sure they are open to test a solution if we deliver them a test package. Is that enough - the customer testing the solution?
-- Daniel
(In reply to Daniel Bristot de Oliveira from comment #10)
> Hi Qiao,
>
> The customer that faced the bug did the major part of the debugging. As they
> are very advanced users, I am quite sure they are open to test a solution if
> we deliver them a test package. Is that enough - the customer testing the
> solution?
>
> -- Daniel
Yes, It's ok for me. Thank you very much!
Set qa_ack+ and add OtherQA keywords.
Comment 14Daniel Bristot de Oliveira
2016-11-23 13:24:41 UTC
Hi!
Test package delivered to the customer. Now waiting on customer's feedback.
Thanks!
Comment 15Daniel Bristot de Oliveira
2016-11-28 08:04:16 UTC
Hi!
The customer tested the package and said that it fixed the problem.
Is there an ETA for the GA of this fix?
Thank you very much for the agility in this case.
-- Daniel
Hi,
Once the patch being reviewed in kdump mail list, we can merge it and create a official build, hopefully it will be within one week or two. But the GA for customer depends on RHEL6.9 schedule..
Thanks
Dave
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.
https://rhn.redhat.com/errata/RHBA-2017-0584.html