Bug 725105

Summary: kdump fails on 6.1 x86 with high lun count
Product: Red Hat Enterprise Linux 6 Reporter: apfeiffe
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED NOTABUG QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1CC: anthony.cheung, anthony.cheung, apfeiffe, bharath.bhushan, ddettke, huangj, matt.woempner, nkattang, phinchman, qcai, sapna.francis, william.gens
Target Milestone: rc   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-09-28 02:37:22 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:
Description Flags
Serial conole log from failed kdump
none
sosreport from failing system none

Description apfeiffe 2011-07-22 20:25:02 UTC
Created attachment 514790 [details]
Serial conole log from failed kdump

Description of problem:
Configuration:
- BL460c G6
- Red Hat 6.1 x86
- Kernel version
- 84 luns and 564 paths

Version-Release number of selected component (if applicable):
kernel-2.6.32-131.0.15.el6.i686
system-config-kdump-2.0.2.2-2.el6.noarch


How reproducible:
About 1 in 3 times it fails to kdump properly.

Steps to Reproduce:
1. Assign a high lun/path count to the system
2. trigger a kdump by running: echo "c" > /pro/sysrq-trigger

  
Actual results:
kdump kernel throws memory errors and then panics

Expected results:
kdump should dump a core file and reboot the system

Additional info:

Comment 1 apfeiffe 2011-07-22 20:29:42 UTC
Created attachment 514791 [details]
sosreport from failing system

Comment 3 Qian Cai 2011-07-25 01:55:56 UTC
Looks like this system is setup with multi-path which currently kdump did not support it at the moment.

Comment 4 apfeiffe 2011-08-01 22:57:14 UTC
kdump is configured for multi-path.  If I remove the extra paths it does create a dump file on the multipath device.  At this point, I have found out the customer I am performing this test for isn't going to support Red Hat 6.1 x86 so I will drop testing kdump on this OS.