Hello Adam,
I added the earlyprintk=1 option to linux boot command and I enabled the CONFIG_EARLY_PRINTK.
The debug messages below show more information compared to logs from the previous tests.
Could you please tell me what do you think might be the cause of the error.
Many thanks in advance.
Best regards, Mahdi
DBG : L4 Bootstrapper Build: #24 Thu Jul 2 14:03:57 CEST 2015, 4.8.3 20140320 (prerelease) Scanning up to 256 MB RAM, starting at offset 32MB DBG : lre/bootstrap/plaform_common : Memory size is 256MB (10000000 - 1fffffff) RAM: 0000000010000000 - 000000001fffffff: 262144kB Total RAM: 256MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 10 modules behind 11100000 moving module 02 { 118c3000-118fc63f } -> { 119b3000-119ec63f } [235072] moving module 01 { 118b9000-118c238b } -> { 119a9000-119b238b } [37772] moving module 00 { 11850000-118b868b } -> { 11940000-119a868b } [427660] moving module 09 { 11550000-1184ffff } -> { 11640000-1193ffff } [3145728] moving module 08 { 111de000-1154f497 } -> { 112ce000-1163f497 } [3609752] moving module 07 { 111dd000-111dd0bc } -> { 112cd000-112cd0bc } [189] moving module 06 { 11086000-111dc46f } -> { 11176000-112cc46f } [1401968] moving module 05 { 11085000-110851b4 } -> { 11175000-111751b4 } [437] moving module 04 { 11032000-11084c1f } -> { 11122000-11174c1f } [338976] moving module 03 { 11010000-11031473 } -> { 11100000-11121473 } [136308] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x10002000 Regions of list 'regions' [ 10000000, 1000015f] { 160} Root mbi_rt [ 10001000, 10001aff] { b00} Kern fiasco [ 10002000, 10076fff] { 75000} Kern fiasco [ 10090000, 1009e177] { e178} Sigma0 sigma0 [ 10140000, 10171d87] { 31d88} Root moe [ 10178000, 101934ab] { 1b4ac} Root moe [ 11000000, 1100f58f] { f590} Boot bootstrap [ 11100000, 1193ffff] { 840000} Root Module DB : Kernel command-line: fiasco -serial_esc API Version: (87) experimental Sigma0 config ip:10090100 sp:00000000 Roottask config ip:10140260 sp:00000000 Starting kernel fiasco at 100012c8 DBG: Startup::stage2:: init CPU, Memory, MMU, Timer, FPU, IPI DBG : ALLOC1: [1f000000; 1fffffff] sz=16777216 Buddy::add_mem(0xf0400000, 1000000): al_start=f0400000; _base=f0400000 Per_cpu_data_alloc: (orig: 0xf0065090-0xf0065a58) DBG Boot_alloc: size=0xc DBG Boot_alloc: size=0x8 Number of IRQs available at this GIC: 160 DBG Boot_alloc: size=0x280 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl L2: ID=410000c7 Type=9e340340 Aux=32070000 WMask=ffff S=0 L2: Type L2C-310 Size = 1024kB Ways=16 Waysize=64 GIC: Switching IRQ 9 to secure GIC: Switching IRQ 8 to secure GIC: Switching IRQ 10 to secure GIC: Switching IRQ 11 to secure GIC: Switching IRQ 58 to secure SERIAL ESC: allocated IRQ 58 for serial uart Not using serial hack in slow timer handler. kernel_main: version: Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: rexported compiled with gcc 4.8.3 for i.MX6 [] Build: #4 Tue Jun 23 11:54:30 CEST 2015
Per_cpu_data_alloc: (orig: 0xf0065090-0xf0065a58)
KERNEL: Warning: Buddy::alloc: Size mismatch: 9c8 v 1000 Allocate 2504 bytes (2KB) for CPU[9] local storage (offset=1184f70, 0xf11ea000-0xf11ea9c8) GIC: Switching IRQ 29 to secure DBG: kernel_thread : setup timer on current cpu... DBG: kernel_thread : enable tlb with current cpu... Number of CPUs: 4 DBG: kernel_thread : Calibrating timer loop... Per_cpu_data_alloc: (orig: 0xf0065090-0xf0065a58) done.
KERNEL: Warning: Buddy::alloc: Size mismatch: 9c8 v 1000 Allocate 2504 bytes (2KB) for CPU[1] local storage (offset=1186f70, 0xf11ec000-0xf11ec9c8) MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 10002000 Memory desc: start: 268435456 end: 536870911 Memory desc: start: 268435456 end: 268439551 Memory desc: start: 268439552 end: 268443647 Memory desc: start: 268443648 end: 268922879 Memory desc: start: 269025280 end: 269086719 Memory desc: start: 269746176 end: 269950975 Memory desc: start: 269975552 end: 270090239 Memory desc: start: 286261248 end: 294911999 Memory desc: start: 520093696 end: 536870911 Memory desc: start: DBG: boot_ap_cpu : create kernel thread 0FPU1: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl GIC: Switching IRQ 29 to secure enPer_cpu_data_alloc: (orig: 0xf0065090-0xf0065a58) d: KERNEL: Warning: Buddy::alloc: Size mismatch: 9c8 v 1000 4Allocate 2504 bytes (2KB) for CPU[2] local storage (offset=1164f70, 0xf11ca000-0xf11ca9c8) 095Cache config: ON
ID_PFR[01]: 00001231 00000011 ID_[DA]FR0: 00010444 00000000 MID_MMFR[04]: 00100103 20000000 01230000 00102111 emory deCPU[1]: goes to idle loop sc: start: 0 end: 4095 Memory desc: start: 0 end: 4095 Memory desc: start: 0 end: 4095 Memory desc: start: 0 end: 4095 Memory desc: start: 0 end: 4095 Memory desc: start: 0 end: 4095 Memory desc: start: 0 end: 4095 Memory desc: start: 0 end: 4095 Memory desc: start: 0 end: 4095 allocated 4KB for maintenance structures SIGMA0: Dump of all r DBG: boot_ap_cpu : create kernel thread esFPU2: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl ourcGIC: Switching IRQ 29 to secure e mCache config: ON apID_PFR[01]: 00001231 00000011sPer_cpu_data_alloc: (orig: 0xf0065090-0xf0065a58)
KERNEL: Warning: Buddy::alloc: Size mismatch: 9c8 v 1000 RAllocate 2504 bytes (2KB) for CPU[3] local storage (offset=1167f70, 0xf11cd000-0xf11cd9c8) AM:---- ID_[DA]FR0: 00010444 00000000 --ID_MMFR[04]: 00100103 20000000 01230000 00102111 -CPU[2]: goes to idle loop ----------------- [4:10000000;10000fff] [0:10077000;1008ffff] [0:1009f000;1013ffff] [4:10140000;10171fff] [0:10172000;10177fff] [4:10178000;10193fff] [0:10194000;110fffff] [4:11100000;1193ffff] [0:11940000;1effffff] IOMEM:---------------------- [0:0;fffffff] [0:20000000;ffffffff] DBG sigma0 finishes initialization, then start pager() SIGMA0: rcv: [l=-2; w=2; i=0] MOE: DBG : MOE DBG: boot_ap_cpu : create kernel thread FPU3: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl : HelloGIC: Switching IRQ 29 to secure worCache config: ON ld ID_PFR[01]: 00001231 00000011CPU[0]: run(thread=9, cpu=0 (1,0,24) ID_[DA]FR0: 00010444 00000000 ID_MMFR[04]: 00100103 20000000 01230000 00102111 CPU[3]: goes to idle loop MOE: found 236464 KByte free memory MOE: found RAM from 10000000 to 1f000000 MOE: allocated 240 KByte for the page array @0x1009f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [11100000-11121474] [C:503000] l4re BOOTFS: [11122000-11174c20] [C:504000] ned BOOTFS: [11175000-111751b5] [C:505000] l4lx.cfg BOOTFS: [11176000-112cc470] [C:506000] io BOOTFS: [112cd000-112cd0bd] [C:507000] arm-rv.io BOOTFS: [112ce000-1163f498] [C:508000] vmlinuz.arm BOOTFS: [11640000-11940000] [C:509000] ramdisk-arm.rd MOE: cmdline: moe rom/l4lx.cfg MOE: Starting: rom/ned rom/l4lx.cfg MOE: loading 'rom/ned' CPU[0]: run(thread=21, cpu=0 (1,0,24) ARGC=2 ARGV=b1007eb4 ENVP=b1007ec0 AUXP=b1007ec4 arg: 'rom/ned' arg: 'rom/l4lx.cfg' CPU[0]: run(thread=24, cpu=0 (1,0,24) CPU[0]: run(thread=21, cpu=0 (1,0,24) DBG : Hello from Ned CPU[0]: run(thread=2c, cpu=0 (1,0,24) CPU[0]: run(thread=2c, cpu=0 (1,0,24) CPU[0]: run(thread=2f, cpu=0 (1,0,24) Ned says: Hi World! Ned: loading file: 'rom/l4lx.cfg' CPU[0]: run(thread=38, cpu=0 (1,0,24) l4linux | ARGC=10 l4linux | ARGV=b1007e4c l4linux | ENVP=b1007e78 l4linux | AUXP=b1007e7c l4linux | arg: 'rom/vmlinuz.arm' l4linux | arg: 'earlyprintk=1' l4linux | arg: 'mem=64M' l4linux | arg: 'console=ttyLv0' l4linux | arg: 'l4x_rd=rom/ramdisk-arm.rd' l4linux | arg: 'root=1:0' l4linux | arg: 'ramdisk_size=4000' l4linux | arg: 'ip=dhcp' l4linux | arg: 'init=/bin/sh' l4linux | arg: 'print-fatal-signals=1' CPU[0]: run(thread=3b, cpu=0 (1,0,24) CPU[0]: run(thread=38, cpu=0 (1,0,24) l4linux | libio: Warning: Query of 'vbus' failed! l4linux | PH 0 (t: 1) offs=00008000 vaddr=02000000 vend=023dd0a8 l4linux | phys=02000000 ephys=023dd0a8 l4linux | f_sz=00357394 memsz=003dd0a8 flgs=rwx l4linux | PH 1 (t: 4) offs=00319174 vaddr=02311174 vend=02311198 l4linux | phys=02311174 ephys=02311198 l4linux | f_sz=00000024 memsz=00000024 flgs=r-x l4linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 l4linux | phys=00000000 ephys=00000000 l4linux | f_sz=00000000 memsz=00000000 flgs=rwx l4linux | Starting binary at 0x20002a8, argc=10 argv=0xafff4f7c *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4linux | External resolver is at 0xa8000738 l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.16.0-l4 (aichouch@aichouch-ThinkCentre-M90) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #3 Thu Jul 2 13:19:20 CEST 2015 l4linux | Binary name: rom/vmlinuz.arm l4linux | This is an AEABI build. l4linux | Linux kernel command line (9 args): earlyprintk=1 mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 ip=dhcp init=/bin/sh print-fatal-signals=1 l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 02000000 - 02400000 [4096 KiB]. l4linux | Areas: Text: 02000000 - 02330000 [3264kB] (a bit longer) l4linux | Data: 02330000 - 02352500 [137kB] l4linux | Initdata: 02312000 - 0232f614 [117kB] l4linux | BSS: 02357394 - 023dd0a8 [535kB] l4linux | Device scan: l4linux | Device scan done. l4linux | l4lx_thread_create: Created thread 413 (cpu0) (u:b3000e00, v:b3000c00, sp:02331fa4) l4linux | main thread will be 413 l4linux | l4x_register_pointer_section: addr = 02000000 size = 4055040 l4linux | section-with-init: Virt: 0x2000000 to 0x23dd0a7 [3956 KiB] l4linux | section-with-init: Phys: 0x1026b000 to 0x106480a7, [3956 KiB] CPU[0]: run(thread=41, cpu=0 (1,0,0) l4linux | Main thread running, waiting... l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 02000000 l4linux | Main memory: Virt: 0x2400000 to 0x63fffff [65536 KiB] l4linux | Main memory: Phys: 0x11a00000 to 0x159fffff, [65536 KiB] l4linux | l4x: vmalloc area: 06400000 - 0e400000 l4linux | l4x_register_pointer_section: addr = 02000000 size = 4055040 l4linux | text: Virt: 0x2000000 to 0x23dd0a7 [3956 KiB] l4linux | text: Phys: 0x1026b000 to 0x106480a7, [3956 KiB] l4linux | Booting Linux on physicl CPU 0x0 Linux version 3.16.0-l (aichouch@aichouch-ThinCentre-M90) (gcc versionm 4.8.3 20140320 (prerelease) (Sourcery CodeBenc Lite 2014.05-29) ) #3 Tu Jul 2 13:19:20 CEST 20m15 CPU: Fiasco [412fc09a]revision 10 (ARMv7), cr=0000000 CPU: PIPT / VIPT nonalasing data cache, VIPT nnaliasing instruction camche Machine: L4 Ignoring unrecognised ag 0x00000000 bootconsole [earlykdb0 enabled Memory policy: Data cahe uncached CPU: All CPU(s) starte in SVC mode. Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | INITRD: 00002000 - 0030000 RAMdisk from 00002000 to 00302000 [3072KiB] KERNEL0: alignment error at 02331eff (PC: 02248e78, SP: 02331c20, FSR: 90000841, PSR: 90) l4linux | Unable to handle kernelpaging request at virtua address 02331eff pgd = 02353000 [02331eff] *pgd=0220042(bad) Internal error: Oops: 0000841 [#1] ARM Modules linked in: CPU: 0 PID: 0 Comm: swpper Not tainted 3.16.0-4 #3 task: 0233ada0 ti: 0230000 task.ti: 02330000 PC is at pcpu_dump_allc_info+0x30/0x214 LR is at pcpu_setup_fist_chunk+0x53c/0x830 pc : [<02248e78>] l : [<0231c51c>] psr: 0000093 sp : 02331ed0 ip : 0000001 fp : 0632a000 r10: 0233923c r9 : 0632900 r8 : 063328c0 r7 : 00008000 r6 : 0632880 r5 : 06332900 r4: 00000001 r3 : 00000000 r2 : 0000001 r1 : 2d2d2d2d r0: 2d2d2d2d vcpu: b3000c00 vcpu-sate: 00000000 Flags: nzcv IRQs off FIQs on Mode SVC_32 IS ARM Segment kernel Process swapper (pid: , stack limit = 0x0233028) Stack: (0x02331ed0 to x02332000) 1ec0: 0000800 00000000 ffffffff 000m00004 1ee0: 0632a000 0231d8d 00000001 022c56b8 0000000 02331f04 0632a000 021m62550 1f00: 022d434c 022c7b2 00000001 06332840 0633200 06332880 00008000 063m328c0 1f20: 06332800 0233923 0632a000 0231c51c fffffff 02358000 06332880 000m00000 1f40: 00000000 0633290 ffffffff 02329dd0 0233900 02358000 06333900 000m00000 1f60: 00000000 0231c89 ffffffff 00000000 0235800 02312648 ffffffff 021m60058 1f80: 02332000 0000001 00000000 02329dd0 0000000 00000000 00000000 000m00000 1fa0: 00000000 0000000 00000000 00000000 0000000 00000000 00000000 000m00000 1fc0: 00000000 0000000 00000000 00000000 0000000 00000000 00000000 000m00000 1fe0: 00000000 0000000 00000000 00000000 0000000 00000000 00000000 000m00000 [<02248e78>] (pcpu_dum_alloc_info) from [<023151c>] (pcpu_setup_first_mchunk+0x53c/0x830) [<0231c51c>] (pcpu_setp_first_chunk) from [<021c890>] (setup_per_cpu_amreas+0x80/0x9c) [<0231c890>] (setup_pe_cpu_areas) from [<0231248>] (start_kernel+0x10cm/0x354) [<02312648>] (start_kenel) from [<00000000>] ( (null)) Code: e8b30003 e599c01 e58d2018 e5d33000 (e58d02f) KERNEL0: alignment error at 02331c7e (PC: 02196564, SP: 02331bd0, FSR: 90000841, PSR: 60000090) KERNEL0: alignment error at 02331c7e (PC: 02196564, SP: 02331bc8, FSR: 90000841, PSR: 60000090) KERNEL0: alignment error at 02331c7e (PC: 02196564, SP: 02331bc8, FSR: 90000841, PSR: 60000090) KERNEL0: alignment error at 02331c7e (PC: 02196564, SP: 02331bc8, FSR: 90000841, PSR: 60000090) KERNEL0: alignment error at 02331c7e (PC: 02196564, SP: 02331bc8, FSR: 90000841, PSR: 60000090) KERNEL0: alignment error at 02331c7e (PC: 02196564, SP: 02331bc8, FSR: 90000841, PSR: 60000090) KERNEL0: alignment error at 02331c7e (PC: 02196564, SP: 02331bc8, FSR: 90000841, PSR: 60000090) KERNEL0: alignment error at 02331c7e (PC: 02196564, SP: 02331bc8, FSR: 90000841, PSR: 60000090) KERNEL0: alignment error at 02331c7e (PC: 02196564, SP: 02331bc8, FSR: 90000841, PSR: 60000090) KERNEL0: alignment error at 02331c7e (PC: 02196564, SP: 02331bc8, FSR: 90000841, PSR: 60000090)
On Fri, Jun 12, 2015 at 4:37 PM, Mahdi Aichouch foxmehdi@gmail.com wrote:
Hello Adam,
I added the "print-fatal-signals=1" option to l4linux command line as you suggested.
I did a make clean and I re-started from a fresh default L4Linux configuration. On which I set the "System Type -> Build type" option equal to ARMv7 for l4linux in order to be able to enabled all the floating point related options:
CONFIG_VFP=y CONFIG_VFPv3=y CONFIG_NEON=y CONFIG_ARM_THUMB=y
Then I did a re-compiled the l4linux kernel. I get an "alignment error" when l4linux tried to load the RAMDISK as shown below.
Do you have any idea of what might be wrong or any hints to track down the issue.
Thank you very much for your help.
Best regards, Mahdi
l4linux | ARGC=9 l4linux | ARGV=b1007e64 l4linux | ENVP=b1007e8c l4linux | AUXP=b1007e90 l4linux | arg: 'rom/vmlinuz.arm' l4linux | arg: 'mem=64M' l4linux | arg: 'console=ttyLv0' l4linux | arg: 'l4x_rd=rom/ramdisk-arm.rd' l4linux | arg: 'root=1:0' l4linux | arg: 'ramdisk_size=4000' l4linux | arg: 'ip=dhcp' l4linux | arg: 'init=/bin/sh' l4linux | arg: 'print-fatal-signals=1' CPU[0]: run(thread=3b, cpu=0 (1,0,24) CPU[0]: run(thread=38, cpu=0 (1,0,24) l4linux | libio: Warning: Query of 'vbus' failed! l4linux | PH 0 (t: 1) offs=00008000 vaddr=02000000 vend=023dd0a8 l4linux | phys=02000000 ephys=023dd0a8 l4linux | f_sz=00357394 memsz=003dd0a8 flgs=rwx l4linux | PH 1 (t: 4) offs=00319140 vaddr=02311140 vend=02311164 l4linux | phys=02311140 ephys=02311164 l4linux | f_sz=00000024 memsz=00000024 flgs=r-x l4linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 l4linux | phys=00000000 ephys=00000000 l4linux | f_sz=00000000 memsz=00000000 flgs=rwx l4linux | Starting binary at 0x20002a8, argc=9 argv=0xafff4f84 *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4linux | External resolver is at 0xa8000738 l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.16.0-l4 (aichouch@aichouch-ThinkCentre-M90) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #2 Fri Jun 12 15:43:25 CEST 2015 l4linux | Binary name: rom/vmlinuz.arm l4linux | This is an AEABI build. l4linux | Linux kernel command line (8 args): mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 ip=dhcp init=/bin/sh print-fatal-signals=1 l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 02000000 - 02400000 [4096 KiB]. l4linux | Areas: Text: 02000000 - 02330000 [3264kB] (a bit longer) l4linux | Data: 02330000 - 02352500 [137kB] l4linux | Initdata: 02312000 - 0232f504 [117kB] l4linux | BSS: 02357394 - 023dd0a8 [535kB] l4linux | Device scan: l4linux | Device scan done. l4linux | l4lx_thread_create: Created thread 413 (cpu0) (u:b3000e00, v:b3000c00, sp:02331fa4) l4linux | main thread will be 413 l4linux | l4x_register_pointer_section: addr = 02000000 size = 4055040 l4linux | section-with-init: Virt: 0x2000000 to 0x23dd0a7 [3956 KiB] l4linux | section-with-init: Phys: 0x10267000 to 0x106440a7, [3956 KiB] CPU[0]: run(thread=41, cpu=0 (1,0,0) l4linux | Main thread running, waiting... l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 02000000 l4linux | Main memory: Virt: 0x2400000 to 0x63fffff [65536 KiB] l4linux | Main memory: Phys: 0x11a00000 to 0x159fffff, [65536 KiB] l4linux | l4x: vmalloc area: 06400000 - 0e400000 l4linux | l4x_register_pointer_section: addr = 02000000 size = 4055040 l4linux | text: Virt: 0x2000000 to 0x23dd0a7 [3956 KiB] l4linux | text: Phys: 0x10267000 to 0x106440a7, [3956 KiB] l4linux | Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 00002000 to 00302000 [3072KiB] KERNEL0: alignment error at 02331eff (PC: 02248d38, SP: 02331c20, FSR: 90000841, PSR: 10) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331ed0, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010) KERNEL0: alignment error at 02331c7e (PC: 02196424, SP: 02331bc8, FSR: 90000841, PSR: 60000010)
On Mon, Jun 8, 2015 at 10:43 AM, Mahdi Aichouch foxmehdi@gmail.com wrote:
Hello l4-hackers,
I found a thread [1] from 2014 with the identical issue that I have. I followed the answer and I applied the solution proposed (which worked in the case of the mentioned thread). But unfortunately did not worked in my case, I still have the same issue as indicated below.
Any help will be very appreciated.
Many thanks in advance.
best regards, Mahdi
[1] http://os.inf.tu-dresden.de/pipermail/l4-hackers/2014/006620.html
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. devtmpfs: mounted Freeing unused kernel memory: 116K (02313000 - 02330000) Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
CPU: 0 PID: 1 Comm: sh Not tainted 3.16.0-l4 #9 [<0200cdd0>] (unwind_backtrace) from [<02005864>] (show_stack+0x10/0x14) [<02005864>] (show_stack) from [<02248d30>] (panic+0x8c/0x1dc) [<02248d30>] (panic) from [<0201dfd0>] (complete_and_exit+0x0/0x1c) [<0201dfd0>] (complete_and_exit) from [<00000001>] (0x1) ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
panic: going to sleep forever, bye l4linux | panic: going to sleep forever, bye
On Fri, Jun 5, 2015 at 4:31 PM, Mahdi Aichouch foxmehdi@gmail.com wrote:
Hello,
Thank you Matthias for your answer.
I didn't put "/bin/init" as a parameter in the "l4lx.cfg" file. I used the default version of the file and the "init" parameter was not set.
I added to the config file "l4lx.cfg" the parameter "init=/bin/sh" but it gives a similar error. As shown in the debug messages below:
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. devtmpfs: mounted Freeing unused kernel memory: 116K (02313000 - 02330000) Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
CPU: 0 PID: 1 Comm: sh Not tainted 3.16.0-l4 #6 [<0200cdd0>] (unwind_backtrace) from [<02005864>] (show_stack+0x10/0x14) [<02005864>] (show_stack) from [<02248c90>] (panic+0x8c/0x1dc) [<02248c90>] (panic) from [<0201df3c>] (complete_and_exit+0x0/0x1c) [<0201df3c>] (complete_and_exit) from [<00000001>] (0x1) ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
panic: going to sleep forever, bye l4linux | panic: going to sleep forever, bye
However, I tried the same l4linux with the same ramdisk on a Qemu versatile express ARM Cortex A9, it worked fine and I get a shell prompt.
Does someone has an idea of the problem or any hints about how to track down the issue.
Many thanks in advance.
Best regards, Mahdi
On Fri, May 29, 2015 at 4:44 PM, Mahdi Aichouch foxmehdi@gmail.com wrote:
Hello Matthias,
Thank you for your help.
I enabled the CONFIG_DEVTMPFS and CONFIG_DEVTMPFS_MOUNT options as you suggested, as shown below in a piece from a .config file:
Then I get another error which I think is different from the mount of the filesystem. But it is still difficult to say what might be wrong.
Could you please tell me what should I check to track down the source of the issue.
Thanks in advance.
Best regards, Mahdi
...
# # Device Drivers #
# # Generic Driver Options # CONFIG_UEVENT_HELPER=y CONFIG_UEVENT_HELPER_PATH="" CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=y CONFIG_FIRMWARE_IN_KERNEL=y CONFIG_EXTRA_FIRMWARE="" CONFIG_FW_LOADER_USER_HELPER=y # CONFIG_DEBUG_DRIVER is not set # CONFIG_DEBUG_DEVRES is not set # CONFIG_SYS_HYPERVISOR is not set # CONFIG_GENERIC_CPU_DEVICES is not set # CONFIG_DMA_SHARED_BUFFER is not set
...
Here is the debug messages :
L4 Bootstrapper Build: #85 Fri May 29 15:43:55 CEST 2015, 4.8.3 20140320 (prerelease) Scanning up to 256 MB RAM, starting at offset 32MB Memory size is 256MB (10000000 - 1fffffff) RAM: 0000000010000000 - 000000001fffffff: 262144kB Total RAM: 256MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 10 modules behind 11100000 moving module 02 { 118a9000-118e263f } -> { 11999000-119d263f } [235072] moving module 01 { 1189f000-118a838b } -> { 1198f000-1199838b } [37772] moving module 00 { 11848000-1189e0c7 } -> { 11938000-1198e0c7 } [352456] moving module 09 { 11548000-11847fff } -> { 11638000-11937fff } [3145728] moving module 08 { 111d6000-11547497 } -> { 112c6000-11637497 } [3609752] moving module 07 { 111d5000-111d50bc } -> { 112c5000-112c50bc } [189] moving module 06 { 1107e000-111d446f } -> { 1116e000-112c446f } [1401968] moving module 05 { 1107d000-1107d17b } -> { 1116d000-1116d17b } [380] moving module 04 { 1102a000-1107cc1f } -> { 1111a000-1116cc1f } [338976] moving module 03 { 11010000-11029473 } -> { 11100000-11119473 } [103540] Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x10002000 Regions of list 'regions' [ 10000000, 1000015f] { 160} Root mbi_rt [ 10001000, 10001aff] { b00} Kern fiasco [ 10002000, 10062fff] { 61000} Kern fiasco [ 10090000, 10096edf] { 6ee0} Sigma0 sigma0 [ 10098000, 1009e177] { 6178} Sigma0 sigma0 [ 10140000, 10171d77] { 31d78} Root moe [ 10178000, 101934ab] { 1b4ac} Root moe [ 11000000, 1100f58f] { f590} Boot bootstrap [ 11100000, 11937fff] { 838000} Root Module API Version: (87) experimental Sigma0 config ip:10090100 sp:00000000 Roottask config ip:10140260 sp:00000000 Starting kernel fiasco at 100012c8 Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl L2: ID=410000c7 Type=9e340340 Aux=02070000 WMask=ffff S=0 L2: Type L2C-310 Size = 1024kB Ways=16 Waysize=64 SERIAL ESC: allocated IRQ 58 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: rexported compiled with gcc 4.8.3 for i.MX6 [] Build: #19 Fri May 29 15:43:14 CEST 2015
Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 10002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:10000000;10000fff] [0:10063000;1008ffff] [0:10097000;10097fff] [0:1009f000;1013ffff] [4:10140000;10171fff] [0:10172000;10177fff] [4:10178000;10193fff] [0:10194000;110fffff] [4:11100000;11937fff] [0:11938000;1effffff] IOMEM:---------------------- [0:0;fffffff] [0:20000000;ffffffff] MOE: Hello world MOE: found 236580 KByte free memory MOE: found RAM from 10000000 to 1f000000 MOE: allocated 240 KByte for the page array @0x1009f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [11100000-11119474] [C:503000] l4re BOOTFS: [1111a000-1116cc20] [C:504000] ned BOOTFS: [1116d000-1116d17c] [C:505000] l4lx.cfg BOOTFS: [1116e000-112c4470] [C:506000] io BOOTFS: [112c5000-112c50bd] [C:507000] arm-rv.io BOOTFS: [112c6000-11637498] [C:508000] vmlinuz.arm BOOTFS: [11638000-11938000] [C:509000] ramdisk-arm.rd MOE: cmdline: moe rom/l4lx.cfg MOE: Starting: rom/ned rom/l4lx.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx.cfg' l4linux | libio: Warning: Query of 'vbus' failed! l4linux | PH 0 (t: 1) offs=00008000 vaddr=02000000 vend=023df0a8 l4linux | phys=02000000 ephys=023df0a8 l4linux | f_sz=00359394 memsz=003df0a8 flgs=rwx l4linux | PH 1 (t: 4) offs=0031a170 vaddr=02312170 vend=02312194 l4linux | phys=02312170 ephys=02312194 l4linux | f_sz=00000024 memsz=00000024 flgs=r-x l4linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000 vend=00000000 l4linux | phys=00000000 ephys=00000000 l4linux | f_sz=00000000 memsz=00000000 flgs=rwx l4linux | Starting binary at 0x20002a8, argc=6 argv=0xafff4f8c *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4linux | External resolver is at 0xa8000738 l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.16.0-l4 (aichouch@aichouch-ThinkCentre-M90) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #4 Fri May 29 15:38:21 CEST 2015 l4linux | Binary name: rom/vmlinuz.arm l4linux | This is an AEABI build. l4linux | Linux kernel command line (5 args): mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 02000000 - 02400000 [4096 KiB]. l4linux | Areas: Text: 02000000 - 02332000 [3272kB] (a bit longer) l4linux | Data: 02332000 - 02354540 [137kB] l4linux | Initdata: 02313000 - 02330614 [117kB] l4linux | BSS: 02359394 - 023df0a8 [535kB] l4linux | Device scan: l4linux | Device scan done. l4linux | l4lx_thread_create: Created thread 413 (cpu0) (u:b3000e00, v:b3000c00, sp:02333fa4) l4linux | main thread will be 413 l4linux | l4x_register_pointer_section: addr = 02000000 size = 4063232 l4linux | section-with-init: Virt: 0x2000000 to 0x23df0a7 [3964 KiB] l4linux | section-with-init: Phys: 0x10256000 to 0x106350a7, [3964 KiB] l4linux | Main thread running, waiting... l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 02000000 l4linux | Main memory: Virt: 0x2400000 to 0x63fffff [65536 KiB] l4linux | Main memory: Phys: 0x11a00000 to 0x159fffff, [65536 KiB] l4linux | l4x: vmalloc area: 06400000 - 0e400000 l4linux | l4x_register_pointer_section: addr = 02000000 size = 4063232 l4linux | text: Virt: 0x2000000 to 0x23df0a7 [3964 KiB] l4linux | text: Phys: 0x10256000 to 0x106350a7, [3964 KiB] l4linux | Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 00002000 to 00302000 [3072KiB] l4linux | l4lx_thread_create: Created thread 418 (timer0) (u:b3000a00, v:00000000, sp:02377fa0) Booting Linux on physical CPU 0x0 Linux version 3.16.0-l4 (aichouch@aichouch-ThinkCentre-M90) (gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #4 Fri May 29 15:38:21 CEST 2015 CPU: Fiasco [412fc09a] revision 10 (ARMv7), cr=00000000 CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: L4 Ignoring unrecognised tag 0x00000000 Memory policy: Data cache uncached CPU: All CPU(s) started in SVC mode. INITRD: 00002000 - 00302000 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 17209 Kernel command line: mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 PID hash table entries: 512 (order: -1, 2048 bytes) Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 64808K/69636K available (2452K kernel code, 137K rwdata, 692K rodata, 117K init, 535K bss, 4828K reserved) Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xffc00000 - 0xffe00000 (2048 kB) vmalloc : 0x06400000 - 0x0e400000 ( 128 MB) lowmem : 0x00000000 - 0x06400000 ( 100 MB) modules : Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xffc00000 - 0xffe00000 (2048 kB) vmalloc : 0x06400000 - 0x0e400000 ( 128 MB) lowmem : 0x00000000 - 0x06400000 ( 100 MB) moNR_IRQS:220 l4timer: Using IRQ210 sched_clock: 64 bits at 1000kHz, resolution 1000ns, wraps every 2147483648000ns Console: colour dummy device 80x30 console [ttyLv0] enabled Calibrating delay loop... 1574.50 BogoMIPS (lpj=7872512) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) CPU: Testing write buffer coherency: ok Setting up static identity map for 0x224e410 - 0x224e410 devtmpfs: initialized VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations Failed to create "l4x" debugfs directory: 1 Switched to clocksource l4kipclk NET: Registered protocol family 2 TCP established hash table entries: 1024 (order: 0, 4096 bytes) TCP bind hash table entries: 1024 (order: 0, 4096 bytes) TCP: Hash tables configured (established 1024 bind 1024) TCP: reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 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) futex hash table entries: 256 (order: -1, 3072 bytes) 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 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. devtmpfs: mounted Freeing unused kernel memory: 116K (02313000 - 02330000) Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
CPU: 0 PID: 1 Comm: init Not tainted 3.16.0-l4 #4 [<0200cdd0>] (unwind_backtrace) from [<02005864>] (show_stack+0x10/0x14) [<02005864>] (show_stack) from [<02248c90>] (panic+0x8c/0x1dc) [<02248c90>] (panic) from [<0201df3c>] (complete_and_exit+0x0/0x1c) [<0201df3c>] (complete_and_exit) from [<00000001>] (0x1) ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
panic: going to sleep forever, bye l4linux | panic: going to sleep forever, bye
On Fri, May 29, 2015 at 8:57 AM, Matthias Lange < matthias.lange@kernkonzept.com> wrote:
Hi,
its just an educated guess, but I suspect that /bin/init tries to access some devices in /dev. Have you enabled devtmpfs and the devtmps automount option in L4Linux?
Matthias.
On 05/28/2015 12:49 PM, Mahdi Aichouch wrote:
Hello,
Thank you very much Mattias for you help.
Now L4Linux goes further but it stops after mounting the root
filesystem.
Do you have an idea of what might be wrong.
Thank you in advance.
Best regards, Mahdi
L4 Bootstrapper Build: #81 Thu May 28 10:36:41 CEST 2015, 4.8.3 20140320
(prerelease)
Scanning up to 256 MB RAM, starting at offset 32MB Memory size is 256MB (10000000 - 1fffffff) RAM: 0000000010000000 - 000000001fffffff: 262144kB Total RAM: 256MB Scanning fiasco Scanning sigma0 Scanning moe Moving up to 10 modules behind 11100000 moving module 02 { 118aa000-118e363f } -> { 1199a000-119d363f }
[235072]
moving module 01 { 118a0000-118a938b } -> { 11990000-1199938b }
[37772]
moving module 00 { 11848000-1189fb17 } -> { 11938000-1198fb17 }
[359192]
moving module 09 { 11548000-11847fff } -> { 11638000-11937fff }
[3145728]
moving module 08 { 111d6000-11547497 } -> { 112c6000-11637497 }
[3609752]
moving module 07 { 111d5000-111d50bc } -> { 112c5000-112c50bc }
[189]
moving module 06 { 1107e000-111d446f } -> { 1116e000-112c446f }
[1401968]
moving module 05 { 1107d000-1107d17b } -> { 1116d000-1116d17b }
[380]
moving module 04 { 1102a000-1107cc1f } -> { 1111a000-1116cc1f }
[338976]
moving module 03 { 11010000-11029473 } -> { 11100000-11119473 }
[103540]
Loading fiasco Loading sigma0 Loading moe find kernel info page... found kernel info page at 0x10002000 Regions of list 'regions' [ 10000000, 1000015f] { 160} Root mbi_rt [ 10001000, 10001aff] { b00} Kern fiasco [ 10002000, 10066fff] { 65000} Kern fiasco [ 10090000, 10096edf] { 6ee0} Sigma0 sigma0 [ 10098000, 1009e177] { 6178} Sigma0 sigma0 [ 10140000, 10171d77] { 31d78} Root moe [ 10178000, 101934ab] { 1b4ac} Root moe [ 11000000, 1100f58f] { f590} Boot bootstrap [ 11100000, 11937fff] { 838000} Root Module API Version: (87) experimental Sigma0 config ip:10090100 sp:00000000 Roottask config ip:10140260 sp:00000000 Starting kernel fiasco at 100012c8 Number of IRQs available at this GIC: 160 FPU0: Arch: VFPv3(3), Part: VFPv3(30), r: 4, v: 9, i: 41, t: hard, p: dbl/sngl L2: ID=410000c7 Type=9e340340 Aux=02070000 WMask=ffff S=0 L2: Type L2C-310 Size = 1024kB Ways=16 Waysize=64 GIC: Switching IRQ 58 to secure SERIAL ESC: allocated IRQ 58 for serial uart Not using serial hack in slow timer handler. Welcome to Fiasco.OC (arm)! L4/Fiasco.OC arm microkernel (C) 1998-2013 TU Dresden Rev: rexported compiled with gcc 4.8.3 for i.MX6 [] Build: #15 Thu May 28 10:35:21 CEST 2015
GIC: Switching IRQ 29 to secure Calibrating timer loop... done. MDB: use page size: 20 MDB: use page size: 12 SIGMA0: Hello! KIP @ 10002000 allocated 4KB for maintenance structures SIGMA0: Dump of all resource maps RAM:------------------------ [4:10000000;10000fff] [0:10067000;1008ffff] [0:10097000;10097fff] [0:1009f000;1013ffff] [4:10140000;10171fff] [0:10172000;10177fff] [4:10178000;10193fff] [0:10194000;110fffff] [4:11100000;11937fff] [0:11938000;1effffff] IOMEM:---------------------- [0:0;fffffff] [0:20000000;ffffffff] MOE: Hello world MOE: found 236564 KByte free memory MOE: found RAM from 10000000 to 1f000000 MOE: allocated 240 KByte for the page array @0x1009f000 MOE: virtual user address space [0-bfffffff] MOE: rom name space cap -> [C:501000] BOOTFS: [11100000-11119474] [C:503000] l4re BOOTFS: [1111a000-1116cc20] [C:504000] ned BOOTFS: [1116d000-1116d17c] [C:505000] l4lx.cfg BOOTFS: [1116e000-112c4470] [C:506000] io BOOTFS: [112c5000-112c50bd] [C:507000] arm-rv.io <http://arm-rv.io
BOOTFS: [112c6000-11637498] [C:508000] vmlinuz.arm BOOTFS: [11638000-11938000] [C:509000] ramdisk-arm.rd MOE: cmdline: moe rom/l4lx.cfg MOE: Starting: rom/ned rom/l4lx.cfg MOE: loading 'rom/ned' Ned says: Hi World! Ned: loading file: 'rom/l4lx.cfg' l4linux | libio: Warning: Query of 'vbus' failed! l4linux | PH 0 (t: 1) offs=00008000 vaddr=02000000
vend=023defa8
l4linux | phys=02000000 ephys=023defa8 l4linux | f_sz=00359394 memsz=003defa8 flgs=rwx l4linux | PH 1 (t: 4) offs=0031afe0 vaddr=02312fe0
vend=02313004
l4linux | phys=02312fe0 ephys=02313004 l4linux | f_sz=00000024 memsz=00000024 flgs=r-x l4linux | PH 2 (t: 1685382481) offs=00000000 vaddr=00000000
vend=00000000
l4linux | phys=00000000 ephys=00000000 l4linux | f_sz=00000000 memsz=00000000 flgs=rwx l4linux | Starting binary at 0x20002b0, argc=6 argv=0xafff4f8c *argv=0xb1007ff0 argv0=rom/vmlinuz.arm l4linux | External resolver is at 0xa8000788 l4linux | ======> L4Linux starting... <======== l4linux | Linux version 3.16.0-l4 (aichouch@aichouch-ThinkCentre-M90
)
(gcc version 4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #1 Wed May 27 18:04:14 CEST 2015 l4linux | Binary name: rom/vmlinuz.arm l4linux | This is an AEABI build. l4linux | Linux kernel command line (5 args): mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 l4linux | CPU mapping (l:p)[1]: 0:0 l4linux | Image: 02000000 - 02400000 [4096 KiB]. l4linux | Areas: Text: 02000000 - 02332000 [3272kB] (a bit
longer)
l4linux | Data: 02332000 - 023543a0 [136kB] l4linux | Initdata: 02314000 - 02331024 [116kB] l4linux | BSS: 02359394 - 023defa8 [535kB] l4linux | Device scan: l4linux | Device scan done. l4linux | l4lx_thread_create: Created thread 413 (cpu0) (u:b3000e00, v:b3000c00, sp:02333fa4) l4linux | main thread will be 413 l4linux | l4x_register_pointer_section: addr = 02000000 size =
4059136
l4linux | section-with-init: Virt: 0x2000000 to 0x23defa7 [3963 KiB] l4linux | section-with-init: Phys: 0x1025a000 to 0x10638fa7, [3963
KiB]
l4linux | Main thread running, waiting... l4linux | L4x: Memory size: 64MB l4linux | L4x: Setting superpages for main memory l4linux | L4x: Adjusted memory start: 02000000 l4linux | Main memory: Virt: 0x2400000 to 0x63fffff [65536 KiB] l4linux | Main memory: Phys: 0x11a00000 to 0x159fffff, [65536
KiB]
l4linux | l4x: vmalloc area: 06400000 - 0e400000 l4linux | l4x_register_pointer_section: addr = 02000000 size =
4059136
l4linux | text: Virt: 0x2000000 to 0x23defa7 [3963 KiB] l4linux | text: Phys: 0x1025a000 to 0x10638fa7, [3963 KiB] l4linux | Loading: rom/ramdisk-arm.rd l4linux | INITRD: Size of RAMdisk is 3072KiB l4linux | RAMdisk from 00002000 to 00302000 [3072KiB] l4linux | l4lx_thread_create: Created thread 418 (timer0)
(u:b3000a00,
v:00000000, sp:02377fa0) Booting Linux on physical CPU 0x0 Linux version 3.16.0-l4 (aichouch@aichouch-ThinkCentre-M90) (gcc
version
4.8.3 20140320 (prerelease) (Sourcery CodeBench Lite 2014.05-29) ) #1 Wed May 27 18:04:14 CEST 2015 CPU: Fiasco [412fc09a] revision 10 (ARMv7), cr=00000000 CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing
instruction cache
Machine: L4 Ignoring unrecognised tag 0x00000000 Memory policy: Data cache uncached INITRD: 00002000 - 00302000 Built 1 zonelists in Zone order, mobility grouping on. Total pages:
17209
Kernel command line: mem=64M console=ttyLv0 l4x_rd=rom/ramdisk-arm.rd root=1:0 ramdisk_size=4000 PID hash table entries: 512 (order: -1, 2048 bytes) Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 64808K/69636K available (2460K kernel code, 136K rwdata, 688K rodata, 116K init, 535K bss, 4828K reserved) Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xffc00000 - 0xffe00000 (2048 kB) vmalloc : 0x06400000 - 0x0e400000 ( 128 MB) lowmem : 0x00000000 - 0x06400000 ( 100 MB) modules : Virtual kernel memory layout: vector : 0xbffff000 - 0xc0000000 ( 4 kB) fixmap : 0xffc00000 - 0xffe00000 (2048 kB) vmalloc : 0x06400000 - 0x0e400000 ( 128 MB) lowmem : 0x00000000 - 0x06400000 ( 100 MB) moNR_IRQS:220 l4timer: Using IRQ210 sched_clock: 64 bits at 1000kHz, resolution 1000ns, wraps every 2147483648000ns Console: colour dummy device 80x30 console [ttyLv0] enabled Calibrating delay loop... 1574.50 BogoMIPS (lpj=7872512) pid_max: default: 32768 minimum: 301 Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) CPU: Testing write buffer coherency: ok Setting up static identity map for 0x22509d8 - 0x22509d8 VFP support v0.3: implementor 41 architecture 3 part 30 variant 9
rev 4
NET: Registered protocol family 16 DMA: preallocated 256 KiB pool for atomic coherent allocations Failed to create "l4x" debugfs directory: 1 Switched to clocksource l4kipclk NET: Registered protocol family 2 TCP established hash table entries: 1024 (order: 0, 4096 bytes) TCP bind hash table entries: 1024 (order: 0, 4096 bytes) TCP: Hash tables configured (established 1024 bind 1024) TCP: reno registered UDP hash table entries: 256 (order: 0, 4096 bytes) UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) NET: Registered protocol family 1 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) futex hash table entries: 256 (order: -1, 3072 bytes) 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 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 (02314000 - 02331000) Kernel panic - not syncing: Attempted to kill init!
exitcode=0x0000000b
CPU: 0 PID: 1 Comm: init Not tainted 3.16.0-l4 #1 [<0200cc68>] (unwind_backtrace) from [<020057e4>]
(show_stack+0x10/0x14)
[<020057e4>] (show_stack) from [<0224ad50>] (panic+0x7c/0x1d0) [<0224ad50>] (panic) from [<0201dcdc>] (do_exit+0x7b8/0x7f0) [<0201dcdc>] (do_exit) from [<0201e858>] (do_group_exit+0x40/0xa0) [<0201e858>] (do_group_exit) from [<02028700>] (get_signal_to_deliver+0x148/0x4b4) [<02028700>] (get_signal_to_deliver) from [<02006e1c>] (do_signal+0x118/0x454) [<02006e1c>] (do_signal) from [<0200a4d4>]
(l4x_vcpu_entry_c+0xa74/0x1dd4)
[<0200a4d4>] (l4x_vcpu_entry_c) from [<0000c548>] (0xc548) ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
panic: going to sleep forever, bye l4linux | panic: going to sleep forever, bye
On Thu, May 28, 2015 at 8:23 AM, Matthias Lange <matthias.lange@kernkonzept.com <mailto:
matthias.lange@kernkonzept.com>>
wrote:
Hi, On 05/27/2015 06:43 PM, Mahdi Aichouch wrote: > Hello, > > I tried to run L4Linux + Fiasco on a Freescale i.mx <
<http://i.mx> 6 > Sabre SD board. > > The L4Linux is started but it stops at loading the ramdisk, as
shown in
> the debug messages below. > > Does someone has an idea of what might be wrong. > > Thank you very much in advance. > > Best regards, > > Mahdi > [...] > l4linux | l4x_register_pointer_section: addr = 02000000 size =
4059136
> l4linux | text: Virt: 0x2000000 to 0x23defa7 [3963
KiB]
> l4linux | text: Phys: 0x1025a000 to 0x10638fa7,
[3963 KiB]
> l4linux | Loading: rom/ramdisk-arm.rd > l4linux | INITRD: Size of RAMdisk is 3072KiB > l4linux | RAMdisk from 00002000 to 00302000 [3072KiB] > l4linux | 'swp(b)' instruction at 0224f728 and faulting. Have you enabled CONFIG_ARM_ENABLE_SWP in your Fiasco config? Matthias. -- Matthias Lange, matthias.lange@kernkonzept.com <mailto:matthias.lange@kernkonzept.com>, +49 - 351 - 41 88 86 14 <tel:%2B49%20-%20351%20-%2041%2088%2086%2014> Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB
Geschäftsführer: Dr.-Ing. Michael Hohmuth
l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
-- Matthias Lange, matthias.lange@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129. Geschäftsführer: Dr.-Ing. Michael Hohmuth