Bug 3473

Summary:	atom-pc kernel fails to build
Product:	[Build System, Metadata & Runtime] OE-Core	Reporter:	Ross Burton <ross.burton>
Component:	kernel	Assignee:	Bruce Ashfield <bruce.ashfield>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Undecided	CC:	bruce.ashfield, tom.zanussi
Version:	1.4
Target Milestone:	---
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	Regression (Used to work)
Verified:		Documentation change:	---

Description Ross Burton 2012-11-21 11:54:35 UTC

ERROR: Function failed: do_kernel_configme (see /data/poky-master/tmp/work/atom_pc-poky-linux/linux-yocto/3.0.32+git1+bf5ee4945ee6d748e6abe16356f2357f76b5e2f0_1+834c2a69c87ee7211932f8ec5102a472828abcb1-r4.1/temp/log.do_kernel_configme.18243 for further information)
ERROR: Logfile of failure stored in: /data/poky-master/tmp/work/atom_pc-poky-linux/linux-yocto/3.0.32+git1+bf5ee4945ee6d748e6abe16356f2357f76b5e2f0_1+834c2a69c87ee7211932f8ec5102a472828abcb1-r4.1/temp/log.do_kernel_configme.18243
Log data follows:
| DEBUG: Executing shell function do_kernel_configme
| [INFO] doing kernel configme
| [INFO] Configuring target/machine combo: "standard/atom-pc"
| [INFO] collecting configs in ./meta/meta-series
| ERROR: could not sanitize configuration fragments
|    errors are logged in /data/poky-master/tmp/work/atom_pc-poky-linux/linux-yocto/3.0.32+git1+bf5ee4945ee6d748e6abe16356f2357f76b5e2f0_1+834c2a69c87ee7211932f8ec5102a472828abcb1-r4.1/linux/meta/cfg/standard/atom-pc/config.log

$ cat /data/poky-master/tmp/work/atom_pc-poky-linux/linux-yocto/3.0.32+git1+bf5ee4945ee6d748e6abe16356f2357f76b5e2f0_1+834c2a69c87ee7211932f8ec5102a472828abcb1-r4.1/linux/meta/cfg/standard/atom-pc/config.log
[INFO] Sanitizing meta/cfg/kernel-cache/ktypes/base/base.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/ktypes/standard/standard.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/features/kgdb/kgdb.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/features/lttng/lttng.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/features/blktrace/blktrace.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/features/systemtap/systemtap.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/features/utrace/utrace.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/features/hrt/hrt.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/features/ftrace/ftrace.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/features/cgroups/cgroups.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/features/namespaces/namespaces.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/features/namespaces/namespaces-experimental.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/features/fuse/fuse.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/cfg/devtmpfs.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/features/debugfs/debugfs.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/bsp/common-pc/common-pc.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/bsp/common-pc/common-pc-gfx.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/cfg/boot-live.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/features/intel-e1xxxx/intel-e100.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/features/intel-e1xxxx/intel-e1xxxx.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/features/latencytop/latencytop.cfg
[INFO] Sanitizing meta/cfg/kernel-cache/features/profiling/profiling.cfg
[INFO] Sanitizing meta/cfg
[ERROR] Kern frag meta/cfg does not exist

Comment 1 Ross Burton 2012-11-21 11:55:37 UTC

This worked on Monday 19th poky, but fails with Wednesday 21st.

Comment 2 Bruce Ashfield 2012-11-21 13:32:29 UTC

I'll grab this. Could be the new tools update.

Comment 3 Bruce Ashfield 2012-11-21 13:34:25 UTC

The error message is correct. There's a typo in the virtio configuration fragments. Fixing it locally
and re-testing.

Comment 4 Bruce Ashfield 2012-11-21 14:01:31 UTC

out of curiosity .. the atom-pc should probably not be preferring the 3.0 kernel. There's a 
typo in the meta data that was fixed for other kernel versions, but not for 3.0. I'll fix it there,
but atom-pc should not be using that kernel by default. I nearly missed the error because
I was checking the wrong kernel version.

Comment 5 Bruce Ashfield 2012-11-21 14:13:41 UTC

As well as fixing the meta-data, I've tweaked the tools to have this output when a similar
error is encountered:

 [ERROR] kernel configuration fragment fragment 'virto.cfg' cannot be found

You'll note the obvious typo in virtio ...

Comment 6 Bruce Ashfield 2012-11-22 17:41:00 UTC

Fix merged to oe-core master:

commit 37c752ab05842a70bca0727af14709e0a9720425
Author: Bruce Ashfield <bruce.ashfield@windriver.com>
Date:   Wed Nov 21 16:32:26 2012 -0500

    kern-tools: report missing config fragments by name
    
    If a configuration fragment was missing, the previous error output
    was not clear about the error:
    
      | [INFO] doing kernel configme
      | [INFO] Configuring target/machine combo: "standard/atom-pc"
      | [INFO] collecting configs in ./meta/meta-series
      | ERROR: could not sanitize configuration fragments
      |    errors are logged in ... linux/meta/cfg/standard/atom-pc/config.log
    
    but we know the name of the missing fragment and can improve the error
    message to be this:
    
      | [ERROR] kernel configuration fragment fragment 'virto.cfg' cannot be found
      | ERROR. A meta series could not be created for branch yocto/standard/common-pc/atom-pc
      | ERROR. Could not locate meta series for atom-pc
      | ERROR. Could not apply patches for atom-pc.
      |        Patch failures can be resolved in the devshell (bitbake -c devshell linux-yocto)
    
    [YOCTO #3473]
    
    (From OE-Core rev: 46cc0d0a2f1486bf541c1a1b11075de3da396cc2)
    
    Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
    Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>