<br><br><div class="gmail_quote">On Fri, Mar 14, 2008 at 4:02 AM, Mohan Kumar M <<a href="mailto:mohan@in.ibm.com">mohan@in.ibm.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Fri, Mar 14, 2008 at 03:36:58AM -0700, Rajasekaran P wrote:<br>
> On Tue, Mar 11, 2008 at 11:48 AM, Geoff Levand <<a href="mailto:geoffrey.levand@am.sony.com">geoffrey.levand@am.sony.com</a>><br>
> wrote:<br>
><br>
</div><div class="Ih2E3d">> Initially I made mistake by referring /proc/meminfo and thought the total<br>
> RAM was > 200M iB (actually it shows around 211MiB in /proc/meminfo<br>
> excluding swap space). But actual available memory is 128MiB only. Thats why<br>
> reserving 128MiB on 32MiB failed and kernel was not booting up.<br>
><br>
> Now "crashkernel" argument works properly for 64MB@64MB and kernel reserves<br>
> 64MB for crash dump capture kernel.<br>
<br>
</div>In PPC64, crashkernel base address is hard coded i.e it is always loaded<br>
at 32MB, even though you have passed 64MB@64MB. Did you get any warning<br>
message like crashkernel reserved at 32MB?<br>
<div class="Ih2E3d"><br>
><br>
> This memory is reserved for "dump capture kernel" which will be loaded later<br>
> by using kexec. Please refer linux_src/Documentation/kdump/kdump.txt for<br>
> more information.<br>
><br>
> I tried to load dump capture configured kernel and facing similar kind of<br>
> problem. After successful loading, Dump capture kernel is NOT BOOTING UP<br>
> upon kernel crash.<br>
<br>
</div>Do you get any message from the dump capture kernel? How do you trigger<br>
the dump?<br>
<div class="Ih2E3d"><br>
> I used the following command to load:<br>
><br>
> # kexec -t elf-ppc64 --append="video=ps3fb:mode:166 rhgb root=/dev/ps3da3<br>
> single maxcpus=1 noirqdistrib" \<br>
> --initrd=/boot/initrd-2.6.23-kdump.img \<br>
> -p vmlinux.strip.kdump<br>
<br>
</div> ^^ Is this kernel compiled with CRASH_DUMP enabled? If yes, it<br>
should build the kernel for 32MB.</blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<div class="Ih2E3d"><br>
> *<br>
> Output:*<br>
> *setup_memory_ranges memory_range[0] start:585001, end:8000000<br>
> get memory ranges:1<br>
> setup_memory_ranges memory_range[0] start:585001, end:8000000<br>
> Modified cmdline:video=ps3fb:mode:166 rhgb root=/dev/ps3da3 single maxcpus=1<br>
> noirqdistrib elfcorehdr=71068K savemaxmem=64M<br>
> segment[0].mem:0x4000000 memsz:5599232<br>
<br>
</div> ^^ Says the vmlinux is loaded at 64MB<br>
<div><div></div><div class="Wj3C7c">> segment[1].mem:0x4557000 memsz:65536<br>
> segment[2].mem:0x4567000 memsz:4096<br>
> segment[3].mem:0x4568000 memsz:36864<br>
> segment[4].mem:0x4571000 memsz:3469312<br>
> segment[5].mem:0x7fff000 memsz:4096<br>
> *<br>
> One more thing I confirmed was, this same dump capture kernel boots up<br>
> properly when I load it on normal mode (kexec -l and then kexec -e). I am<br>
> having no clue on this..</div></div></blockquote><div><span style="color: rgb(0, 0, 153);"><br>Yes,I built this kernel with CRASH_DUMP and VMCORE file system enabled. Moreover, I disabled SMP as well.</span><br style="color: rgb(0, 0, 153);">
<span style="color: rgb(0, 0, 153);">My system kernel is (First kernel) is SMP enabled, does it matter?<br><br>I dont get any message from dump capture kernel.<br><br>I trigger crash dump using :</span><br style="color: rgb(51, 51, 255);">
<p style="color: rgb(0, 0, 153);"><font face="Verdana" size="2"><span style="font-size: 10pt; font-family: Verdana;">echo c > /proc/sysrq-trigger</span></font></p>
<span style="color: rgb(0, 0, 153);">Initially capture kernel was loaded into 32MB only, but still it was not booting. So I tweaked the </span><font style="color: rgb(0, 0, 153);" face="Verdana" size="2"><span style="font-size: 10pt; font-family: Verdana;">KDUMP_KERNELBASE macro to load capture kernel to 64MB ( My idea is, first 64MB for system kernel and second 64MB for capture kernel). Should it be 32MB only?<br>
</span></font></div></div><br>