Re: kernel init exception
Hi, David, Segher, Maybe it was caused by floating exception.I found that,system received a program check exception,the reason for it was REASON_ILLEGAL. I also use show_regs to print the NIP in exception,it seemed that ,this exception was caused by 'vmhaddshs' instruction in user mode of init process . Is vmhaddshs avaliable on e500mc? My cross compile tool is gcc-4.1.2-glibc-2.5.0 ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: kernel init exception
Maybe it was caused by floating exception.I found that,system received a program check exception,the reason for it was REASON_ILLEGAL. I also use show_regs to print the NIP in exception,it seemed that ,this exception was caused by 'vmhaddshs' instruction in user mode of init process . Is vmhaddshs avaliable on e500mc? My cross compile tool is gcc-4.1.2-glibc-2.5.0 This isn't vmhaddshs (which is an AltiVec instruction), but something else that also uses primary opcode 4. It sounds like your toolchain isn't set up correctly for e500mc. Segher ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: kernel init exception
2010/7/1 Segher Boessenkool seg...@kernel.crashing.org: Maybe it was caused by floating exception.I found that,system received a program check exception,the reason for it was REASON_ILLEGAL. I also use show_regs to print the NIP in exception,it seemed that ,this exception was caused by 'vmhaddshs' instruction in user mode of init process . Is vmhaddshs avaliable on e500mc? My cross compile tool is gcc-4.1.2-glibc-2.5.0 This isn't vmhaddshs (which is an AltiVec instruction), but something else that also uses primary opcode 4. It sounds like your toolchain isn't set up correctly for e500mc. Segher I 've used cross_tool (powerpc_mc) that freescale provided, to compile the kernel image, and use an ordinary powerpc cross tool to compile busybox into cpio ramdisk. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
kernel init exception
We are porting linux 2.6.21.7 to a powerpc e500mc board , p4080. But something is wrong when loading init file: log: free init memory... init has generated signal 4 but has no handler for it I found it print in _exception --- if (is_init(current)) { if (handler == SIG_DFL) { printk(KERN_CRIT init has generated signal %d but has no handler for it\n, signr); do_exit(signr); } } why there generated a signal 4 in init process? Thanks ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: kernel init exception
why there generated a signal 4 in init process? That's SIGILL; sounds like you compiled init with the wrong (sub-)arch or cpu flags. Segher ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: kernel init exception
On Tue, Jun 29, 2010 at 06:51:16PM +0200, Segher Boessenkool wrote: why there generated a signal 4 in init process? That's SIGILL; sounds like you compiled init with the wrong (sub-)arch or cpu flags. Or it's been corrupted during load. -- David Gibson| I'll have my music baroque, and my code david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_ | _way_ _around_! http://www.ozlabs.org/~dgibson ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev