Hide Forgot
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:
Created attachment 514791 [details] sosreport from failing system
Looks like this system is setup with multi-path which currently kdump did not support it at the moment.
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.