Bug 240010
Summary: | Kexec/Kdump fails with RHEL5 on ES7000 ia64 EL Servers. | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Ramesh Babu Ankam <ramesh.ankam> |
Component: | kexec-tools | Assignee: | Neil Horman <nhorman> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.0 | CC: | ashwin.patil, jarod, luyu, mona.tumkurnarasimhamurthy, qcai, tarangini.polisetty, vineetha.ramachandra |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | ia64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-05-14 10:36:13 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ramesh Babu Ankam
2007-05-14 11:35:38 UTC
Does base kernel work or not? Is the kdump service enabled? You need to 'chkconfig kdump on' and 'service kdump start' to make sure the kdump environment actually gets set up. A manual kexec -l only loads a kernel for rebooting, not for panic dump. (In reply to comment #1) > Does base kernel work or not? By the steps to reproduce, we used the base kernel to kexec and it didn't work. (In reply to comment #2) > Is the kdump service enabled? You need to 'chkconfig kdump on' and 'service > kdump start' to make sure the kdump environment actually gets set up. A manual > kexec -l only loads a kernel for rebooting, not for panic dump. We didn't check the kdump part when we performed the steps in the bugzilla. We want to get the second kernel to boot when the first kernel panics. After we get to reboot, we can try the dump feature. Is kdump necessary to get kexec working? -Ashwin Just a 'kexec -l' won't work, that only specifies a kernel to reboot into via a clean kexec reboot. You need to load a kernel with 'kexec -p' (-p = panic kernel) for it to be used for an automatic reboot following a panic (this is part of what the kdump initscript does). You also must have a crashkernel memory region reserved for the panic kernel to use. Please see the HOWTO included in our kexec-tools rpm. Today we tried the kexec/kdump tests on RHEL5. All the tests were run in runlevel 3(Non-GUI mode) 1. RHEL5 Single Processor Results i. Kexec worked fine with kexec -l and kexec -e commands. ii.kdump gave a kernel panic with kexec -p command. Also, I executed a crash without the kexec -p but there were PROCNODE errors. 2. RHEL5 Multi Processor Results i. Kexec failed with Procnode error with kexec -l and kexec -e without kdump service running. ii.Kdump failed with Procnode error when a crash was initiated. Neil, any of this seem familiar to you at all? This is a new one to me... No, Can we please get: 1) /etc/kdump.conf from this system 2) the initramfs that kdump produces which gets loaded on kdump service start 3) serial console log of kexec kernels boot process ping. Any update here? ping. Is it safe to close? (In reply to comment #10) > ping. Is it safe to close? Ya you can close this issue. |