![]() | |||||||||||||
Messages in this thread |
> > > I've been doing some kexec tests (as described in Documentation/kdump.txt) too > > > but can't get to load the image and get similar error messages. Let me know > > > if you need more info about the hardware. The first_kernel was booted with > > > "crashkernel=64M@16M" and the 16M value was configured into the second during > > > kconfig in "Physical address where the kernel is loaded" as 0x1000000. > > > > > > [root@zmei]: kexec -p vmlinux --args-linux --append="root=/dev/hda1 maxcpus=1 > > > init 1" > > > > kexec-tools-1.101 loads for me, but if cmdline is used, it hangs up > > after "Starting new kernel" > > maxcpus=1 is the culprit. Even through bios/grub kernel does not boot with > option maxcpus=1. It is a known issue with got notieced 2.6.12-rc2-mm1 onwards. > So build second kernel as uniprocessor kernel and don't specify maxcpus=1 and > test it out. It should work. > Vivek, kexec-tools-1.101 does not contain your last patch series (that includes --crashdump which is lacking from the above cmdline). Currently you need to patch up 1.101 with the stuff from [RFC/PATCH 5/17][kexec-tools-1.101] Add command line option "--crash-dump" etc. It would be good having a 1.2 or something with the patches included on the site... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-05-11 09:19 [from the cache] ©2003-2008 | |||||||||||||