Bug 4991 - Invalid symbolic link kernel image in qemu rootfs
Summary: Invalid symbolic link kernel image in qemu rootfs
Status: RESOLVED FIXED
Alias: None
Product: Kernel
Classification: Yocto Project Subprojects
Component: linux-yocto (show other bugs)
Version: 1.5
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.5 M4
Assignee: Darren Hart
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-08-07 09:24 UTC by Yi Zhao
Modified: 2013-09-18 15:19 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yi Zhao 2013-08-07 09:24:29 UTC
Image location: http://autobuilder.yoctoproject.org/pub/nightly/20130731-1/machines/qemu/

Git rev: master/9de0ad47462c13ac4a2d73e12e92be6c1b4e0415

For qemux86, qemux86-64, and qemuarm images, The kernel image symbolic link file is invalid in /boot directory. 

#################
root@qemux86:~# ls -l /boot/
total 206137
-rw-r--r-- 1 root root    370464 Jul 25 06:18 Module.symvers-3.8.13-yocto-standard
-rw-r--r-- 1 root root   2190813 Jul 25 06:18 System.map-3.8.13-yocto-standard
lrwxrwxrwx 1 root root        29 Jul 31 06:53 bzImage -> bzImage-3.8.13-yocto-standard
-rw-r--r-- 1 root root     90781 Jul 25 06:18 config-3.8.13-yocto-standard
-rw-r--r-- 1 root root 207599805 Jul 25 06:18 vmlinux-3.8.13-yocto-standard
root@qemux86:~# 
##################

###################
root@qemux86-64:~# ls -l /boot/
total 142661
-rw-r--r-- 1 root root    348525 Jul 25 08:12 Module.symvers-3.8.13-yocto-standard
-rw-r--r-- 1 root root   2356611 Jul 25 08:12 System.map-3.8.13-yocto-standard
lrwxrwxrwx 1 root root        29 Jul 31 06:43 bzImage -> bzImage-3.8.13-yocto-standard
-rw-r--r-- 1 root root     74221 Jul 25 08:12 config-3.8.13-yocto-standard
-rw-r--r-- 1 root root 142726804 Jul 25 08:12 vmlinux-3.8.13-yocto-standard
root@qemux86-64:~# 
####################

####################
root@qemuarm:~# ls -l /boot/
total 91975
-rw-r--r-- 1 root root   299749 Jul 25 11:17 Module.symvers-3.8.13-yocto-standard
-rw-r--r-- 1 root root  1545345 Jul 25 11:17 System.map-3.8.13-yocto-standard
-rw-r--r-- 1 root root    61075 Jul 25 11:17 config-3.8.13-yocto-standard
-rw-r--r-- 1 root root 91899977 Jul 25 11:17 vmlinux-3.8.13-yocto-standard
lrwxrwxrwx 1 root root       28 Jul 31 06:42 zImage -> zImage-3.8.13-yocto-standard
root@qemuarm:~# 
####################
Comment 1 Darren Hart 2013-08-08 15:53:11 UTC
Which images specifically? I just built core-image-minimal for qemux86 and the /boot directory in the ext2 image is empty.
Comment 2 Darren Hart 2013-08-08 15:54:51 UTC
bah, apologies, was building poky-tiny on accident.
Comment 3 Darren Hart 2013-08-09 17:02:24 UTC
This appears to be due to pkg_postinst_kernel-base making the alternatives link when it's kernel-image that installs the actual kernel image. Testing a correction.
Comment 4 Darren Hart 2013-08-09 17:55:11 UTC
Patch submitted to OE-Core
Comment 5 Darren Hart 2013-09-18 15:19:38 UTC
commit 7590f6926de6dcee05a5b71ef61b8a09972daac5
Author: Darren Hart <dvhart@linux.intel.com>
Date:   Fri Aug 9 10:58:42 2013 -0700

    kernel.bbclass: Correct post(inst|rm) package association
    
    Fixes [YOCTO #4991]
    
    The kernel image is installed as part of the kernel-image package, but
    the symlink creation/removal via alternatives is being done in
    pkg_post(inst|rm)_kernel-base.
    
    Move the postinst alternatives logic into the kernel-image functions.
    
    (From OE-Core rev: 35f538b117e3387354d2dab1f22c3de28ab1322b)