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 at in.ibm.com] > Sent: Wednesday, May 14, 2008 1:26 PM > To: gib > Cc: kexec at 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 at 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 at lists.infradead.org > http://lists.infradead.org/mailman/listinfo/kexec