Skip to contentSkip to conversation

Poky & armv5te

DISCUSSION Gary Thomas 4 participants 9 messages Feb 2, 2011 – Feb 3, 2011

lore
Share & tools
lore
#0 lore raw

I'd like to use Poky with my OMAP-L138 which is armv5te Sadly today, this just isn't a go because of GCC issues. I've tried all the combinations which are in the trees (main & contrib) with no luck:
* 4.3.3 - fails to build GCC
* 4.5.1 - everything builds but kernel crashes
* 4.5.2 - fails to build GCC

Am I totally out of luck?

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#1 lore raw
Quoted 9 lines · Gary Thomas

I'd like to use Poky with my OMAP-L138 which is armv5te Sadly today, this just isn't a go because of GCC issues. I've tried all the combinations which are in the trees (main & contrib) with no luck:
* 4.3.3 - fails to build GCC
* 4.5.1 - everything builds but kernel crashes
* 4.5.2 - fails to build GCC

Am I totally out of luck?

What are you running into? I've recently backported some changes in support of the Beagleboard (armv7-a) which were necessary to build with 4.5.1 and our 2.21 binutils.

Signature · 3 lines
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
#2 lore raw
Quoted 9 lines · Darren Hart
Quoted 8 lines · Gary Thomas

I'd like to use Poky with my OMAP-L138 which is armv5te Sadly today, this just isn't a go because of GCC issues. I've tried all the combinations which are in the trees (main & contrib) with no luck:
* 4.3.3 - fails to build GCC
* 4.5.1 - everything builds but kernel crashes
* 4.5.2 - fails to build GCC

Quoted 3 lines
Quoted 1 line

Am I totally out of luck?

What are you running into? I've recently backported some changes in support of the Beagleboard (armv7-a) which were necessary to build with 4.5.1 and our 2.21 binutils.

As far as 4.5.1 goes, the kernel crashes immediately on bootup. I didn't diagnose this much as it seemed to be similar to the problem reported 2011-01-31 18:52GMT
'Kernel Panics on armv4t with gcc.4.5.1'
To that end, I tried to use the 4.5.2 patches from Nitin which failed to build at all (reported this morning)

Do you have a tree with your changes? I could try my armv5te overlay to see what happens.

Thanks

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#3 lore raw
In reply to Darren Hart
Quoted 9 lines · Darren Hart
Quoted 8 lines · Gary Thomas

I'd like to use Poky with my OMAP-L138 which is armv5te Sadly today, this just isn't a go because of GCC issues. I've tried all the combinations which are in the trees (main & contrib) with no luck:
* 4.3.3 - fails to build GCC
* 4.5.1 - everything builds but kernel crashes
* 4.5.2 - fails to build GCC

Quoted 5 lines
Quoted 1 line

Am I totally out of luck?

What are you running into? I've recently backported some changes in support of the Beagleboard (armv7-a) which were necessary to build with 4.5.1 and our 2.21 binutils.

Those wouldn't affect armv5. What puzzles me is that qemuarm is effectively an armv5 like system and those do build and boot in qemu.

When you managed images above for 4.5.1 did you try using a known good kernel with our userspace? I'm wondering if we can narrow it to a kernel issue?

Cheers,

Richard

#4 lore raw
Quoted 16 lines · Richard Purdie
Quoted 9 lines · Darren Hart
Quoted 8 lines · Gary Thomas

I'd like to use Poky with my OMAP-L138 which is armv5te Sadly today, this just isn't a go because of GCC issues. I've tried all the combinations which are in the trees (main& contrib) with no luck:
* 4.3.3 - fails to build GCC
* 4.5.1 - everything builds but kernel crashes
* 4.5.2 - fails to build GCC

Quoted 5 lines
Quoted 1 line

Am I totally out of luck?

What are you running into? I've recently backported some changes in support of the Beagleboard (armv7-a) which were necessary to build with 4.5.1 and our 2.21 binutils.

Quoted 6 lines

Those wouldn't affect armv5. What puzzles me is that qemuarm is effectively an armv5 like system and those do build and boot in qemu.

When you managed images above for 4.5.1 did you try using a known good kernel with our userspace? I'm wondering if we can narrow it to a kernel issue?

