Bug 945 - kernel config validation task displays misleading warnings
Summary: kernel config validation task displays misleading warnings
Status: RESOLVED FIXED
Alias: None
Product: Kernel
Classification: Yocto Project Subprojects
Component: kernel-configuration (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.1
Assignee: Bruce Ashfield
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-03-31 20:49 UTC by Tom Zanussi
Modified: 2011-04-04 08:37 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Zanussi 2011-03-31 20:49:14 UTC
The kernel config validation warnings seem wrong in some cases, and in other cases, the warnings seem to point to the BSP itself having a problem, whereas in reality the problem is in the base configs and needs to be cleaned up there, and it would be better to point the user to the actual source if possible instead.

For example:

NOTE: package linux-yocto-2.6.37+git1+e2cabadc059ad8d91f7e4a023106620d93abd23a_1+2b412826bbeb4a16abe2ea74f2456ab880c6e3c1-r17: task do_kernel_configcheck: Started
NOTE: validating kernel configuration
The following Kconfig files no longer exist in this tree:
      drivers/ieee1394/Kconfig
      drivers/media/video/zc0301/Kconfig

This BSP sets 1 invalid/obsolete kernel options.
These config options are not offered anywhere within this kernel.
The full list can be found in your workspace at:
/usr/local/src/yocto/sbtest/build/tmp/work/sugarbay-poky-linux/linux-yocto-2.6.37+git1+e2cabadc059ad8d91f7e4a023106620d93abd23a_1+2b412826bbeb4a16abe2ea74f2456ab880c6e3c1-r17/linux/meta/cfg/yocto/standard/common-pc-64/sugarbay/invalid.cfg

This BSP sets 24 kernel options that are possibly non-hardware related.
The full list can be found in your workspace at:
/usr/local/src/yocto/sbtest/build/tmp/work/sugarbay-poky-linux/linux-yocto-2.6.37+git1+e2cabadc059ad8d91f7e4a023106620d93abd23a_1+2b412826bbeb4a16abe2ea74f2456ab880c6e3c1-r17/linux/meta/cfg/yocto/standard/common-pc-64/sugarbay/specified_non_hdw.cfg

WARNING: There were 103 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:
/usr/local/src/yocto/sbtest/build/tmp/work/sugarbay-poky-linux/linux-yocto-2.6.37+git1+e2cabadc059ad8d91f7e4a023106620d93abd23a_1+2b412826bbeb4a16abe2ea74f2456ab880c6e3c1-r17/linux/meta/cfg/yocto/standard/common-pc-64/sugarbay/mismatch.cfg

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




For the last message, the '103 hardware options' are all of the form:

Value requested for CONFIG_ACPI not in final ".config"
Requested value: ""
Actual value set: "CONFIG_ACPI=y"

which makes it seem as though CONFIG_ACPI was requested to be valueless rather than y/n/m, so any setting of these config options triggers a warning.


The '24 kernel options that are possibly non-hardware related' include such things as:

CONFIG_DRM_I915
CONFIG_DRM_I915_KMS
CONFIG_NETDEVICES
CONFIG_SND_HDA_INTEL

which are hardware-related.  For example, the I915 options come from the i915 feature, which is defined in i915.scc using 'kconf hardware', so should be identified as hardware-related.

The other messages relate to obsolete stuff in base branches, and not the BSP per se e.g.:

The following Kconfig files no longer exist in this tree:
      drivers/ieee1394/Kconfig
      drivers/media/video/zc0301/Kconfig

CONFIG_KGDB_8250

The ieee1394 and zc0301 Kfonfig files are referenced in kernel-cache/ktypes/wrs_base/hardware.kcf, and not in the BSP itself.  Similarly, the CONFIG_KGDB_8250 config item comes from kernel-cache/bsp/common-pc-64/common-pc-64.cfg; while the warning does indicate things that need to be removed for this kernel, it needs to be done in the base configs and not the BSP per se.
Comment 1 Bruce Ashfield 2011-03-31 21:26:29 UTC
We've already got an item on the 1.1 schedule for all the cleanup. But we can keep
this around for now.