Hello, every l4-hacker.
I've succeeded booting "Hello world + L4/Fiasco" on Freescale i.MX6q_sabre_sd because big help of Admed, Tim, Matthias.
And then, I'm trying to boot "L4 Linux + L4/Fiasco" on my board.
I've configured for L4 linux build. Such as..
|System type -> ARM system type (L4 Linux) Build type (Use ARMv7) |
And then, I've successfully build it.
I've did "make uimage E='L4Linux ARM' ..." ,so I've got uimage. And I try to boot it ,using 'uImage' and 'u-boot.bin'.
But I did not boot it on my board. It was stoped at "l4linux | panic: going to sleep forever, bye"
==================== ... (eclipsis) Trying to unpack rootfs image as initramfs... rootfs image is not initramfs (junk in compressed archive); looks like an initrd INITRD: Freeing memory. l4x: Checks passed. NetWinder Floating Point Emulator V0.97 (double precision) msgmni has been set to 126 io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) L4 serial driver ttyLv0 at MMIO 0x1 (irq = 211, base_baud = 230400) is a L4 l4ser_shm: L4 shared mem serial driver l4cdds: No name given, not starting. brd: module loaded l4bdds: No name given, not starting. mousedev: PS/2 mouse device common for all mice TCP: cubic registered NET: Registered protocol family 17 Minicom2.6.2RAMDISK: 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: 112K (022ea000 - 02306000) Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
CPU: 0 PID: 1 Comm: sh Not tainted 3.13.0-l4-svn46 #1 [<0200b6ec>] (unwind_backtrace+0x0/0xf8) from [<02005308>] (show_stack+0x10/0x14) [<02005308>] (show_stack+0x10/0x14) from [<0222a17c>] (panic+0x78/0x1c0) [<0222a17c>] (panic+0x78/0x1c0) from [<02017d28>] (do_exit+0x724/0x7cc) [<02017d28>] (do_exit+0x724/0x7cc) from [<02017ea0>] (do_group_exit+0x40/0xa0) [<02017ea0>] (do_group_exit+0x40/0xa0) from [<02021754>] (get_signal_to_deliver+0x1a4/0x474) [<02021754>] (get_signal_to_deliver+0x1a4/0x474) from [<02006738>] (do_signal+0x78/0x3d4) [<02006738>] (do_signal+0x78/0x3d4) from [<02006b08>] (do_work_pending+0x74/0xcc) [<02006b08>] (do_work_pending+0x74/0xcc) from [<02009cf4>] (l4x_vcpu_entry_c+0x18ec/0x1e3c) [<02009cf4>] (l4x_vcpu_entry_c+0x18ec/0x1e3c) from [<00094e9c>] (0x94e9c) panic: going to sleep forever, bye l4linux | panic: going to sleep forever, bye
====================
I guess that the problem is somthing about ramdisk(root file system) and kernel command line might be wrong.
Referentially I've used ramdisk file(ramdisk-arm.rd) and my kernel command line "setenv bootargs_mmc 'setenv bootargs ${bootargs} root=/dev/mmcblk1p1 rootwait rw video=mxcfb1:dev=ldb,LDB-XGA,if=RGB666 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24'".
How do you think about that?
Is wrong my kernel command line,on this situation ?
- Taeung -