Hi, On Fri Jul 03, 2015 at 14:42:35 +0200, Mahdi Aichouch wrote: > However, there is still a problem after the mount of the root filesystem as > shown below. > > Do you have an idea of what might be wrong.
This tells us that the 'sh' is doing something wrong or triggers something that makes it crash due to a signal. Which ramdisk is this? One of mine? On the current one the pc location has just a register move, so likely not the one. The PC value is always the same of consecutive tries? Could you send me the /bin/sh of the ramdisk you're using (private mail). Adam > RAMDISK: ext2 filesystem found at block 0 > RAMDISK: Loading 3072KiB [1 disk] into ram disk... done. > EXT4-fs (ram0): couldn't mount as ext3 due to feature incompatibilities > EXT4-fs (ram0): mounting ext2 file system using the ext4 subsystem > EXT4-fs (ram0): mounted filesystem without journal. Opts: (null) > VFS: Mounted root (ext2 filesystem) readonly on device 1:0. > Freeing unused kernel memory: 116K (02312000 - 0232f000) > potentially unexpected fatal signal 4. > > CPU: 0 PID: 1 Comm: sh Not tainted 3.16.0-l4 #3 > task: 05c23ac0 ti: 05c26000 task.ti: 05c26000 > PC is at 0xc4c0 > LR is at 0x0 > pc : [<0000c4c0>] lr : [<00000000>] psr: 00000010 > sp : bfa42ef0 ip : 00000000 fp : 00000000 > r10: 00000000 r9 : 00000000 r8 : 00000000 > r7 : 00000000 r6 : 00000000 r5 : 00000000 r4 : 00000000 > r3 : 00000000 r2 : 00000000 r1 : 00000000 r0 : 00000000 > vcpu: b3000c00 vcpu-state: 00000001 > Flags: nzcv IRQs on FIQs on Mode USER_32 ISA ARM Segment user > CPU: 0 PID: 1 Comm: sh Not tainted 3.16.0-l4 #3 > [<02000>] (unwind_backtrace) from [<02005924>] (show_stack+0x10/0x14) > [<02005924>] (show_stack) from [<02028c50>] > (get_signal_to_deliver+0x240/0x4cc) > [<02028c50>] (get_signal_to_deliver) from [<02006fb4>] > (do_signal+0x118/0x464) > [<02006fb4>] (do_signal) from [<020073a0>] (do_work_pending+0xa0/0xe8) > [<020073a0>] (do_work_pending) from [<02008d50>] > (l4x_pre_iret_work.isra.31.part.32+0x60/0x104) > [<02008d50>] (l4x_pre_iret_work.isra.31.part.32) from [<02009e38>] > (l4x_vcpu_entry_c+0x274/0x1ddc) > [<02009e38>] (l4x_vcpu_entry_c) from [<00000000>] ( (null)) > Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 > > CPU: 0 PID: 1 Comm: sh Not tainted 3.16.0-l4 #3 > [<02000>] (unwind_backtrace) from [<02005924>] (show_stack+0x10/0x14) > [<02005924>] (show_stack) from [<022486c0>] (panic+0x8c/0x1dc) > [<022486c0>] (panic) from [<0201e0b0>] (complete_and_exit+0x0/0x1c) > [<0201e0b0>] (complete_and_exit) from [<00000001>] (0x1) > ---[ end Kernel panic - not syncing: Attempted to kill init! > exitcode=0x00000004 > > panic: going to sleep forever, bye > panic: going to sleep forever, bye -- Adam a...@os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/ _______________________________________________ l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
