Bug 5859 - kernel version mismatched on non-x86 bsp with 1.6 m3 rc2 build
Summary: kernel version mismatched on non-x86 bsp with 1.6 m3 rc2 build
Status: RESOLVED DUPLICATE of bug 5858
Alias: None
Product: Kernel
Classification: Yocto Project Subprojects
Component: linux-yocto (show other bugs)
Version: 1.6
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Bruce Ashfield
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-02-21 08:38 UTC by Yi Zhao
Modified: 2014-02-21 10:16 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yi Zhao 2014-02-21 08:38:34 UTC
Image location: http://autobuilder.yoctoproject.org/pub/nightly/20140218-3/machines/

Git rev: master/54562006c1327c5b99daa4cc05a3ba7e38412da1

In autobuilder download directory, the file name of kernel shows the kernel version is 3.10.28, but the real version is 3.10.25.

For mpc8315e-rdb:

http://autobuilder.yoctoproject.org/pub/nightly/20140218-3/machines/mpc8315e-rdb/uImage--3.10.28+git0+8f8af5a3b1_10de7036a4-r0-mpc8315e-rdb-20140218153900.bin

###############
~# uname -a
Linux mpc8315e-rdb 3.10.25-yocto-standard #1 PREEMPT Tue Feb 18 16:25:43 UTC 2014 ppc GNU/Linux
###############

This issue exists on beagleboard, mpc8315e-rdb and routerstationpro.
Comment 1 Paul Eggleton 2014-02-21 10:07:48 UTC
This is an exact duplicate of #5858. I'm not sure if this was intentional given it's for three machines; however I think we only need one bug open for it even if that was the case.

*** This bug has been marked as a duplicate of bug 5858 ***
Comment 2 Yi Zhao 2014-02-21 10:16:07 UTC
(In reply to comment #1)
> This is an exact duplicate of #5858. I'm not sure if this was intentional
> given it's for three machines; however I think we only need one bug open for
> it even if that was the case.
> 
> *** This bug has been marked as a duplicate of bug 5858 ***

I'm sorry for this. When I filed this bug I encountered some Internet connection issues. That made the same bug reported many times.