Re: Running l4android on cubieboard2

On Mon Jan 19, 2015 at 18:56:59 +0100, cem akpolat wrote:
> I encountered new failure, by the way I tested with hello word application.
> It works fine. I couldn't fine an explanation related  "sh Not tainted".
> There are of course some general definitions, but with them I cannot find
> the missing part here.

My first guess here is missing FPU support in Fiasco. How did you fix
the previous issue you had while booting Linux?

> Additionally I want to ask, the booting parameters
> in uboot and the parameters in l4lx.cfg are evaluated together or l4lx.cfg
> booting parameters ignores the uboot booting parameters.

The arguments given in uboot are not getting through to L4Linux, i.e. it
does not see them.

> Freeing unused kernel memory: 116K (02306000 - 02323000)
> Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
> 
> CPU: 0 PID: 1 Comm: sh Not tainted 3.16.0-l4-svn50 #2
> [<0200c198>] (unwind_backtrace) from [<020054e8>] (show_stack+0x10/0x14)
> [<020054e8>] (show_stack) from [<0223dbe4>] (panic+0x7c/0x1e0)
> [<0223dbe4>] (panic) from [<02018ce0>] (do_exit+0x708/0x7a0)
> [<02018ce0>] (do_exit) from [<02018e44>] (do_group_exit+0x3c/0x9c)
> [<02018e44>] (do_group_exit) from [<020229c8>]
> (get_signal_to_deliver+0x148/0x490)
> [<020229c8>] (get_signal_to_deliver) from [<02006a30>]
> (do_signal+0x114/0x448)
> [<02006a30>] (do_signal) from [<02009b14>] (l4x_vcpu_entry_c+0x934/0x1b18)
> [<02009b14>] (l4x_vcpu_entry_c) from [<000ea560>] (0xea560)
> ---[ end Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x0000000b
> 
> panic: going to sleep forever, bye
> l4linux | panic: going to sleep forever, bye



Adam
-- 
Adam                 [email protected]
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/