Re: Solution of the previous thread "Running L4Linux + Fiasco on Freescale i.MX 6 Sabre SD"

Hello Adam,
Thanks for your reply and I'm sorry for the ambiguity of my description. In
fact, I have followed that thread and have solved many problems until the
 last step. (
http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007551.html). You
guessed that it was the problem of the ramdisk, which I downloaded at
http://os.inf.tu-dresden.de/download/ramdisk-arm.rd  . After that, you and
Mahdi no longer posted messages in this mailing list at this subject. So, I
want to know how you address this problem.

The output of the execution now appears like this:

>* 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*


Thanks a lot for your help!

Regards,
Le Guan


Date: Fri, 14 Aug 2015 00:00:09 +0200
> From: Adam Lackorzynski <[email protected]>
> To: [email protected]
> Subject: Re: Solution of the previous thread "Running L4Linux + Fiasco
>         on Freescale i.MX 6 Sabre SD"
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset=iso-8859-1
>
> On Thu Aug 13, 2015 at 10:43:33 -0400, Le Guan wrote:
> > Hi l4-hackers,
> >
> > Greetings! I encountered exactly the same problem as Mahdi's. His
> original
> > thread can be found at
> > http://os.inf.tu-dresden.de/pipermail/l4-hackers/2015/007491.html.
> > AS Mahdi and Adam communicated using private email later, I don't know if
> > the problem has been solved. If it has been solved, can anybody give me
> > some hint on it?
>
> When 'swp' is trapping then it's not enabled in the CPU. You can do so by
> enabling it in Fiasco's config.
> Alternative: Why is 'swp' used at all on an ARMv7 architecture as the
> imx6? Did you compile L4Linux for ARMv7?
>
>
>
> Adam
> --
> Adam                 [email protected]
>   Lackorzynski         http://os.inf.tu-dresden.de/~adam/
>

_______________________________________________
l4-hackers mailing list
[email protected]
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers