Hi, Vivek.

I applied all your patches to linux 2.6.16-mm1, and did kdump on my i386
machine with 8GB memory. But the problem that vmcore is truncated and
limited to 4GB wasn't solved.
Are there a command option etc. that should be specified?

arch       : i386 smp
kernel     : 2.6.16-mm1 + Viveck's patch(2006/03/23 64bit resources)
memory     : 8GB
kexec-tools: 1.01 + kdump7.patch

The operation log is as follows. 
--------------------------------------------------
# uname -r
2.6.16-mm1-kdump.smp
# free
             total       used       free     shared    buffers     cached
Mem:       8227052    1928564    6298488          0      72564    1695096
-/+ buffers/cache:     160904    8066148
Swap:      2096472          0    2096472
# cat /proc/cmdline
root=LABEL=/123 [EMAIL PROTECTED]
# kexec -p /boot/vmlinux-2.6.16-mm1-kdump.capture --args-linux \
> --elf64-core-headers --initrd=/boot/initrd-2.6.16-mm1-kdump.capture.img \
> --append="root=LABEL=/123 init 3"
# echo c > /proc/sysrq-trigger

(capture-kernel is booting.)

# uname -r
2.6.16-mm1-kdump.capture
# free
             total       used       free     shared    buffers     cached
Mem:         60516      53552       6964          0       1420      11756
-/+ buffers/cache:      40376      20140
Swap:      2096472      24216    2072256
# ll /proc/vmcore
-r--------  1 root root 4226876448  3月 30 10:58 /proc/vmcore
#
--------------------------------------------------

>o Currently /proc/iomem exports physical memory also apart from io device
>  memory. But on i386, it truncates any memory more than 4GB. This leads
>  to problems for kexec/kdump.
>
>o Kexec reads /proc/iomem to determine the system memory layout and prepares
>  a memory map based on that and passes it to the kernel being kexeced. Given
>  the fact that memory more than 4GB has been truncated, new kernel never
>  gets to see and use that memory.
>
>o Kdump also reads /proc/iomem to determine the physical memory layout of
>  the system and encodes this informaiton in ELF headers. After a crash
>  new kernel parses these ELF headers being used by previous kernel and
>  vmcore is prepared accordingly. As memory more than 4GB has been truncated,
>  kdump never sees that memory and never prepares ELF headers for it. Hence
>  vmcore is truncated and limited to 4GB even if there is more physical
>  memory in the system.
>
>o This patch exports memory more than 4GB through /proc/iomem on i386.

Thanks
Ken'ichi Ohmichi
_______________________________________________
fastboot mailing list
[email protected]
https://lists.osdl.org/mailman/listinfo/fastboot

Reply via email to