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" 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 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", For reference, cpuinfo is: system type : Broadcom BCM47XX processor : 0 cpu model : Broadcom BCM3302 V0.6 BogoMIPS : 263.16 wait instruction : yes microsecond timers : yes tlb_entries : 32 extra interrupt vector : yes hardware watchpoint : no ASEs implemented : shadow register sets : 1 core : 0 VCED exceptions : not available VCEI exceptions : not available 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? b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ openwrt-devel mailing list [email protected] http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