Not sure I got that far, but I'll check it out.

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#5 lore raw
Quoted 17 lines · Gary Thomas
Quoted 16 lines · Richard Purdie
Quoted 14 lines · Darren Hart
Quoted 9 lines · Gary Thomas

I'd like to use Poky with my OMAP-L138 which is armv5te Sadly today, this just isn't a go because of GCC issues. I've tried all the combinations which are in the trees (main& contrib) with no luck:
* 4.3.3 - fails to build GCC
* 4.5.1 - everything builds but kernel crashes
* 4.5.2 - fails to build GCC

Am I totally out of luck?

What are you running into? I've recently backported some changes in support of the Beagleboard (armv7-a) which were necessary to build with 4.5.1 and our 2.21 binutils.

Quoted 8 lines
Quoted 6 lines

Those wouldn't affect armv5. What puzzles me is that qemuarm is effectively an armv5 like system and those do build and boot in qemu.

When you managed images above for 4.5.1 did you try using a known good kernel with our userspace? I'm wondering if we can narrow it to a kernel issue?

Not sure I got that far, but I'll check it out.

A simple test indicates that the user-space tools built in Poky do run fine on this hardware when built with GCC/4.5.1 and BINUTILS/2.21 It's only the kernel that crashes hard with this combo.

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#6 lore raw
Quoted 25 lines · Gary Thomas
Quoted 24 lines · Gary Thomas
Quoted 22 lines · Richard Purdie
Quoted 9 lines · Darren Hart
Quoted 8 lines · Gary Thomas

I'd like to use Poky with my OMAP-L138 which is armv5te Sadly today, this just isn't a go because of GCC issues. I've tried all the combinations which are in the trees (main& contrib) with no luck:
* 4.3.3 - fails to build GCC
* 4.5.1 - everything builds but kernel crashes
* 4.5.2 - fails to build GCC

Quoted 5 lines
Quoted 1 line

Am I totally out of luck?

What are you running into? I've recently backported some changes in support of the Beagleboard (armv7-a) which were necessary to build with 4.5.1 and our 2.21 binutils.

Those wouldn't affect armv5. What puzzles me is that qemuarm is effectively an armv5 like system and those do build and boot in qemu.

When you managed images above for 4.5.1 did you try using a known good kernel with our userspace? I'm wondering if we can narrow it to a kernel issue?

Quoted 5 lines
Quoted 1 line

Not sure I got that far, but I'll check it out.

A simple test indicates that the user-space tools built in Poky do run fine on this hardware when built with GCC/4.5.1 and BINUTILS/2.21 It's only the kernel that crashes hard with this combo.

Ok, thats positive in many ways :)

When you say the kernel crashes hard can you be any more specific about where in the process its doing that? Any chance its using -Os anywhere in the kernel build and that is causing the problem?

Cheers,

Richard

#7 lore raw
Quoted 32 lines · Richard Purdie
Quoted 25 lines · Gary Thomas
Quoted 24 lines · Gary Thomas
Quoted 22 lines · Richard Purdie
Quoted 9 lines · Darren Hart
Quoted 8 lines · Gary Thomas

I'd like to use Poky with my OMAP-L138 which is armv5te Sadly today, this just isn't a go because of GCC issues. I've tried all the combinations which are in the trees (main& contrib) with no luck:
* 4.3.3 - fails to build GCC
* 4.5.1 - everything builds but kernel crashes
* 4.5.2 - fails to build GCC

Quoted 5 lines
Quoted 1 line

Am I totally out of luck?

What are you running into? I've recently backported some changes in support of the Beagleboard (armv7-a) which were necessary to build with 4.5.1 and our 2.21 binutils.

Those wouldn't affect armv5. What puzzles me is that qemuarm is effectively an armv5 like system and those do build and boot in qemu.

When you managed images above for 4.5.1 did you try using a known good kernel with our userspace? I'm wondering if we can narrow it to a kernel issue?

Quoted 5 lines
Quoted 1 line

Not sure I got that far, but I'll check it out.

A simple test indicates that the user-space tools built in Poky do run fine on this hardware when built with GCC/4.5.1 and BINUTILS/2.21 It's only the kernel that crashes hard with this combo.

