On 5/11/07, Bernhard Walle <bwalle at suse.de> wrote: > * Amul Shah <amul.shah at unisys.com> [2007-05-11 23:12]: > > I am using a redhat derived 2.6.18 linux kernel and I am experiencing a > > panic when the second kernel boots. I can't find the exact set of > > emails that I want to tell me that kexec on IA64 isn't ready yet. > > Well, it basically works ... > > > Horms said this a month ago: > > https://lists.linux-foundation.org/pipermail/fastboot/2007-March/013286.html > > My recommendation is that 2.6.21rc3 is a farily good release for > > kexec, > > and if you aren't worried about ia64 then 2.6.20 is probably > > good too. > > If you really need something against 2.6.9, then I guess you > > will have > > to try to pull the patches out of git, but that is going to be > > really hard work given that 2.6.9 is quite old now. > > > > For the curious, the panic log is below. I did a cursory inspection of > > the kernel sources and found that the function start_secondary is called > > from head.S. I don't know much about IA64 arch and assembly, so I > > thought I would ask first if the IA64 implementation works. > > Did you try the 'maxpus=1' option for the panic kernel? > > > Thanks, > Bernhard I'll give the maxcpus option a try. However, I used a kexec since the kdump failed and the people testing the functionality weren't sure what else to do. thanks, Amul (yes the same as the thread initiator)
