<0>Kernel panic - not syncing: Attempted to kill init! [ 2.268655] Kernel panic - not syncing: Attempted to kill init!
That is you problem. You need to specify init in your boot flags. In configs/common/FSConfig.py it checks if the image name contains "android". If so it adds init to the boot flags: boot_flags += " init/init " Try adding "android" as part of the file name. Or just add " init/init " to be part of the boot flags always. -Tony On Mon, Aug 27, 2012 at 7:43 PM, Abhinav Kannan < abhinavkannan2...@u.northwestern.edu> wrote: > Hi, > > I am trying to run Android on Gem5 for my project and I needed help in > getting the system to run. > > I am running the gem5-stable release and am using the ARM architecture. > I have set M5_PATH to point to the gem5-stable/system directory > > Here are the different approaches I tried: > > 1. I am trying to create a custom Android image file by following the > instructions given on the website. > > I downloaded the Android source code and patched it with Arm specific > files as given in > http://www.linux-arm.org/LinuxKernel/LinuxAndroidPlatform > for kernel version 2.6.35 > > I successfully compiled the patched Android ICS source code and created an > image file using the gem5 image creation utility and transfered the Android > file system on it. I am using the pre-built kernel image given on the site. > > When I try to run the simulation I get kernel panic message and the system > does not boot: > > VFS: Mounted root (ext2 filesystem) on device 8:1. > [ 2.254005] VFS: Mounted root (ext2 filesystem) on device 8:1. > <6>Freeing init memory: 148K > [ 2.254019] Freeing init memory: 148K > /bin/sh: earlyprintk: No such file or directory > <0>Kernel panic - not syncing: Attempted to kill init! > [ 2.268655] Kernel panic - not syncing: Attempted to kill init! > [<c003899c>] (unwind_backtrace+0x0/0xe4) from [<c02f2a08>] > (panic+0x50/0xd0) > [ 2.268666] [<c003899c>] (unwind_backtrace+0x0/0xe4) from [<c02f2a08>] > (panic+0x50/0xd0) > [<c02f2a08>] (panic+0x50/0xd0) from [<c004efe4>] (do_exit+0x68/0x620) > [ 2.268679] [<c02f2a08>] (panic+0x50/0xd0) from [<c004efe4>] > (do_exit+0x68/0x620) > [<c004efe4>] (do_exit+0x68/0x620) from [<c004f640>] > (do_group_exit+0xa4/0xd4) > [ 2.268691] [<c004efe4>] (do_exit+0x68/0x620) from [<c004f640>] > (do_group_exit+0xa4/0xd4) > [<c004f640>] (do_group_exit+0xa4/0xd4) from [<c004f680>] > (sys_exit_group+0x10/0x18) > [ 2.268704] [<c004f640>] (do_group_exit+0xa4/0xd4) from [<c004f680>] > (sys_exit_group+0x10/0x18) > [<c004f680>] (sys_exit_group+0x10/0x18) from [<c00326c0>] > (ret_fast_syscall+0x0/0x30) > [ 2.268718] [<c004f680>] (sys_exit_group+0x10/0x18) from [<c00326c0>] > (ret_fast_syscall+0x0/0x30) > > Am I missing something in the build process? I compared my init.rc file > with the one from the clean ICS image file and there were no differences. > > 2. I tried to run the simulation using the pre-built images and I was able > to boot the Gingerbread bbench, gingerbread clean and Ics bbench images > using the pre-compiled kernel image. > > This does not solve the purpose as I want to use my own Android image file. > > 3. I downloaded and compiled the armdroid kernel source code and tried to > run the simulation. After compilation, I get the file "uImage" in > arch/arm/boot folder. I renamed uImage to vmlinux.arm.custom and used it in > the simulation. The simulation exits immediately with the message "Could > not load kernel file". I have placed the kernel image in > gem5-stable/system/binaries. Am I using the correct kernel image file? > > It would be really helpful if someone could point me in the correct > direction so that I can get the system to run. > Kindly let me know in case any additional information is required. > > Thanks and Regards, > Abhinav Kannan > > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
