Hello, i'm porting Montavista linux 2.6.24.3 to our board which is based on Amd alchemy mips processor. I'm using U-boot as boot loader and Eldk 4.1 by Denx, which contains also busybox 1.3.0, for development. Linux boots well until it gets to starting of init process. After sys_execve function is completed (with no error), process, called init, invokes fpu emulator eight times with no error. After that is program moving in scheduller code and any assembler code, which is used to clearing memmory bits. Then linux randomly crashes with "not syncing - attemted to kill init" message. This happens no matter if i try to boot from nfs or from ramdisk. I used ramdisk, which is part of eldk package and ramdisk which i created using bussybox in combination with Eldk libraries, but result was almost the same. The difference was only in some libraries, which are loaded by linker, i think. I got the same results with NFS. I can not post you messages, which writes linux during boot, because my console also doesn't work yet. I didn't even try to make console work much, because i can read printk messages from log_buf variable, when i debug linux using kgdb. I also compiled hello world application, i found at bussybox internet page, with Eldk compiler, changed it to elf format with cross compile objcopy and renamed it to init, but kernel gave me no init found message. Right now, i'm quite clueless, because my knowledges ot this problematics are quie poor. Could someone give me any hint, or idea, where the problem could probably be? Are there any differences in constitution of filesystem between ramdisk and filesystem accessed through NFS?
Thanks, Martin. _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
