Bug 2265

Summary: [autobuilder] version field in kernel name mismatched with real version
Product: [Yocto Project Subprojects] Kernel Reporter: Yi Zhao <yi.zhao>
Component: kernel-toolingAssignee: Bruce Ashfield <bruce.ashfield>
Status: RESOLVED FIXED QA Contact:
Severity: minor    
Priority: Low CC: dexuan.cui, dvhart, elizabeth.flanagan, infras.ab.watcher, Infras.watcher, jessica.zhang, jiajun.xu, liang.li2, sgw, yp.kernel.watcher, yp.watcher
Version: 1.2   
Target Milestone: 1.2   
Hardware: x86   
OS: Multiple   
Whiteboard: pull request sent
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Yi Zhao 2012-04-09 07:36:45 UTC
For some bsp in autobuilder, the version field in the kernel name is incorrect.

For example: http://autobuilder.pokylinux.org/nightly/20120405-1/machines/mpc8315e-rdb/

The kernel name is uImage-3.0.24+git1+a4ac64fe873f08ef718e2849b88914725dc99c1c_1+7ba6d6853b6e7cf00a742baeba1503c80fc05314-r4-mpc8315e-rdb-20120405071926.bin, but it is real version is 3.0.23.
#########
root@mpc8315e-rdb:~# uname -a
Linux mpc8315e-rdb 3.0.23-yocto-standard #1 PREEMPT Thu Apr 5 02:49:46 PDT 2012 ppc GNU/Linux
#########
Comment 1 Beth Flanagan 2012-04-09 20:17:13 UTC
Not an autobuilder bug. The autobuilder does not determine the name of uImage. It seems that:

LINUX_VERSION ?= "3.0.24" 
PV = "${LINUX_VERSION}+git${SRCPV}"

is innaccurate in meta/recipes-kernel/linux/linux-yocto_3.0.bb 

Reassigning to kernel team.
Comment 2 Darren Hart 2012-04-09 20:24:23 UTC
If we checkout the BSP branch and read the Makefile, we see:

VERSION = 3
PATCHLEVEL = 0
SUBLEVEL = 24

So the sources will build a 3.0.24 kernel, and as noted by Beth in Comment 1, the recipe also reflects a 3.0.24 kernel.

It appears that for whatever reason, the image on the autobuilder has not rebuilt the kernel image from the new sources.

Note that for the uImage listed (machine sources 7ba6d6853b6e7cf00a742baeba1503c80fc05314), 3.0.23 is correct. This is the machine SRCREV in meta-yocto. The correct fix is to update the machine SRCREV to what is current in the BSP branch.

Bruce, was this an omission, or has the mpc machine been held back deliberately?
Comment 3 Dexuan Cui 2012-04-10 02:30:27 UTC
(Sorry for my previous incorrect change to the Whiteboard -- I didn't use the correct link...)
Comment 4 Bruce Ashfield 2012-04-10 04:27:58 UTC
looks like an omission for meta-yocto. will update ASAP.
Comment 5 Bruce Ashfield 2012-04-10 13:36:38 UTC
pull request sent to the list.
Comment 6 Jessica 2012-05-01 17:37:04 UTC
Bruce, please mark the bug as fixed since the pull request sent
Comment 7 Bruce Ashfield 2012-05-01 21:46:19 UTC
verified.