Fwd: Running L4Linux + Fiasco on Freescale i.MX 6 Sabre SD

Adam Lackorzynski adam at os.inf.tu-dresden.de
Thu Jun 25 22:36:18 CEST 2015

On Fri Jun 12, 2015 at 16:37:51 +0200, Mahdi Aichouch wrote:
> 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:

Ok good.

> 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.
> 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)

The Linux is crashing before the virtual serial inside Linux is set up,
that's why we do not see anything. What typically helps is early-printk.
Thus, make sure to enable CONFIG_EARLY_PRINTK in the L4Linux config and
to put earlyprintk=1 on the Linux command line. That should hopefully
show more and also the reason for the error.

Adam                 adam at os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/

More information about the l4-hackers mailing list