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):
Steps to Reproduce:
1. Boot the system with efi enabled
2. Try to crash the system
3. System hangs
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.
Can you answer the question from QE why using 3.10 kernel with RHEL6 userspace? and Why not use RHEL7 user space?
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?
(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
> -- Daniel
Yes, It's ok for me. Thank you very much!
Set qa_ack+ and add OtherQA keywords.
Here is a test build, I have tested on local machine, but feel free to do a test:
Hi, This is the V2 build though I believe there are no difference for testing:
Test package delivered to the customer. Now waiting on customer's feedback.
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.
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..
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.