Bug 442912
| Summary: | Kdump panics by vmcore copy when system uses booting from SAN | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Lumir Unzeitig <lunzeitig> |
| Component: | kernel | Assignee: | Red Hat Kernel Manager <kernel-mgr> |
| Status: | CLOSED DUPLICATE | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 5.0 | CC: | qcai |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-04-22 14:05:29 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: | |||
The error that you indicate above is fixed in kernel 2.6.18-34.el5. If you upgrade to that kernel or later, and specify the reset_devices commandline option in /etc/sysconfig/kdump, you're problem should clear up. Please confirm. Thanks! Thanks for quik reposnse. Unfortunatelly I cannot upgrade the kernel because there are piece of sw dependending on the kernel version (cluster,volume manager (veritas), file system (veritas) ). Does a workaround exist for getting the crashdump manually? Thanks for your answer. |
Description of problem: Kdump panics when tries to copy /proc/vmcore to a location (/var/crash or a server via scp). The kexec boots the right kernel nad ramdisk, the vmcore file is located in /proc, but the "cp" command in /etc/init.d/kdump file (save_core func) initiates panic. This behaviour happens on all 5 Linux systems which booting from the SAN. The others booted by local disks are OK. ---------- EDAC k8 MC0: GART TLB errorr: transaction type(generic), cache level(generic) EDAC k8 MC0: extended error code: GART error Kernel panic - not syncingL MC: processor context corrupt ---------- Version-Release number of selected component (if applicable): kexec: 1-1.0.1-164.el5 qla2xxx: 8.01.07.15 (source:QLogic) How reproducible: 100% in our configuration Steps to Reproduce: 1. Set up crashkernel=512M@16M for kernel 2. Start the kdump service 3. Initiate panic echo c > /proc/sysrq-trigger Actual results: Vmcore file is created but not copied out of /proc. Expected results: Vmcore file is copied to selected destination and sytem is rebooted. Additional info: HW: Fujitsu-Siemens, BladeSever BX630-S2 (4x DualCore AMD Proc 885), 8{32}GB RAM, HBA QLogic ISP23xx