[meta-ti] Stumped. Can't get 2.6.37 TI kernel to boot when built with toolchain from denzil or Linaro gcc-linaro-arm-linux-gnueabihf-4.8-2013.07-1_linux/

Khem Raj raj.khem at gmail.com
Fri Aug 16 14:33:03 PDT 2013


On Fri, Aug 16, 2013 at 1:58 PM, Brian Hutchinson <b.hutchman at gmail.com>wrote:

> On Fri, Aug 16, 2013 at 11:37 AM, Khem Raj <raj.khem at gmail.com> wrote:
>
>>
>> On Fri, Aug 16, 2013 at 8:12 AM, Brian Hutchinson <b.hutchman at gmail.com>wrote:
>>
>>>  At this point I'm using the toolchains outside of OE (meta-toolchain
>>> from denzil branch and Linaro 4.8) to make life a bit simpler.
>>
>>
>>
>> ​can you use the the toolchain from OE-Core and see if it happens with
>> that too ?​
>>
>>
> OK, that kept me busy for a while.  I built core-image-minimal -c
> populate_sdk with OE Core + meta-ti and installed that on my application
> development machine
>


good. So as I understand now you have a compiler from OE-Core
​​

>
> CPU: 0    Not tainted  (2.6.37+ #1)
> PC is at strcmp+0x10/0x48
> LR is at omap_mbox_get+0x40/0x1cc
> pc : [<c01dcd94>]    lr : [<c0061a50>]    psr: a0000013
> sp : ca023f10  ip : ca023f20  fp : ca023f1c
> r10: ca022018  r9 : 00000000  r8 : c04a20c0
> r7 : c049c5c8  r6 : c04a2798  r5 : c0408919  r4 : c047d898
> r3 : 00000000  r2 : 00000064  r1 : c0408919  r0 : 0000004c
> Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
> Control: 10c5387d  Table: 80004019  DAC: 00000017
> Process swapper (pid: 1, stack limit = 0xca0222e8)
> Stack: (0xca023f10 to 0xca024000)
> 3f00:                                     ca023f44 ca023f20 c0061a50
> c01dcd90
> 3f20: c02b67c0 c01dcd90 c049c4a0 c049c56c c049c4a0 c0024ec8 ca023f6c
> ca023f48
> 3f40: c02b9fe4 c0061a1c 00000001 00000000 c002b040 c002b040 c04d1f08
> c006a954
> 3f60: ca023f94 ca023f70 c0024f04 c02b9e70 c002b040 c002b0d0 c006a954
> c0024ec8
> 3f80: c04a20c0 00000000 ca023fd4 ca023f98 c00373b8 c0024ed4 00000036
> 00000000
> 3fa0: ca023fbc 00000196 c04896cc c002b040 c002b0d0 c006a954 00000013
> 00000000
> 3fc0: 00000000 00000000 ca023ff4 ca023fd8 c0008d68 c003730c 00000000
> 00000000
> 3fe0: 00000000 c0008cc0 00000000 ca023ff8 c006a954 c0008ccc eda485b5
> b186e796
> Backtrace:
> [<c01dcd84>] (strcmp+0x0/0x48) from [<c0061a50>] (omap_mbox_get+0x40/0x1cc)
> [<c0061a10>] (omap_mbox_get+0x0/0x1cc) from [<c02b9fe4>]
> (notify_shm_drv_setup+0x180/0x254)
>  r7:c0024ec8 r6:c049c4a0 r5:c049c56c r4:c049c4a0
> [<c02b9e64>] (notify_shm_drv_setup+0x0/0x254) from [<c0024f04>]
> (notify_init+0x3c/0x2a8)
>  r6:c006a954 r5:c04d1f08 r4:c002b040
> [<c0024ec8>] (notify_init+0x0/0x2a8) from [<c00373b8>]
> (do_one_initcall+0xb8/0x180)
>  r9:00000000 r8:c04a20c0 r7:c0024ec8 r6:c006a954 r5:c002b0d0
> r4:c002b040
> [<c0037300>] (do_one_initcall+0x0/0x180) from [<c0008d68>]
> (kernel_init+0xa8/0x150)
> [<c0008cc0>] (kernel_init+0x0/0x150) from [<c006a954>] (do_exit+0x0/0x5dc)
>  r5:c0008cc0 r4:00000000
> Code: e1a0c00d e92dd800 e24cb004 e3a03000 (e7d02003)
> ---[ end trace 599d30e660dbf8fa ]---
> Kernel panic - not syncing: Attempted to kill init!
> Backtrace:
> [<c0044aec>] (dump_backtrace+0x0/0x104) from [<c0351cf0>]
> (dump_stack+0x18/0x1c)
>  r6:c01dcd96 r5:0000000b r4:c04a2858 r3:ffffffff
> [<c0351cd8>] (dump_stack+0x0/0x1c) from [<c0351ee0>] (panic+0x60/0x178)
> [<c0351e80>] (panic+0x0/0x178) from [<c006a9c0>] (do_exit+0x6c/0x5dc)
>  r3:c0480894 r2:ca020130 r1:00000001 r0:c040ad52
>  r7:ca022000
> [<c006a954>] (do_exit+0x0/0x5dc) from [<c0044f58>] (die+0x280/0x2bc)
>  r7:ca022000
> [<c0044cd8>] (die+0x0/0x2bc) from [<c0351d50>]
> (__do_kernel_fault.part.4+0x5c/0x7c)
> [<c0351cf4>] (__do_kernel_fault.part.4+0x0/0x7c) from [<c035862c>]
> (do_page_fault+0x200/0x21c)
>  r7:ca020000 r3:ca023ec8
> [<c035842c>] (do_page_fault+0x0/0x21c) from [<c035866c>]
> (do_translation_fault+0x24/0xa4)
> [<c0358648>] (do_translation_fault+0x0/0xa4) from [<c00371f8>]
> (do_DataAbort+0x3c/0xa0)
>  r7:ca023ec8 r6:0000004c r5:c046a550 r4:00000005
> [<c00371bc>] (do_DataAbort+0x0/0xa0) from [<c035672c>]
> (__dabt_svc+0x4c/0x60)
> Exception stack(0xca023ec8 to 0xca023f10)
> 3ec0:                   0000004c c0408919 00000064 00000000 c047d898
> c0408919
> 3ee0: c04a2798 c049c5c8 c04a20c0 00000000 ca022018 ca023f1c ca023f20
> ca023f10
> 3f00: c0061a50 c01dcd94 a0000013 ffffffff
>  r7:c049c5c8 r6:c04a2798 r5:ca023efc r4:ffffffff
> [<c01dcd84>] (strcmp+0x0/0x48) from [<c0061a50>] (omap_mbox_get+0x40/0x1cc)
> [<c0061a10>] (omap_mbox_get+0x0/0x1cc) from [<c02b9fe4>]
> (notify_shm_drv_setup+0x180/0x254)
>  r7:c0024ec8 r6:c049c4a0 r5:c049c56c r4:c049c4a0
> [<c02b9e64>] (notify_shm_drv_setup+0x0/0x254) from [<c0024f04>]
> (notify_init+0x3c/0x2a8)
>  r6:c006a954 r5:c04d1f08 r4:c002b040
> [<c0024ec8>] (notify_init+0x0/0x2a8) from [<c00373b8>]
> (do_one_initcall+0xb8/0x180)
>  r9:00000000 r8:c04a20c0 r7:c0024ec8 r6:c006a954 r5:c002b0d0
> r4:c002b040
> [<c0037300>] (do_one_initcall+0x0/0x180) from [<c0008d68>]
> (kernel_init+0xa8/0x150)
> [<c0008cc0>] (kernel_init+0x0/0x150) from [<c006a954>] (do_exit+0x0/0x5dc)
>  r5:c0008cc0 r4:00000000
>

​This needs to be debugged. Since 3.x kernels works fine with gcc 4.8.x, I
would assume its something that got fixed in kernel along the way. You have
to hunt
I dont have neither the platform nor another device where I use 2.6.37 so
cant help much with hunt




>
> To build the above, I simple sourced the
> /usr/local/oecore-i686/environment-setup-armv7a-vfp-neon-oe-linux-gnueabi
> script and then unset LDFLAGS.
>
> For kicks, I did a clean build of the kernel again and built with make
> EXTRA_CFLAGS=-mno-unaligned-access uImage and that resulted in a hung
> kernel:
>
> ## Booting kernel from Legacy Image at 83000000 ...
>    Image Name:   Linux-2.6.37+
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    2348876 Bytes = 2.2 MiB
>    Load Address: 80008000
>    Entry Point:  80008000
>    Verifying Checksum ... OK
>    Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
>
> Regards,
>
> Brian
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-ti/attachments/20130816/178eef26/attachment.html>


More information about the meta-ti mailing list