On 6/12/19 1:07 PM, Borislav Petkov wrote: > On Wed, Jun 12, 2019 at 04:52:22PM +0000, Lendacky, Thomas wrote: >> I think the discussion ended up being that debuginfo wasn't being stripped >> from the kernel and initrd (mainly the initrd). What are the sizes of >> the kernel and initrd that you are loading for kdump via kexec? >> >> From previous post: >> kexec -s -p /boot/vmlinuz-5.2.0-rc3+ --initrd=/boot/initrd.img-5.2.0-rc3+ > > You mean those sizes? > > $ ls -lh /boot/vmlinuz-5.2.0-rc3+ /boot/initrd.img-5.2.0-rc3+ > -rw-r--r-- 1 root root 7.8M Jun 10 12:53 /boot/initrd.img-5.2.0-rc3+ > -rw-r--r-- 1 root root 6.7M Jun 10 12:53 /boot/vmlinuz-5.2.0-rc3+ > > That should fit easily in 256M :) Certainly seems like they should. I know there are other things that are loaded, but that should be plenty of room. I wonder if Baoquan or Lianbo could track where things are being loaded to see if everything is being calculated and placed properly. Thanks, Tom > _______________________________________________ kexec mailing list kexec@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/kexec
