[..] > > makedumpfile going to cyclic buffer has helped out greatly, but on > > our new systems we're still looking at 512 MB crash kernels. > > I tried 6TiB system/16 PCIE cards, kdump on RHEL 6.5 beta still does not work. > still get OOM. What crashkernel= option you are using? Interesting. So something is consuming lot of memory. How about setting "debug_mem_level 1" in /etc/kdump.conf and regenerate initrd and retry. This time it should output some memory usage info at various points during boot and that can give us some idea who is consuming how much memory. If some module are consuming lot of memory, then you can try "blacklist" option in /etc/kdump.conf to disable those. If it is not modules, then it will concern me because then either kernel is consuming too much memory (which it should not) or for some reason makedumpfile cyclic mode did not work for you properly. While you are re-testing, how about also increasing debug message level of makedumpfile. makedumpfile developers should be able to have a look at that. In /etc/kdump.conf, specify. core_collector makedumpfile -c --message-level 31 -d 31 If message level 31 turns out to be too verbose, reduce it as per makedumpfile man page. Thanks Vivek -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
