Suspicious warnings while beta testing yocto 1.2

Suspicious warnings while beta testing yocto 1.2

[Andrea Galbusera]

While beta testing yocto 1.2 I'm building for beagleboard with:

OE Build Configuration:
BB_VERSION        = "1.15.1"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "beagleboard"
DISTRO            = "poky"
DISTRO_VERSION    = "1.1+snapshot-20120330"
TUNE_FEATURES     = "armv7a vfp neon cortexa8"
TARGET_FPU        = "vfp-neon"
meta
meta-yocto        = "<unknown>:<unknown>"

I see warnings complaining that some options set by the BSP are not
valid for the kernel being built. This is the first time I noticed and
it's confusing me. After some search I find a past conversation where
it was suggested that warnings like this for a Yocto maintained BSP
should be considered bugs. Can anyone explain this? Build is
completing successfully. Not yet tested the kernel on actual hardware.
Later I will see if something similar also happens in edison not.

Here is the log:

This BSP sets 15 invalid/obsolete kernel options.
These config options are not offered anywhere within this kernel.
The full list can be found in your workspace at:
/home/gizero/Documents/research/yocto-1.2-beta/yp-beta-build/tmp/work/beagleboard-poky-linux-gnueabi/linux-yocto-3.0.23+git1+e559129b4a6f39f68b75141096b2d516cf7a7f35_1+fccd4e4041454f16f1e7a25569ec530eaa1bf89e-r4/linux/meta/cfg/yocto/standard/beagleboard/invalid.cfg

This BSP sets 50 kernel options that are possibly non-hardware related.
The full list can be found in your workspace at:
/home/gizero/Documents/research/yocto-1.2-beta/yp-beta-build/tmp/work/beagleboard-poky-linux-gnueabi/linux-yocto-3.0.23+git1+e559129b4a6f39f68b75141096b2d516cf7a7f35_1+fccd4e4041454f16f1e7a25569ec530eaa1bf89e-r4/linux/meta/cfg/yocto/standard/beagleboard/specified_non_hdw.cfg

WARNING: There were 12 hardware options requested that do not
         have a corresponding value present in the final ".config" file.
         This probably means you aren't getting the config you wanted.
The full list can be found in your workspace at:
/home/gizero/Documents/research/yocto-1.2-beta/yp-beta-build/tmp/work/beagleboard-poky-linux-gnueabi/linux-yocto-3.0.23+git1+e559129b4a6f39f68b75141096b2d516cf7a7f35_1+fccd4e4041454f16f1e7a25569ec530eaa1bf89e-r4/linux/meta/cfg/yocto/standard/beagleboard/mismatch.cfg

Waiting a second to make sure you get a chance to see this...

If useful I can provide the list of options as per given log files.

Re: Suspicious warnings while beta testing yocto 1.2

[Bruce Ashfield]

On 12-03-30 01:18 PM, Andrea Galbusera wrote:
> While beta testing yocto 1.2 I'm building for beagleboard with:
>
> OE Build Configuration:
> BB_VERSION        = "1.15.1"
> TARGET_ARCH       = "arm"
> TARGET_OS         = "linux-gnueabi"
> MACHINE           = "beagleboard"
> DISTRO            = "poky"
> DISTRO_VERSION    = "1.1+snapshot-20120330"
> TUNE_FEATURES     = "armv7a vfp neon cortexa8"
> TARGET_FPU        = "vfp-neon"
> meta
> meta-yocto        = "<unknown>:<unknown>"
>
> I see warnings complaining that some options set by the BSP are not
> valid for the kernel being built. This is the first time I noticed and
> it's confusing me. After some search I find a past conversation where
> it was suggested that warnings like this for a Yocto maintained BSP
> should be considered bugs. Can anyone explain this? Build is
> completing successfully. Not yet tested the kernel on actual hardware.
> Later I will see if something similar also happens in edison not.

There are a few outstanding items for 1.2 as part of M4 .. one of
them is squashing the remaining configuration values that are
causing warnings.

Cheers,

Bruce

>
> Here is the log:
>
> This BSP sets 15 invalid/obsolete kernel options.
> These config options are not offered anywhere within this kernel.
> The full list can be found in your workspace at:
> /home/gizero/Documents/research/yocto-1.2-beta/yp-beta-build/tmp/work/beagleboard-poky-linux-gnueabi/linux-yocto-3.0.23+git1+e559129b4a6f39f68b75141096b2d516cf7a7f35_1+fccd4e4041454f16f1e7a25569ec530eaa1bf89e-r4/linux/meta/cfg/yocto/standard/beagleboard/invalid.cfg
>
> This BSP sets 50 kernel options that are possibly non-hardware related.
> The full list can be found in your workspace at:
> /home/gizero/Documents/research/yocto-1.2-beta/yp-beta-build/tmp/work/beagleboard-poky-linux-gnueabi/linux-yocto-3.0.23+git1+e559129b4a6f39f68b75141096b2d516cf7a7f35_1+fccd4e4041454f16f1e7a25569ec530eaa1bf89e-r4/linux/meta/cfg/yocto/standard/beagleboard/specified_non_hdw.cfg
>
> WARNING: There were 12 hardware options requested that do not
>           have a corresponding value present in the final ".config" file.
>           This probably means you aren't getting the config you wanted.
> The full list can be found in your workspace at:
> /home/gizero/Documents/research/yocto-1.2-beta/yp-beta-build/tmp/work/beagleboard-poky-linux-gnueabi/linux-yocto-3.0.23+git1+e559129b4a6f39f68b75141096b2d516cf7a7f35_1+fccd4e4041454f16f1e7a25569ec530eaa1bf89e-r4/linux/meta/cfg/yocto/standard/beagleboard/mismatch.cfg
>
> Waiting a second to make sure you get a chance to see this...
>
> If useful I can provide the list of options as per given log files.
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Re: Suspicious warnings while beta testing yocto 1.2

[Bob Cochran]

On 03/30/2012 01:20 PM, Bruce Ashfield wrote:
> There are a few outstanding items for 1.2 as part of M4 .. one of
> them is squashing the remaining configuration values that are
> causing warnings.

I'm also seeing some kernel config errors for the MPC8315 while beta 
testing.  Should I ignore or pursue?

BTW, when I'm not beta testing, I work from the mainline and my own config.

Re: Suspicious warnings while beta testing yocto 1.2

[Bruce Ashfield]

On Fri, Mar 30, 2012 at 1:27 PM, Bob Cochran <yocto@mindchasers.com> wrote:
> On 03/30/2012 01:20 PM, Bruce Ashfield wrote:
>>
>> There are a few outstanding items for 1.2 as part of M4 .. one of
>> them is squashing the remaining configuration values that are
>> causing warnings.
>
>
> I'm also seeing some kernel config errors for the MPC8315 while beta
> testing.  Should I ignore or pursue?

ignore for now, all the configs will be audited, so we already have a work item
to cover it.

Bruce

>
> BTW, when I'm not beta testing, I work from the mainline and my own config.



>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Re: Suspicious warnings while beta testing yocto 1.2

[Andrea Galbusera]

Bruce,

On Fri, Mar 30, 2012 at 7:20 PM, Bruce Ashfield
<bruce.ashfield@windriver.com> wrote:
> On 12-03-30 01:18 PM, Andrea Galbusera wrote:
>>
>> While beta testing yocto 1.2 I'm building for beagleboard with:
>>
>> OE Build Configuration:
>> BB_VERSION        = "1.15.1"
>> TARGET_ARCH       = "arm"
>> TARGET_OS         = "linux-gnueabi"
>> MACHINE           = "beagleboard"
>> DISTRO            = "poky"
>> DISTRO_VERSION    = "1.1+snapshot-20120330"
>> TUNE_FEATURES     = "armv7a vfp neon cortexa8"
>> TARGET_FPU        = "vfp-neon"
>> meta
>> meta-yocto        = "<unknown>:<unknown>"
>>
>> I see warnings complaining that some options set by the BSP are not
>> valid for the kernel being built. This is the first time I noticed and
>> it's confusing me. After some search I find a past conversation where
>> it was suggested that warnings like this for a Yocto maintained BSP
>> should be considered bugs. Can anyone explain this? Build is
>> completing successfully. Not yet tested the kernel on actual hardware.
>> Later I will see if something similar also happens in edison not.
>
>
> There are a few outstanding items for 1.2 as part of M4 .. one of
> them is squashing the remaining configuration values that are
> causing warnings.

Ok, thanks! Ignoring for now...


> Cheers,
>
> Bruce
>
>>
>> Here is the log:
>>
>> This BSP sets 15 invalid/obsolete kernel options.
>> These config options are not offered anywhere within this kernel.
>> The full list can be found in your workspace at:
>>
>> /home/gizero/Documents/research/yocto-1.2-beta/yp-beta-build/tmp/work/beagleboard-poky-linux-gnueabi/linux-yocto-3.0.23+git1+e559129b4a6f39f68b75141096b2d516cf7a7f35_1+fccd4e4041454f16f1e7a25569ec530eaa1bf89e-r4/linux/meta/cfg/yocto/standard/beagleboard/invalid.cfg
>>
>> This BSP sets 50 kernel options that are possibly non-hardware related.
>> The full list can be found in your workspace at:
>>
>> /home/gizero/Documents/research/yocto-1.2-beta/yp-beta-build/tmp/work/beagleboard-poky-linux-gnueabi/linux-yocto-3.0.23+git1+e559129b4a6f39f68b75141096b2d516cf7a7f35_1+fccd4e4041454f16f1e7a25569ec530eaa1bf89e-r4/linux/meta/cfg/yocto/standard/beagleboard/specified_non_hdw.cfg
>>
>> WARNING: There were 12 hardware options requested that do not
>>          have a corresponding value present in the final ".config" file.
>>          This probably means you aren't getting the config you wanted.
>> The full list can be found in your workspace at:
>>
>> /home/gizero/Documents/research/yocto-1.2-beta/yp-beta-build/tmp/work/beagleboard-poky-linux-gnueabi/linux-yocto-3.0.23+git1+e559129b4a6f39f68b75141096b2d516cf7a7f35_1+fccd4e4041454f16f1e7a25569ec530eaa1bf89e-r4/linux/meta/cfg/yocto/standard/beagleboard/mismatch.cfg
>>
>> Waiting a second to make sure you get a chance to see this...
>>
>> If useful I can provide the list of options as per given log files.
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>