Question about forcing kernel panic on PowerMac G5 by kexec command

Question about forcing kernel panic on PowerMac G5 by kexec command

[gib]

[-- Attachment #1.1: Type: text/plain, Size: 578 bytes --]

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. ), 

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.

Does anybody know about this issue? It would be very helpful for me.

 

Thanks in advance.

Suchada


[-- Attachment #1.2: Type: text/html, Size: 3914 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

Re: Question about forcing kernel panic on PowerMac G5 by kexec command

[Mohan Kumar M]

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.

Regards,
Mohan.


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

RE: Question about forcing kernel panic on PowerMac G5 by kexec command

[gib]

Hi Mohan,

Thank you very much for your reply.

> What kernel version you are trying? Also what level of kexec-tools you
use?
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 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[0].mem:0x2000000 memsz:8269624
	segment[1].mem:0x27e3000 memsz:65536
	segment[2].mem:0x27f3000 memsz:4096
	segment[3].mem:0x27f4000 memsz:36864
	segment[5].mem:0x9fbf000 memsz:266240

Why the savemaxmem=0M? since it should be some value else.
Do you have any idea about this?

Regards,
Suchada

-----Original Message-----
From: Mohan Kumar M [mailto:mohan@in.ibm.com] 
Sent: Tuesday, April 22, 2008 2:35 PM
To: gib
Cc: kexec@lists.infradead.org
Subject: Re: Question about forcing kernel panic on PowerMac G5 by kexec
command

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.

Regards,
Mohan.



_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

Re: Question about forcing kernel panic on PowerMac G5 by kexec command

[Mohan Kumar M]

gib wrote:
> Hi Mohan,
> 
> Thank you very much for your reply.
> 
>> What kernel version you are trying? Also what level of kexec-tools you
> use?
> 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.
> 

Hi Gib,

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[0].mem:0x2000000 memsz:8269624
> 	segment[1].mem:0x27e3000 memsz:65536
> 	segment[2].mem:0x27f3000 memsz:4096
> 	segment[3].mem:0x27f4000 memsz:36864
> 	segment[5].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@d8000000/reg
0000000 0000 0000 d800 0000 0000 0000 0200 0000
0000010

Regards,
Mohan.

> -----Original Message-----
> From: Mohan Kumar M [mailto:mohan@in.ibm.com] 
> Sent: Tuesday, April 22, 2008 2:35 PM
> To: gib
> Cc: kexec@lists.infradead.org
> Subject: Re: Question about forcing kernel panic on PowerMac G5 by kexec
> command
> 
> 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.
> 
> Regards,
> Mohan.
> 
> 
> 
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

RE: Question about forcing kernel panic on PowerMac G5 by kexec command

[gib]

Hi Mohan,

Sorry for the late reply.

> I am not sure about the latest kexec tools. Is it possible to test with 
> the kexec-tools shipped with the distro?

I tried to test with the kexec-tools shipped with the distro before and it
gave me the same result as the latest kexec-tools (kexec-tools-testing
20080324).

> Can you give us the contents of the reg property in the last memory node 
> in device tree?

With the command # hexdump /proc/device-tree/memory@0,0/reg I got
0000000 0000 0000 0000 0000 2000 0000 0000 0000
0000010 0000 0000 0000 0000 0000 0000 2000 0000
0000020 2000 0000 0000 0000 4000 0000 2000 0000
0000030 0000 0000 0000 0000 0000 0000 0000 0000
*
0000060

Is it because of this problem that cause the system did not go the next step
and kept showing "Sending IPI to other CPU" message?

Thanks for your help,
Suchada

-----Original Message-----
From: Mohan Kumar M [mailto:mohan@in.ibm.com] 
Sent: Wednesday, April 23, 2008 6:48 PM
To: gib; kexec@lists.infradead.org
Subject: Re: Question about forcing kernel panic on PowerMac G5 by kexec
command

gib wrote:
> Hi Mohan,
> 
> Thank you very much for your reply.
> 
>> What kernel version you are trying? Also what level of kexec-tools you
> use?
> 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.
> 

Hi Gib,

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[0].mem:0x2000000 memsz:8269624
> 	segment[1].mem:0x27e3000 memsz:65536
> 	segment[2].mem:0x27f3000 memsz:4096
> 	segment[3].mem:0x27f4000 memsz:36864
> 	segment[5].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@d8000000/reg
0000000 0000 0000 d800 0000 0000 0000 0200 0000
0000010

Regards,
Mohan.

> -----Original Message-----
> From: Mohan Kumar M [mailto:mohan@in.ibm.com] 
> Sent: Tuesday, April 22, 2008 2:35 PM
> To: gib
> Cc: kexec@lists.infradead.org
> Subject: Re: Question about forcing kernel panic on PowerMac G5 by kexec
> command
> 
> 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.
> 
> Regards,
> Mohan.
> 
> 
> 
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec



_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

Re: Question about forcing kernel panic on PowerMac G5 by kexec command

[Mohan Kumar M]

gib wrote:
> Hi Mohan,
> 
> Sorry for the late reply.
> 
>> I am not sure about the latest kexec tools. Is it possible to test with 
>> the kexec-tools shipped with the distro?
> 
> I tried to test with the kexec-tools shipped with the distro before and it
> gave me the same result as the latest kexec-tools (kexec-tools-testing
> 20080324).
> 
>> Can you give us the contents of the reg property in the last memory node 
>> in device tree?
> 
> With the command # hexdump /proc/device-tree/memory@0,0/reg I got
> 0000000 0000 0000 0000 0000 2000 0000 0000 0000
> 0000010 0000 0000 0000 0000 0000 0000 2000 0000
> 0000020 2000 0000 0000 0000 4000 0000 2000 0000
> 0000030 0000 0000 0000 0000 0000 0000 0000 0000
> *
> 0000060
> 

Hi Suchada,

Do you have only one entry for memory node in the /proc/device-tree 
directory?

Do you know last good working version of kernel (for kdump) and try to 
boot into that kernel and check the memory nodes in device-tree?

kexec-tools uses reg property in the memory device nodes to calculate 
the total system memory.

 From above "hexdump", I could not parse the memory properties.

Regards,
Mohan.


> Is it because of this problem that cause the system did not go the next step
> and kept showing "Sending IPI to other CPU" message?
> 
> Thanks for your help,
> Suchada
> 


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

RE: Question about forcing kernel panic on PowerMac G5 by kexec command

[gib]

Hi Mohan,

> Do you have only one entry for memory node in the /proc/device-tree
directory?
Yes, I have only one entry(for memory) in the /proc/device-tree directory.

> Do you know last good working version of kernel (for kdump) and try to 
> boot into that kernel and check the memory nodes in device-tree?
What is the last version of kernel for kdump which you mentioned?
(now I using the vanilla kernel 2.6.25 version)

Please tell me and I will try to boot into it.

Thank you,
Suchada

-----Original Message-----
From: Mohan Kumar M [mailto:mohan@in.ibm.com] 
Sent: Wednesday, May 14, 2008 1:26 PM
To: gib
Cc: kexec@lists.infradead.org
Subject: Re: Question about forcing kernel panic on PowerMac G5 by kexec
command

gib wrote:
> Hi Mohan,
> 
> Sorry for the late reply.
> 
>> I am not sure about the latest kexec tools. Is it possible to test with 
>> the kexec-tools shipped with the distro?
> 
> I tried to test with the kexec-tools shipped with the distro before and it
> gave me the same result as the latest kexec-tools (kexec-tools-testing
> 20080324).
> 
>> Can you give us the contents of the reg property in the last memory node 
>> in device tree?
> 
> With the command # hexdump /proc/device-tree/memory@0,0/reg I got
> 0000000 0000 0000 0000 0000 2000 0000 0000 0000
> 0000010 0000 0000 0000 0000 0000 0000 2000 0000
> 0000020 2000 0000 0000 0000 4000 0000 2000 0000
> 0000030 0000 0000 0000 0000 0000 0000 0000 0000
> *
> 0000060
> 

Hi Suchada,

Do you have only one entry for memory node in the /proc/device-tree 
directory?

Do you know last good working version of kernel (for kdump) and try to 
boot into that kernel and check the memory nodes in device-tree?

kexec-tools uses reg property in the memory device nodes to calculate 
the total system memory.

 From above "hexdump", I could not parse the memory properties.

Regards,
Mohan.


> Is it because of this problem that cause the system did not go the next
step
> and kept showing "Sending IPI to other CPU" message?
> 
> Thanks for your help,
> Suchada
> 



_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

Re: Question about forcing kernel panic on PowerMac G5 by kexec command

[Mohan Kumar M]

gib wrote:
> Hi Mohan,
> 
>> Do you have only one entry for memory node in the /proc/device-tree
> directory?
> Yes, I have only one entry(for memory) in the /proc/device-tree directory.
> 
>> Do you know last good working version of kernel (for kdump) and try to 
>> boot into that kernel and check the memory nodes in device-tree?
> What is the last version of kernel for kdump which you mentioned?
> (now I using the vanilla kernel 2.6.25 version)

Hi Suchada,

Sorry, I don't have information related to G5 and kexec/kdump. Still I 
am not sure why the device tree is exporting only one memory node.

Regards,
Mohan.

> 
> Please tell me and I will try to boot into it.
> 
> Thank you,
> Suchada
> 
> -----Original Message-----
> From: Mohan Kumar M [mailto:mohan@in.ibm.com] 
> Sent: Wednesday, May 14, 2008 1:26 PM
> To: gib
> Cc: kexec@lists.infradead.org
> Subject: Re: Question about forcing kernel panic on PowerMac G5 by kexec
> command
> 
> gib wrote:
>> Hi Mohan,
>>
>> Sorry for the late reply.
>>
>>> I am not sure about the latest kexec tools. Is it possible to test with 
>>> the kexec-tools shipped with the distro?
>> I tried to test with the kexec-tools shipped with the distro before and it
>> gave me the same result as the latest kexec-tools (kexec-tools-testing
>> 20080324).
>>
>>> Can you give us the contents of the reg property in the last memory node 
>>> in device tree?
>> With the command # hexdump /proc/device-tree/memory@0,0/reg I got
>> 0000000 0000 0000 0000 0000 2000 0000 0000 0000
>> 0000010 0000 0000 0000 0000 0000 0000 2000 0000
>> 0000020 2000 0000 0000 0000 4000 0000 2000 0000
>> 0000030 0000 0000 0000 0000 0000 0000 0000 0000
>> *
>> 0000060
>>
> 
> Hi Suchada,
> 
> Do you have only one entry for memory node in the /proc/device-tree 
> directory?
> 
> Do you know last good working version of kernel (for kdump) and try to 
> boot into that kernel and check the memory nodes in device-tree?
> 
> kexec-tools uses reg property in the memory device nodes to calculate 
> the total system memory.
> 
>  From above "hexdump", I could not parse the memory properties.
> 
> Regards,
> Mohan.
> 
> 
>> Is it because of this problem that cause the system did not go the next
> step
>> and kept showing "Sending IPI to other CPU" message?
>>
>> Thanks for your help,
>> Suchada
>>
> 
> 
> 
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

Re: Question about forcing kernel panic on PowerMac G5 by kexec command

[Mohan Kumar M]

Mohan Kumar M wrote:
> gib wrote:
>> Hi Mohan,
>>
>>> Do you have only one entry for memory node in the /proc/device-tree
>> directory?
>> Yes, I have only one entry(for memory) in the /proc/device-tree directory.
>>
>>> Do you know last good working version of kernel (for kdump) and try to 
>>> boot into that kernel and check the memory nodes in device-tree?
>> What is the last version of kernel for kdump which you mentioned?
>> (now I using the vanilla kernel 2.6.25 version)
> 
> Hi Suchada,
> 
> Sorry, I don't have information related to G5 and kexec/kdump. Still I 
> am not sure why the device tree is exporting only one memory node.

Hi Suchada,

Is there any node called "ibm,dynamic-reconfiguration-memory" in the 
device tree?

Regards,
Mohan.


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

RE: Question about forcing kernel panic on PowerMac G5 by kexec command

[gib]

Hi Mohan,

> Is there any node called "ibm,dynamic-reconfiguration-memory" in the 
> device tree?
There is no any node called "ibm,dynamic-reconfiguration-memory" in my
PowerMac G5.
What is the mentioned node (ibm,dynamic-reconfiguration-memory) responsible
for?

Regards,
Suchada

-----Original Message-----
From: Mohan Kumar M [mailto:mohan@in.ibm.com] 
Sent: Friday, May 23, 2008 6:05 PM
To: gib
Cc: kexec@lists.infradead.org
Subject: Re: Question about forcing kernel panic on PowerMac G5 by kexec
command

Mohan Kumar M wrote:
> gib wrote:
>> Hi Mohan,
>>
>>> Do you have only one entry for memory node in the /proc/device-tree
>> directory?
>> Yes, I have only one entry(for memory) in the /proc/device-tree
directory.
>>
>>> Do you know last good working version of kernel (for kdump) and try to 
>>> boot into that kernel and check the memory nodes in device-tree?
>> What is the last version of kernel for kdump which you mentioned?
>> (now I using the vanilla kernel 2.6.25 version)
> 
> Hi Suchada,
> 
> Sorry, I don't have information related to G5 and kexec/kdump. Still I 
> am not sure why the device tree is exporting only one memory node.

Hi Suchada,

Is there any node called "ibm,dynamic-reconfiguration-memory" in the 
device tree?

Regards,
Mohan.



_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec