[Regression] X crash on Yocto startup with BSP 3.5.7-1.0.0

[DiegoFSL]

Hi i.MX community,

I'd like to advise that although with latest BSP 3.5.7-1.0.0 Yocto has gained support for hardfloat, it "somehow" lost support for softfloat.

It's not that's really lost; but there's a severe regression in X support: there's an X crash on startup (which does not happen on hardfloat variant).

Here's full Xorg.0.log:

http://pastebin.com/U8TEcZiA

Did anybody else test X11 on a Yocto BSP 3.5.7-1.0.0 softfloat build?

Bye,

Diego

[OtavioSalvador]

This has been fixed in master branch of Yocto BSP and will be available in 1.5 release.

[EricNelson]

Hi Diego,

How are you disabling hard-float?

It appears that the DEFAULTTUNE settings are un-conditional:

~/yocto-3.5.7/sources$ for f in meta-fsl-* ; do grep -r DEFAULTTUNE $f/* ; done
meta-fsl-bsp-release/imx/README:DEFAULTTUNE_mx6 = "cortexa9hf-neon
meta-fsl-bsp-release/imx/meta-fsl-arm/conf/machine/include/fsl-mx6-common.inc:DEFAULTTUNE_mx6 = "cortexa9hf-neon"
meta-fsl-bsp-release/imx/meta-fsl-arm/conf/layer.conf:DEFAULTTUNE_mx6 = "cortexa9hf-neon"

I think those DEFAULTTUNE_mx6 = "cortexa9hf-neon" statements should use ?=.

[DiegoFSL]

Hi Eric,

I think you're using meta-fsl-* from Freescale, but I suggest you to use traditional Yocto ones, and switch to master-next for meta-fsl-arm, meta-fsl-arm-extra and meta-fsl-demos.

Then you'll have:

$ for f in meta-fsl-* ; do grep -r DEFAULTTUNE $f/* ; done
meta-fsl-arm/conf/machine/include/imx-base.inc:DEFAULTTUNE_mx6 ?= "cortexa9hf-neon"

Then setting DEFAULTTUNE in local.conf should work:

http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/commit/?h=master-next&id=970a07a4d56b521cfffe...

Bests,

Diego

[EricNelson]

Thanks Diego,

You're absolutely right, and I'll try the Yocto versions.

[LeonardoSandova]

Diego,

which image/machine are you building?

(FYI LaurenPost / EnriqueOchoaVazquez)

[DiegoFSL]

I'm building fsl-image-gui for machine Nitrogen6x.

See also bug report:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=4946

[LaurenPost]

I tried this on imx6qsabresd and have no issues.   Right before release we did have problems with disabling hwfp correctly but it was enabled in the final update.

Also I've seen multiple times that switching between hwfp and swfp can corrupt build states.  I always keep these completely separate builds both with cache and tmp directories.