Quoted 5 lines

Ok, thats positive in many ways :)

When you say the kernel crashes hard can you be any more specific about where in the process its doing that? Any chance its using -Os anywhere in the kernel build and that is causing the problem?

For ARM .. it definitely is using Os. Unless gcc 4.5.1 has some changes in this area, ARM builds require Os, as they have for a while (see below).

Typically if you build an ARM kernel without Os you get indeterminate errors (in the network stack, scheduler optimizations, etc). At least in kernels 2.6.34 and older this is true, I've shared in the marathon debug sessions to prove it :) In fact, we explicitly force on the CC_OPTIMIZE_FOR_SIZE in our configuration of th ARM kernels to make sure this doesn't creep back in.

A quick check shows that out of ~170 ARM defconfigs 151 turn on CONFIG_CC_OPTIMIZE_FOR_SIZE, and the ones with it off are typically older ones.

I just doubled checked qemuarm, and it also turns on CC_OPTIMIZE_FOR_SIZE (which it was supposed to do). I started a build for it and will do a boot to see what happens shortly.

Maybe this has changed recently (I haven't had to have a deeper look in 2.6.37 (yet)), so I am happy to be corrected :)

Cheers,

Bruce

Quoted 13 lines

Cheers,

Richard

_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

#8 lore raw
Quoted 55 lines · Bruce Ashfield
Quoted 32 lines · Richard Purdie
Quoted 25 lines · Gary Thomas
Quoted 24 lines · Gary Thomas
Quoted 22 lines · Richard Purdie
Quoted 9 lines · Darren Hart
Quoted 8 lines · Gary Thomas

I'd like to use Poky with my OMAP-L138 which is armv5te Sadly today, this just isn't a go because of GCC issues. I've tried all the combinations which are in the trees (main& contrib) with no luck:
* 4.3.3 - fails to build GCC
* 4.5.1 - everything builds but kernel crashes
* 4.5.2 - fails to build GCC

Quoted 5 lines
Quoted 1 line

Am I totally out of luck?

What are you running into? I've recently backported some changes in support of the Beagleboard (armv7-a) which were necessary to build with 4.5.1 and our 2.21 binutils.

Those wouldn't affect armv5. What puzzles me is that qemuarm is effectively an armv5 like system and those do build and boot in qemu.

When you managed images above for 4.5.1 did you try using a known good kernel with our userspace? I'm wondering if we can narrow it to a kernel issue?

Quoted 5 lines
Quoted 1 line

Not sure I got that far, but I'll check it out.

A simple test indicates that the user-space tools built in Poky do run fine on this hardware when built with GCC/4.5.1 and BINUTILS/2.21 It's only the kernel that crashes hard with this combo.

Quoted 5 lines

Ok, thats positive in many ways :)

When you say the kernel crashes hard can you be any more specific about where in the process its doing that? Any chance its using -Os anywhere in the kernel build and that is causing the problem?

For ARM .. it definitely is using Os. Unless gcc 4.5.1 has some changes in this area, ARM builds require Os, as they have for a while (see below).

Typically if you build an ARM kernel without Os you get indeterminate errors (in the network stack, scheduler optimizations, etc). At least in kernels 2.6.34 and older this is true, I've shared in the marathon debug sessions to prove it :) In fact, we explicitly force on the CC_OPTIMIZE_FOR_SIZE in our configuration of th ARM kernels to make sure this doesn't creep back in.

A quick check shows that out of ~170 ARM defconfigs 151 turn on CONFIG_CC_OPTIMIZE_FOR_SIZE, and the ones with it off are typically older ones.

Quoted 7 lines

I just doubled checked qemuarm, and it also turns on CC_OPTIMIZE_FOR_SIZE (which it was supposed to do). I started a build for it and will do a boot to see what happens shortly.

Maybe this has changed recently (I haven't had to have a deeper look in 2.6.37 (yet)), so I am happy to be corrected :)

The kernel I'm using is 2.6.32 and it does have CONFIG_CC_OPTIMIZE_FOR_SIZE=y

I should be able to investigate what's crashing shortly .

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------