On Thu, Mar 30, 2006 at 04:37:16PM +0900, Ken'ichi Ohmichi wrote: > > 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.
Hi, Thanks for testing it out. > # 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" command line looks ok. For future testings, you can also specify "irqpoll" option to reduce the chances of driver initialization failing in second kernel. > # 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 > # There was one more patch from maneesh to resolve the /proc/vmcore size issue. On my system even if dump size was more than 4G, but /proc/vmcore was not showing it correctly. Once I copied it to disk, size was correct. Can you please apply following patch also. http://marc.theaimsgroup.com/?l=linux-kernel&m=114322483016676&w=2 In fact all these patches are now in -mm2. So can directly test it with -mm2 without applying any additional patches. Copy the dump to the disk and it should be of right size. If it is not, can you please also provide me the output of /proc/iomem from the first kernel. Thanks Vivek
_______________________________________________ fastboot mailing list [email protected] https://lists.osdl.org/mailman/listinfo/fastboot
