Re: [OpenWrt-Devel] kexec failure on mips
On Sun, 2009-02-22 at 14:56 +0100, Holger Gross wrote: now the kernel loads, but does not boot: br-lan: port 1(eth0.0) entering disabled state Starting new kernel Will call new kernel at 0029d000 Bye ... Do you have a serial console on your device? I don't yet. My TTL-to-RS232 level converter arrived the other day, although I'd really rather find one of those nokia usb cables with the level adjuster built in. Anyway, sounds like you and I are having the same problems and likely seeing the kernel boot on a serial console will reveal the problem. I just need to find the time to get to it. b. 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
Re: [OpenWrt-Devel] kexec failure on mips
On Sun, 2009-02-22 at 17:17 +0100, Holger Gross wrote: i use the serial console, no other output is given. Oh, so the kernel doesn't even begin to boot? now i m trying something of http://www.nabble.com/kexec-on-mips---anyone-has-it-working--tt17485898.html#a17485898 Maybe I didn't quite follow the thread well enough but I didn't really see any solutions in there. It does seem clear that there are all sorts of avenues for failure to kexec. :-( If you do manage to make any headway, please, do post here. b. 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
Re: [OpenWrt-Devel] kexec failure on mips
Hi, i have the same problem using kexec with buffalo whr g54s openwrt rc2 kernel 2.4: 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 0x8001 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
Re: [OpenWrt-Devel] kexec failure on mips
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 0x8001 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
Re: [OpenWrt-Devel] kexec failure on mips
On Fri, 2009-02-06 at 23:45 -0500, Brian J. Murrell wrote: 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. Ah ha! Seems this was a simple case of KEXEC not being configured in the kernel configuration. Now I can load a kernel with no (apparent) problems: r...@gw:~# kexec -l /vmlinux-2.6.25.20 --append=root=/dev/mtdblock2 rootfstype=squashfs,jffs2 init=/etc/preinit noinitrd console=ttyS0,115200 but booting it doesn't seem to complete: r...@gw:~# kexec -e and it reboots, but never comes back until I power reset the unit. I guess a serial port could really help at this point. I don't have one though. I guess I should look into adding one to my wl500gp. Any ideas before/while I do though? Any debugging tips on how I can determine how far it's getting without a serial console? b. 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
Re: [OpenWrt-Devel] kexec failure on mips
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 0x8001 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. -- 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
[OpenWrt-Devel] kexec failure on mips
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 openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
