On 08/01/2013 04:55 AM, Vivek Goyal wrote:
On Wed, Jul 31, 2013 at 04:48:00PM -0400, Vivek Goyal wrote:
On Wed, Jul 31, 2013 at 04:42:27PM -0400, Vivek Goyal wrote:
[..]
This system is behaving strangely. Yesterday I tried everything and it did not work and today both 3.9 and 3.10 kernel seem to work (with acpi_rsdp=). I am upgrading kexec-tools now and will try again. If that works, then will try without acpi_rsdp.
Well, with 3.10 kernel boots up device showsup but dump saving fails. Looks like makedumpfile bailed out.
Hopefully upgrading kexec-tools will fix it.
Well now OOM killer trigger while loading selinux policy. Red flags, memory utilization of various components has gone up and even 128MB does not seem to be sufficient.
I upgraded from kexec-tools-2.0.3-71.fc19.x86_64 to kexec-tools-2.0.4-5.fc19.x86_64 and memory problem started happening. Have we done any significant change in kexec-tools which contributes to this.
The main contribute is Harald enabled 98selinux. Chaowang said selinux will use ~50M memory as the peak for load_policy. That is too much..
Ccing selinux peole Daniel and Eric. I wonder if there's a way we can use in kdump initrd for minimum memory footprint. Because we will not switch_root, so it will not influence the normal 1st kernel selinux.
Thanks Vivek