1375 2011-08-17 06:23:05 +0000 Kernel 2.6.37 include/generated/utsrelease.h not sync with .config 2012-03-27 13:28:20 +0000 1 1 6 Yocto Project Subprojects Kernel kernel-configuration unspecified JasperForest x86_64 RESOLVED FIXED (P3) Bruce to find an owner Medium minor 1.2 M4 1 gavian bruce.ashfield dvhart meta.mr.watcher meta.watcher sgw yp.kernel.watcher yp.watcher --- --- --- oldest_to_newest 15505 0 gavian 2011-08-17 06:23:05 +0000 In the kernel 2.6.37 the .config file isn't synced with include/generated/utsrelease.h. It causes that modules compiled against this kernel will have kernel magic number mismatch. content of the 'include/generated/utsrelease.h' file: UTS_RELEASE "2.6.37.6-yocto-standard+" content of the '.config' file: CONFIG_LOCALVERSION="-yocto-standard" Workaround: After compilation run 'make CC=${KERNEL_CC} LD=${KERNEL_LD} prepare' in the tmp/sysrootfs/<arch>/kernel directory 15508 1 bruce.ashfield 2011-08-17 06:56:04 +0000 .. and what's the new utsrelease.h file after you run this ? 'make CC=${KERNEL_CC} LD=${KERNEL_LD} prepare' in the tmp/sysrootfs/<arch>/kernel directory I'm building and loading modules constantly, as are our QA tests without mismatch. What you list below, looks like the proper behaviour to me. So I must be missing something. 15510 2 gavian 2011-08-17 07:12:11 +0000 It corrects the utsrelease.h file. The content of the utsrelease.h file after `make prepare` is: #UTS_RELEASE "2.6.37.6-yocto-standard" (the plus sign is gone). (In reply to comment #1) > .. and what's the new utsrelease.h file after you run this ? > > 'make CC=${KERNEL_CC} LD=${KERNEL_LD} prepare' in the > tmp/sysrootfs/<arch>/kernel directory > > I'm building and loading modules constantly, as are our QA tests without > mismatch. What you list below, looks like the proper behaviour to me. So I must > be missing something. 15511 3 bruce.ashfield 2011-08-17 07:13:42 +0000 There's something else wrong then. Do you have local changes to your kernel source tree ? 15755 4 gavian 2011-08-25 03:52:21 +0000 I have made bitbake to create a krenel package from the beginning. Fetch, patch, etc. and still have the same file mismatch. content of kernel-abiversion: 2.6.37.6-yocto-standard+ content of utsrelease.h #define UTS_RELEASE "2.6.37.6-yocto-standard+" content of .config CONFIG_LOCALVERSION="-yocto-standard" I don't know where is this plus sign coming from ?? (In reply to comment #3) > There's something else wrong then. Do you have local changes to your > kernel source tree ? 15757 5 dvhart 2011-08-25 08:11:41 +0000 The plus sign is added to a kernel built from git sources that have been modified if I recall correctly. 15758 6 bruce.ashfield 2011-08-25 08:15:20 +0000 correct. it usually signifies a dirty tree, that's why I was asking about local changes. Are there any patches applied by recipes in this case ? 15763 7 bruce.ashfield 2011-08-25 11:22:45 +0000 I'm seeing something different here, looking into what could be the delta. 16770 8 dvhart 2011-10-06 15:29:17 +0000 Bruce, can you elaborate on Comment 7? Are you seeing a problem here? 16792 9 bruce.ashfield 2011-10-07 21:03:42 +0000 I saw a tweaked utsrelease file, meaning it didn't quite match recipe space. But I've never seen any build or runtime issues. I'm still working on this, but release items have taken priority for now. 18928 10 bruce.ashfield 2012-03-08 20:55:35 +0000 I'll look at this during M4 19481 11 bruce.ashfield 2012-03-26 20:31:55 +0000 FYI: this is nearly fixed in master. I'll close the bug when the final part of the fix goes in. [OE-core] [PATCH] kernel.bbclass: touch .scmversion also in ${S} Fixes this problem. 19516 12 bruce.ashfield 2012-03-27 13:28:20 +0000 commit cafb94f571236603999b406dffef88306ed48cb3 in master solves this issue.