Hi Holger, Le Tuesday 17 February 2009 18:36:40 Holger Gross, vous avez écrit : > Hi, > > i have the same problem using kexec with buffalo whr g54s openwrt rc2 > kernel 2.4:
2.4 kernel ? are you sure ? If so, you will not be able to kexec into a new kernel, this is a 2.6 specific feature. > > kexec_load failed: Success > entry = 0x298000 flags = 0 > nr_segments = 2 > segment[0].buf = 0x2ac37008 > segment[0].bufsz = 27307b > segment[0].mem = 0x1000 > segment[0].memsz = 297000 > segment[1].buf = 0x456338 > segment[1].bufsz = 1a4 > segment[1].mem = 0x298000 > segment[1].memsz = 1000 > > is there any solution for this? > > Am 07.02.2009 12:25, schrieb Florian Fainelli: > > Hi Brian, > > > > Le Saturday 07 February 2009 05:45:44 Brian J. Murrell, vous avez écrit : > >> I have an asus wl500gp that I'm trying to kexec a kernel on. I had > >> written about this before but have another bit of info and I'm hoping it > >> rings a bell for someone so that I don't have to through the painful > >> process of printk() instrumenting the kernel and flashing new kernels > >> with more and more debug. > >> > >> Anyway, my command line is: > >> > >> # kexec -l /vmlinux-2.6.25.20 --append="root=/dev/sda1 rootfstype=ext3 > >> noinitrd console=ttyS0,115200 init=/etc/preinit" > > > > That's a valid command line. > > > >> where /vmlinux-2.6.25.20 is build_dir/linux-brcm47xx/vmlinux.elf from my > >> build tree. > >> > >> kexec -l returns: > >> > >> kexec_load failed: Success result = 89 > >> entry = 0x29f000 flags = 0 > >> nr_segments = 2 > >> segment[0].buf = 0x2ac33008 > >> segment[0].bufsz = 27a07a > >> segment[0].mem = 0x1000 > >> segment[0].memsz = 29e000 > >> segment[1].buf = 0x458440 > >> segment[1].bufsz = 194 > >> segment[1].mem = 0x29f000 > >> segment[1].memsz = 1000 > > > > It seems to me like the entry is not valid here, it should be around > > 0x80010000 or so, but I need to check whether the entry reported here is > > the entry point i the ELF header. > > > >> and "result", 89 is what is returned from kexec_load() in my_load() in > >> the kexec-tools package. I dug a bit but could not really find anything > >> in sys_kexec_load() or it's callees that would return "89", > >> > >> > >> > >> Anyone with any ideas at all? > >> > >> Anyone actually using kexec on a mips architecture with success, just so > >> I know I am not chasing a pipe-dream? > > > > I have been using kexec successfully on rb532 w/ 2.6.24, and apart that > > it did mangle the serial console ouput, the kexec'd kernel booted fine, > > but that was prior to upgrading to kexec-tools-2.0.0. I will give it a > > try and report back here. > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > openwrt-devel mailing list > > openwrt-devel@lists.openwrt.org > > http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel > > _______________________________________________ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel -- Best regards, Florian Fainelli Email : flor...@openwrt.org http://openwrt.org -------------------------------
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
