| Summary: | Default core_collector makedumpfile fails to write core file | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Mike Miller (OS Dev) <mike.miller> | ||||||
| Component: | kernel | Assignee: | Red Hat Kernel Manager <kernel-mgr> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 5.8 | CC: | mike.miller, qcai | ||||||
| Target Milestone: | rc | Flags: | pm-rhel:
needinfo?
(mike.miller) |
||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-06-02 13:20:27 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
What does the kdump.conf looks like? Make sure you having a dump target defined and "default shell" set. Also, if you have any kdump_pre and kdump_post script? There were some vital information missing from the console output. Can you extract the kdump initramfs and add "#!/bin/msh -x" to "init", and then put it back and re-run with new console output attached? Right now, it will reboot your system in those situations. # Configures where to put the kdump /proc/vmcore files # # This file contains a series of commands to perform (in order) when a # kernel crash has happened and the kdump kernel has been loaded. Directives in # this file are only applicable to the kdump initramfs, and have no effect if # the root filesystem is mounted and the normal init scripts are processed My modified kdump.conf is as follows: # # Currently only one dump target and path may be configured at once # if the configured dump target fails, the default action will be preformed # the default action may be configured with the default directive below. If the # configured dump target succedes # # See the kdump.conf(5) man page for details of configuration directives #raw /dev/sda5 #ext3 /dev/sda3 #ext3 LABEL=/boot #ext3 UUID=03138356-5e61-4ab3-b58e-27507ac41937 #net my.server.com:/export/tmp #net user.com #path /var/crash #core_collector makedumpfile -c --message-level 1 #core_collector cp --sparse=always core_collector cp #link_delay 60 #kdump_post /var/crash/scripts/kdump-post.sh #extra_bins /usr/bin/lftp #disk_timeout 30 #extra_modules gfs2 #options modulename options #default shell The default kdump.conf had all lines commented out. I'm gathering the output from the kdump initrd now. Will post separately. Created attachment 526308 [details]
kdump crash log with -x added to init
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug. Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support). |
Created attachment 525198 [details] kdump crash log Description of problem: On some systems the core_collector must be changed to cp for the core file to be written to disk. Version-Release number of selected component (if applicable): 5.7/5.8 How reproducible: Always Steps to Reproduce: 1. Setup kdump 2. Invoke a crash 3. Actual results: The core file is not written to disk. Expected results: The core file should saved to disk. Additional info: Changing the core_collector to cp allows kdump to work _most_ of the time. Attached file shows a possible recursive lock and an unexpected IRQ trap.