Question about forcing kernel panic on PowerMac G5 by kexec command
Mohan Kumar M
mohan at in.ibm.com
Wed Apr 23 05:48:07 EDT 2008
> Hi Mohan,
> Thank you very much for your reply.
>> What kernel version you are trying? Also what level of kexec-tools you
> I've tried kernel 2.6.24 and 2.6.25 with the kexec-tools-testing 20080324,
> the both of them gave me the same result.
I am not sure about the latest kexec tools. Is it possible to test with
the kexec-tools shipped with the distro?
>> I hope you are aware that you need two different kernels for kdump,
>> first one is meant for normal use and another one is kdump kernel. Did
>> you compile the kdump kernel with CONFIG_CRASH_DUMP?
> Yes, I built 2 kernels the first one as the system kernel and the second one
> as the dump-capture kernel(with CONFIG_CRASH_DUMP).
> Another notice is when I pre-loaded the dump-capture kernel(kexec -p
> /boot/vmlinux...), I got
> Modified cmdline: elfcorehdr=41188K savemaxmem=0M ...
> segment.mem:0x2000000 memsz:8269624
> segment.mem:0x27e3000 memsz:65536
> segment.mem:0x27f3000 memsz:4096
> segment.mem:0x27f4000 memsz:36864
> segment.mem:0x9fbf000 memsz:266240
> Why the savemaxmem=0M? since it should be some value else.
> Do you have any idea about this?
savemaxmem should give current memory.
Can you give us the contents of the reg property in the last memory node
in device tree?
For eg, in my POWER5 system,
# hexdump /proc/device-tree/memory at d8000000/reg
0000000 0000 0000 d800 0000 0000 0000 0200 0000
> -----Original Message-----
> From: Mohan Kumar M [mailto:mohan at in.ibm.com]
> Sent: Tuesday, April 22, 2008 2:35 PM
> To: gib
> Cc: kexec at lists.infradead.org
> Subject: Re: Question about forcing kernel panic on PowerMac G5 by kexec
> gib wrote:
>> Hello all,
>> I'm working on PowerMac G5 complied with CONFIG_KEXEC = y.
>> It's work fine with Kexec command option l ( kexec -l /boot/vmlinux. )
>> but after the capture kernel pre-loading ( by kexec -p /boot/vmlinux. ),
> Hi Suchada,
> What kernel version you are trying? Also what level of kexec-tools you use?
> I hope you are aware that you need two different kernels for kdump,
> first one is meant for normal use and another one is kdump kernel. Did
> you compile the kdump kernel with CONFIG_CRASH_DUMP?
>> when I forced kernel panic by "echo c > /proc/sysrq-trigger" the console
>> kept showing "Sending IPI to other CPU" and did not go to the next step.
>> According to this list there was some problem about kdump in ppc970 based
> CPU which PowerMac's CPU are.
> There was a interrupt routing problem with specific ppc970 cpu type, but
> that problem is fixed now.
> kexec mailing list
> kexec at lists.infradead.org
More information about the kexec