| Summary: | linux-yocto failed to do_patch after add a patch by yocto-kernel tool | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Yi Zhao <yi.zhao> | ||||||||||||
| Component: | kernel | Assignee: | Richard Purdie <richard.purdie> | ||||||||||||
| Status: | RESOLVED FIXED | QA Contact: | Yi Zhao <yi.zhao> | ||||||||||||
| Severity: | minor | ||||||||||||||
| Priority: | Medium | CC: | alexandru.c.georgescu, bruce.ashfield, dvhart, georgex.l.musat, ke.zou, mhalstead, richard.purdie, ross.burton, sgw, tf+bugs.yocto, tom.zanussi, yi.zhao | ||||||||||||
| Version: | 1.6 | ||||||||||||||
| Target Milestone: | 2.1 M4 | ||||||||||||||
| Hardware: | x86 | ||||||||||||||
| OS: | Multiple | ||||||||||||||
| Whiteboard: | |||||||||||||||
| OS type for building Yocto: | --- | Type of Regression: | Regression (Used to work) | ||||||||||||
| Verified: | Documentation change: | Don't know | |||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Yi Zhao
2014-04-15 06:31:55 UTC
Created attachment 1915 [details]
log.do_patch
Does the branch you requested to use exist in the kernel repository? "Branch standard/common-pc/myqemux86 set up to track remote branch standard/common-pc/base from origin." When you do not create a new branch, do you use standard/common-pc/base or something else? (In reply to comment #2) > Does the branch you requested to use exist in the kernel repository? Yes. The yocto-bsp tool can list all branch in kernel repository. For myqemux86, it bases on standard/common-pc/base Here are the full outputs: ########################### $ yocto-bsp create myqemux86 qemu Checking basic git connectivity... Done. Which qemu architecture would you like to use? [default: i386] 1) i386 (32-bit) 2) x86_64 (64-bit) 3) ARM (32-bit) 4) PowerPC (32-bit) 5) MIPS (32-bit) Would you like to use the default (3.14) kernel? (y/n) [default: y] Do you need a new machine branch for this BSP (the alternative is to re-use an existing branch)? [y/n] [default: y] Getting branches from remote repo git://git.yoctoproject.org/linux-yocto-3.14.git... Please choose a machine branch to base this BSP on: [default: standard/common-pc/base] 1) standard/arm-versatile-926ejs 2) standard/base 3) standard/beagleboard 4) standard/beaglebone 5) standard/ck 6) standard/common-pc/atom-pc 7) standard/common-pc/base 8) standard/crownbay 9) standard/edgerouter 10) standard/emenlow 11) standard/fri2 12) standard/fsl-mpc8315e-rdb 13) standard/mti-malta32 14) standard/mti-malta64 15) standard/qemuppc 16) standard/routerstationpro 17) standard/sys940x Would you like SMP support? (y/n) [default: y] Does your BSP have a touchscreen? (y/n) [default: n] Does your BSP have a keyboard? (y/n) [default: y] New qemu BSP created in meta-myqemux86 $ yocto-kernel patch add myqemux86 ./yocto-testmod.patch Added patches: yocto-testmod.patch $ yocto-kernel patch list myqemux86 The current set of machine-specific patches for myqemux86 is: 1) yocto-testmod.patch $ yocto-kernel config add myqemux86 CONFIG_MISC_DEVICES=y Added item: CONFIG_MISC_DEVICES=y $ yocto-kernel config add myqemux86 CONFIG_YOCTO_TESTMOD=y Added item: CONFIG_YOCTO_TESTMOD=y $ yocto-kernel config list myqemux86 The current set of machine-specific kernel config items for myqemux86 is: 1) CONFIG_MISC_DEVICES=y 2) CONFIG_YOCTO_TESTMOD=y ########################## (In reply to comment #3) > "Branch standard/common-pc/myqemux86 set up to track remote branch > standard/common-pc/base from origin." > > When you do not create a new branch, do you use standard/common-pc/base or > something else? For myqemux86, it uses standard/common-pc/base. I also tested myqemuarm, it uses standard/arm-versatile-926ejs Thanks Yi Zhao, that should be enough for us to reproduce. Tom, do you need any additional detail? Yeah, I've reproduced it. The (updated) patches get applied just fine, but the failure seems to be something trying to apply them *again*. error: drivers/misc/yocto-testmod.c: already exists in index Looking at the branches, the patches are apparently being applied to standard/base instead of standard/common-pc/qemutest, which exists but apparently isn't being used: [trz@empanada linux]$ git branch master meta meta-orig standard/arm-versatile-926ejs * standard/base standard/beagleboard standard/beaglebone standard/ck standard/common-pc-64/base standard/common-pc-64/chiefriver standard/common-pc-64/crystalforest standard/common-pc-64/jasperforest standard/common-pc-64/mohonpeak standard/common-pc-64/romley standard/common-pc-64/sugarbay standard/common-pc/atom-pc standard/common-pc/base standard/common-pc/qemutest Created attachment 2015 [details]
myqemux86 bsp
This is strange and used to work before. The patch is good, and gets applied (albeit to the wrong branch) but do_patch fails. Running bitbake virtual/kernel again after that, do_patch succeeds and builds fine (but on top of the wrong branch):
trz@elmorro:/usr/local/src/yocto/test/build$ bitbake virtual/kernelLoading cache: 100% |###########################################| ETA: 00:00:00
Loaded 1248 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.23.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-12.04"
TARGET_SYS = "i586-poky-linux"
MACHINE = "myqemux86"
DISTRO = "poky"
DISTRO_VERSION = "1.6+snapshot-20140620"
TUNE_FEATURES = "m32 i586"
TARGET_FPU = ""
meta
meta-yocto
meta-yocto-bsp
meta-myqemux86 = "master0:5b1c329804f9f3fadcc46452390f537052ff7d0e"
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: do_patch (log file is located at /usr/local/src/yocto/test/build/tmp/work/myqemux86-poky-linux/linux-yocto/3.14.5+gitAUTOINC+602be954ac_96930820e0-r0.4/temp/log.do_patch.9400)
ERROR: Logfile of failure stored in: /usr/local/src/yocto/test/build/tmp/work/myqemux86-poky-linux/linux-yocto/3.14.5+gitAUTOINC+602be954ac_96930820e0-r0.4/temp/log.do_patch.9400
Log data follows:
| DEBUG: Executing shell function do_patch
| Branch meta-temp set up to track remote branch meta from origin.
| Deleted branch meta-temp (was d36a7ef).
| [INFO] validating against known patches (myqemux86-standard-meta)
Branch standard/common-pc/myqemux86 set up to track remote branch standard/common-pc/base from origin.
Context reduced to (1/1) to apply fragment at 388 ] (/)(91 %)%)
| error: patch failed: drivers/misc/Makefile:37
| error: drivers/misc/Makefile: patch does not apply
| error: drivers/misc/yocto-testmod.c: already exists in index
| ERROR. could not update git tree
| ERROR. Could not apply patches for myqemux86.
| Patch failures can be resolved in the devshell (bitbake -c devshell linux-yocto)
| WARNING: /usr/local/src/yocto/test/build/tmp/work/myqemux86-poky-linux/linux-yocto/3.14.5+gitAUTOINC+602be954ac_96930820e0-r0.4/temp/run.do_patch.9400:1 exit 1 from
| exit 1
| ERROR: Function failed: do_patch (log file is located at /usr/local/src/yocto/test/build/tmp/work/myqemux86-poky-linux/linux-yocto/3.14.5+gitAUTOINC+602be954ac_96930820e0-r0.4/temp/log.do_patch.9400)
ERROR: Task 3 (/usr/local/src/yocto/test/meta/recipes-kernel/linux/linux-yocto_3.14.bb, do_patch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 386 tasks of which 381 didn't need to be rerun and 1 failed.
No currently running tasks (386 of 404)
Summary: 1 task failed:
/usr/local/src/yocto/test/meta/recipes-kernel/linux/linux-yocto_3.14.bb, do_patch
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
trz@elmorro:/usr/local/src/yocto/test/build/tmp/work/myqemux86-poky-linux/linux-yocto/3.14.5+gitAUTOINC+602be954ac_96930820e0-r0.4/linux$ git branch
master
meta
standard/arm-versatile-926ejs
* standard/base
standard/beagleboard
standard/beaglebone
standard/ck
standard/common-pc-64/base
standard/common-pc/base
standard/common-pc/myqemux86
standard/edgerouter
standard/fsl-mpc8315e-rdb
standard/mti-malta32
standard/mti-malta64
standard/preempt-rt/base
standard/preempt-rt/fri2
standard/preempt-rt/qemuppc
standard/qemuppc
standard/routerstationpro
standard/tiny/base
standard/tiny/common-pc
trz@elmorro:/usr/local/src/yocto/test/build/tmp/work/myqemux86-poky-linux/linux-yocto/3.14.5+gitAUTOINC+602be954ac_96930820e0-r0.4/linux$ git log
commit fbfe435e27c0918a092266738a07c90bc1713be3
Author: invalid_git config <unknown@unknown>
Date: Fri Jun 20 15:57:40 2014 -0500
commit fbfe435e27c0918a092266738a07c90bc1713be3
Author: invalid_git config <unknown@unknown>
Date: Fri Jun 20 15:57:40 2014 -0500
diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
index 6cb388e..086c6ab 100644
--- a/drivers/misc/Kconfig
+++ b/drivers/misc/Kconfig
@@ -381,6 +381,11 @@ config HMC6352
This driver provides support for the Honeywell HMC6352 compass,
providing configuration and heading data via sysfs.
+config YOCTO_TESTMOD
+ tristate "Yocto Test Driver"
+ help
+ This driver provides a silly message for testing Yocto.
+
config DS1682
tristate "Dallas DS1682 Total Elapsed Time Recorder with Alarm"
depends on I2C
diff --git a/drivers/misc/Makefile b/drivers/misc/Makefile
index 99b9424..808a3fc 100644
--- a/drivers/misc/Makefile
+++ b/drivers/misc/Makefile
@@ -37,6 +37,7 @@ obj-$(CONFIG_DS1682) += ds1682.o
obj-$(CONFIG_TI_DAC7512) += ti_dac7512.o
obj-$(CONFIG_C2PORT) += c2port/
obj-$(CONFIG_HMC6352) += hmc6352.o
+obj-$(CONFIG_YOCTO_TESTMOD) += yocto-testmod.o
obj-y += eeprom/
obj-y += cb710/
obj-$(CONFIG_SPEAR13XX_PCIE_GADGET) += spear13xx_pcie_gadget.o
diff --git a/drivers/misc/yocto-testmod.c b/drivers/misc/yocto-testmod.c
new file mode 100644
index 0000000..a0b33f1
--- /dev/null
+++ b/drivers/misc/yocto-testmod.c
@@ -0,0 +1,38 @@
+/*
+ * Copyright 2013 Intel Corporation
+ * Authored-by: Tom Zanussi <tom.zanussi@linux.intel.com>
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License along
+ * with this program; if not, write to the Free Software Foundation, Inc.,
+ * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+ */
+
+#include <linux/module.h>
+
+static int __init yocto_testmod_init(void)
+{
+ printk("Krillroy swam here!");
+
+ return 0;
+}
+
+static void __exit yocto_testmod_exit(void)
+{
+ printk("Krillroy no longer swims here!");
+}
+
+module_init(yocto_testmod_init);
+module_exit(yocto_testmod_exit);
+
+MODULE_AUTHOR("Tom Zanussi <tom.zanussi@linux.intel.com");
+MODULE_DESCRIPTION("Yocto Test Driver");
+MODULE_LICENSE("GPL");
trz@elmorro:/usr/local/src/yocto/test/build$ bitbake virtual/kernel
Loading cache: 100% |################################################################| ETA: 00:00:00
Loaded 1248 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.23.1"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-12.04"
TARGET_SYS = "i586-poky-linux"
MACHINE = "myqemux86"
DISTRO = "poky"
DISTRO_VERSION = "1.6+snapshot-20140620"
TUNE_FEATURES = "m32 i586"
TARGET_FPU = ""
meta
meta-yocto
meta-yocto-bsp
meta-myqemux86 = "master0:5b1c329804f9f3fadcc46452390f537052ff7d0e"
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: validating kernel config, see log.do_kernel_configcheck for details
NOTE: Tasks Summary: Attempted 404 tasks of which 385 didn't need to be rerun and all succeeded.
It seems like a problem with the kernel tools - Bruce, can you take a look?
BSP attached.
Seems this issue is related with the host. I tested it on Ubuntu 12.04 x86_64, Ubuntu 13.10 x86_64 and Ubuntu 14.04 x86_64. It failed on 12.04 and 13.10, but passed on 14.04. I have run into a manifestation of this bug as well this week. We have a custom kernel derived from the Yocto 3.4 kernel, with a standard/<machine> branch, which was building fine under danny, but not under daisy. From trying to debug the tools, the correct standard/<machine> branch is passed into the patchme utility, but the generate_branch_name() function in kgit-meta changes the patch set to standard/base, which fails to apply onto our kernel; I have not yet worked out why that change is happening. Tom/Bruce: What are the next steps with this one? (In reply to comment #12) > Tom/Bruce: What are the next steps with this one? I guess I'll have to refresh my investigation of this and provide the needed info myself - it seems like a clear-cut kernel tools problem, and not a yocto-kernel tool problem per se, as it's also reported by someone else independently, but I will try to dig further. (In reply to comment #11) > I have run into a manifestation of this bug as well this week. We have a > custom kernel derived from the Yocto 3.4 kernel, with a standard/<machine> > branch, which was building fine under danny, but not under daisy. > > From trying to debug the tools, the correct standard/<machine> branch is > passed into the patchme utility, but the generate_branch_name() function in > kgit-meta changes the patch set to standard/base, which fails to apply onto > our kernel; I have not yet worked out why that change is happening. Could you provide a reproducible test-case for the problem and post it here? Assigned to tf who need to support the request. The patch stage is failing because, as per comment #7, the patches that are getting applied have already been applied to the tree, I suspect this is somehow related to the introduction of the kgit-s2q script, the following output looks relevant: | [INFO] No annotated resume point (parent ID) falling back to patch id detection | [INFO] Could not autodetect resume point via patch ID falling back to diffstat detection | [INFO] Could not autodetect resume point via diffstat | [INFO] Could not autodetect resume point via annotation, patch ID, diffstat or matching filename. | Patch that created current HEAD commit is unknown. Starting from the first patch. Reverting back to yocto-kernel-tools rev fbcdcb8e23c38352b46235598f34d7b345f458f1 (the last quilt-based version of kern-tools used by Yocto), makes everything work again with our kernel, so it looks like the patch application detection in the kgit-s2g tool is not working. The patch application detection of the new tools works all day every day. What you mean is that for some reason that patches generated here are not working .. not the general case, since that is known to work well .. and we are applying (and skipping) patches with it all the time. I'll have a look at this later, but not for a week or so. (In reply to comment #17) > Reverting back to yocto-kernel-tools rev > fbcdcb8e23c38352b46235598f34d7b345f458f1 (the last quilt-based version of > kern-tools used by Yocto), makes everything work again with our kernel, so > it looks like the patch application detection in the kgit-s2g tool is not > working. Bruce agreed to take a look. This is working fine on the master branch: yow-bashfiel-d3 [/home/bruc...r0.4/linux]> pwd /home/bruce/poky/build/tmp/work/myqemux86-poky-linux/linux-yocto/3.14.17+gitAUTOINC+cfbe4f24b8_2957702793-r0.4/linux > git whatchanged commit c09b0c52c39051cc2e39b3d541b0add7cc5f2fdc Author: invalid_git config <unknown@unknown> Date: Tue Sep 16 23:24:42 2014 -0400 :100644 100644 6cb388e8fb7d... 086c6abeffb6... M drivers/misc/Kconfig :100644 100644 99b9424ce31d... 808a3fc6288a... M drivers/misc/Makefile :000000 100644 000000000000... a0b33f1d1e69... A drivers/misc/yocto-testmod.c > git branch master meta standard/arm-versatile-926ejs standard/base standard/beagleboard standard/beaglebone standard/ck standard/common-pc-64/base standard/common-pc/base * standard/common-pc/myqemux86 standard/edgerouter standard/fsl-mpc8315e-rdb standard/mti-malta32 standard/mti-malta64 standard/preempt-rt/base standard/preempt-rt/fri2 standard/preempt-rt/qemuppc standard/qemuppc standard/routerstationpro standard/tiny/base standard/tiny/common-pc Sending back for a new test, since with the attached myqemux86 bsp layer, I can patch and build fine on master (and that's where yocto 1.7 bugs are addressed). If a backport is required to an older branch, someone can nominate my latest updates to the maintainer. OK, I don't see the problem with the myqemux86 bsp with 3.14, but with 3.17 I do, see below. This is using the same bsp as before but renaming the 3.14 kernel .bbappend to 3.17 and the preferred version in the machine.conf to 3.17. That bsp attached for reference. [trz@empanada build]$ bitbake core-image-minimal Parsing recipes: 100% |#########################################################| Time: 00:00:18 Parsing of 886 .bb files complete (0 cached, 886 parsed). 1281 targets, 47 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.23.2" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Fedora-19" TARGET_SYS = "i586-poky-linux" MACHINE = "myqemux86" DISTRO = "poky" DISTRO_VERSION = "1.6+snapshot-20140920" TUNE_FEATURES = "m32 i586" TARGET_FPU = "" meta meta-yocto meta-yocto-bsp meta-myqemux86 = "master0:280b6d0011f101e7a8edabd34c265b37a2f791ed" NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: Function failed: do_patch (log file is located at /home/trz/yocto/yocto-bsp-1.7/build/tmp/work/myqemux86-poky-linux/linux-yocto/3.17-rc4+gitAUTOINC+7df849fc7e_1a3939eb74-r0.4/temp/log.do_patch.27470) ERROR: Logfile of failure stored in: /home/trz/yocto/yocto-bsp-1.7/build/tmp/work/myqemux86-poky-linux/linux-yocto/3.17-rc4+gitAUTOINC+7df849fc7e_1a3939eb74-r0.4/temp/log.do_patch.27470 Log data follows: | DEBUG: Executing shell function do_patch | Unstaged changes after reset: | M meta/cfg/kernel-cache/00-README | M meta/cfg/kernel-cache/arch/arm/arm.scc | M meta/cfg/kernel-cache/arch/mips/4kc-cache-tlb-hazard-tlbp-cache-coherency.patch | M meta/cfg/kernel-cache/arch/mips/mips-support-preemptible-kernel.patch | M meta/cfg/kernel-cache/arch/mips/mips.scc | D meta/cfg/kernel-cache/arch/powerpc/powerpc-85xx-Make-sure-lwarx-hint-isn-t-set-on-ppc32.patch | M meta/cfg/kernel-cache/bsp/arm-versatile-926ejs/arm-versatile-926ejs-standard.scc | M meta/cfg/kernel-cache/bsp/arm-versatile-926ejs/arm-versatile-926ejs.cfg | M meta/cfg/kernel-cache/bsp/arm-versatile-926ejs/arm-versatile-926ejs.scc | M meta/cfg/kernel-cache/bsp/arm-versatile-926ejs/arm_versatile_926ejs-add-default-nor-flash-mtd-parts.patch | M meta/cfg/kernel-cache/bsp/arm-versatile-926ejs/arm_versatile_926ejs-kick-off-PrimeCell-RTC-PL031.patch | D meta/cfg/kernel-cache/bsp/atom-pc/atom-pc-eth.cfg | D meta/cfg/kernel-cache/bsp/atom-pc/atom-pc-standard.scc | D meta/cfg/kernel-cache/bsp/atom-pc/atom-pc-wifi.cfg | D meta/cfg/kernel-cache/bsp/atom-pc/atom-pc.scc | D meta/cfg/kernel-cache/bsp/atom-pc/boot-live.cfg | M meta/cfg/kernel-cache/bsp/beagleboard/beagleboard-standard.scc | M meta/cfg/kernel-cache/bsp/beagleboard/beagleboard.cfg | M meta/cfg/kernel-cache/bsp/beagleboard/beagleboard.scc | D meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64-graphics.cfg | M meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64-preempt-rt.scc | M meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64-standard.scc | D meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.cfg | M meta/cfg/kernel-cache/bsp/common-pc-64/common-pc-64.scc | M meta/cfg/kernel-cache/bsp/common-pc-64/hardware.cfg | M meta/cfg/kernel-cache/bsp/common-pc/common-pc-gfx.cfg | D meta/cfg/kernel-cache/bsp/common-pc/common-pc-net.cfg | M meta/cfg/kernel-cache/bsp/common-pc/common-pc-preempt-rt.scc | M meta/cfg/kernel-cache/bsp/common-pc/common-pc-standard.scc | D meta/cfg/kernel-cache/bsp/common-pc/common-pc.cfg | M meta/cfg/kernel-cache/bsp/common-pc/common-pc.scc | M meta/cfg/kernel-cache/bsp/common-pc/hardware.cfg | M meta/cfg/kernel-cache/bsp/crownbay/crownbay-standard.scc | M meta/cfg/kernel-cache/bsp/crownbay/crownbay.cfg | M meta/cfg/kernel-cache/bsp/crownbay/crownbay.scc | D meta/cfg/kernel-cache/bsp/crownbay/eg20t.cfg | M meta/cfg/kernel-cache/bsp/emenlow/emenlow-standard.scc | M meta/cfg/kernel-cache/bsp/emenlow/emenlow.cfg | M meta/cfg/kernel-cache/bsp/emenlow/emenlow.scc | D meta/cfg/kernel-cache/bsp/emenlow/reboot-quirk.cfg | M meta/cfg/kernel-cache/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb-standard.scc | M meta/cfg/kernel-cache/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.cfg | M meta/cfg/kernel-cache/bsp/fsl-mpc8315e-rdb/fsl-mpc8315e-rdb.scc | D meta/cfg/kernel-cache/bsp/fsl-mpc8315e-rdb/powerpc-boot-remove-Os-from-BOOTFLAGS.patch | M meta/cfg/kernel-cache/bsp/jasperforest/jasperforest-standard.scc | M meta/cfg/kernel-cache/bsp/jasperforest/jasperforest.cfg | M meta/cfg/kernel-cache/bsp/jasperforest/jasperforest.scc | M meta/cfg/kernel-cache/bsp/mti-malta32/mousedev-mousedev-patch-for-qemumips.patch | M meta/cfg/kernel-cache/bsp/mti-malta32/mti-malta32-be-standard.scc | M meta/cfg/kernel-cache/bsp/mti-malta32/mti-malta32-common.cfg | M meta/cfg/kernel-cache/bsp/mti-malta32/mti-malta32-le-standard.scc | M meta/cfg/kernel-cache/bsp/mti-malta32/mti-malta32.scc | M meta/cfg/kernel-cache/bsp/qemu-ppc32/qemu-platform-v2.patch | M meta/cfg/kernel-cache/bsp/qemu-ppc32/qemu-powerpc-work-around-for-qemu-powerpc-32-interru.patch | M meta/cfg/kernel-cache/bsp/qemu-ppc32/qemu-ppc32-standard.scc | M meta/cfg/kernel-cache/bsp/qemu-ppc32/qemu-ppc32.cfg | M meta/cfg/kernel-cache/bsp/qemu-ppc32/qemu-ppc32.scc | M meta/cfg/kernel-cache/bsp/qemu-ppc32/qemu_ppc-enable-IDE-support.patch | M meta/cfg/kernel-cache/bsp/qemu-ppc32/qemu_ppc32-support-multiple-ethernet-interfaces.patch | D meta/cfg/kernel-cache/bsp/routerstationpro/Add-NET_DSA_MV88E6063-support-for-ar71xx.patch | D meta/cfg/kernel-cache/bsp/routerstationpro/Add-arch-suport-for-ar71xx.patch | D meta/cfg/kernel-cache/bsp/routerstationpro/Add-generic-support-for-mips.patch | D meta/cfg/kernel-cache/bsp/routerstationpro/Add-gpio-support-for-nxp_74hc153.patch | D meta/cfg/kernel-cache/bsp/routerstationpro/Add-include-file-support-ar71xx.patch | D meta/cfg/kernel-cache/bsp/routerstationpro/Add-leds-support-for-ar71xx.patch | D meta/cfg/kernel-cache/bsp/routerstationpro/Add-mtd-support-ar71xx.patch | D meta/cfg/kernel-cache/bsp/routerstationpro/Add-myloader-support-for-ar71xx.patch | D meta/cfg/kernel-cache/bsp/routerstationpro/Add-net-driver-support-ar71xx.patch | D meta/cfg/kernel-cache/bsp/routerstationpro/Add-pci-supoprt-for-ar7xxx.patch | D meta/cfg/kernel-cache/bsp/routerstationpro/Add-spi-support-for-ar71xx.patch | D meta/cfg/kernel-cache/bsp/routerstationpro/Add-usb-controller-support-for-ar71xx.patch | D meta/cfg/kernel-cache/bsp/routerstationpro/Get-compare_irq-from-function.patch | D meta/cfg/kernel-cache/bsp/routerstationpro/fix-compiling-errors.patch | D meta/cfg/kernel-cache/bsp/routerstationpro/fix-mtd-bugs-for-ar71xx.patch | D meta/cfg/kernel-cache/bsp/routerstationpro/routerstationpro-standard.scc | D meta/cfg/kernel-cache/bsp/routerstationpro/routerstationpro.cfg | D meta/cfg/kernel-cache/bsp/routerstationpro/routerstationpro.scc | M meta/cfg/kernel-cache/bsp/sugarbay/sugarbay-standard.scc | M meta/cfg/kernel-cache/bsp/sugarbay/sugarbay.cfg | M meta/cfg/kernel-cache/bsp/sugarbay/sugarbay.scc | D meta/cfg/kernel-cache/cfg/fs.cfg | D meta/cfg/kernel-cache/cfg/fs.scc | M meta/cfg/kernel-cache/cfg/sound.scc | M meta/cfg/kernel-cache/cfg/usb-mass-storage.cfg | M meta/cfg/kernel-cache/cfg/usb-mass-storage.scc | D meta/cfg/kernel-cache/cfg/vfat.cfg | M meta/cfg/kernel-cache/features/bsdjail/bsdjail.scc | M meta/cfg/kernel-cache/features/cgroups/README.cgroups | D meta/cfg/kernel-cache/features/cgroups/cgroups-blkio-fix-compiling-error.patch | D meta/cfg/kernel-cache/features/cgroups/cgroups-blkio-v13-body.patch | D meta/cfg/kernel-cache/features/cgroups/cgroups-blkio-v13-doc.patch | D meta/cfg/kernel-cache/features/cgroups/cgroups-blkio-v13-hook.patch | D meta/cfg/kernel-cache/features/cgroups/cgroups-blkio-v13-ioband-doc.patch | D meta/cfg/kernel-cache/features/cgroups/cgroups-blkio-v13-ioband.patch | D meta/cfg/kernel-cache/features/cgroups/cgroups-blkio-v13-iocontext.patch | D meta/cfg/kernel-cache/features/cgroups/cgroups-blkio-v13-pagecgroup.patch | D meta/cfg/kernel-cache/features/cgroups/cgroups-dm-ioband.patch | M meta/cfg/kernel-cache/features/cgroups/cgroups.cfg | M meta/cfg/kernel-cache/features/cgroups/cgroups.scc | D meta/cfg/kernel-cache/features/cgroups/dm_ioband_blkio.cfg | D meta/cfg/kernel-cache/features/cgroups/dm_ioband_blkio.scc | D meta/cfg/kernel-cache/features/cgroups/net_traffic_controller.cfg | D meta/cfg/kernel-cache/features/cgroups/net_traffic_controller.scc | M meta/cfg/kernel-cache/features/drm-emgd/drm-emgd.cfg | D meta/cfg/kernel-cache/features/drm-emgd/drm-emgd.scc | M meta/cfg/kernel-cache/features/drm-psb/drm-psb.cfg | D meta/cfg/kernel-cache/features/edac/EDAC-Add-sysfs-notify-calls-for-counters.patch | D meta/cfg/kernel-cache/features/edac/EDAC-E7501-PCI-fixup-for-MCH-DVNP.patch | D meta/cfg/kernel-cache/features/edac/EDAC-Enhancement-for-e7xxx-driver.patch | D meta/cfg/kernel-cache/features/edac/EDAC-Improvement-for-common-parts.patch | D meta/cfg/kernel-cache/features/edac/EDAC-avoid-redundant-kobject_put-call-for-mci-edac_m.patch | D meta/cfg/kernel-cache/features/edac/EDAC-dump-CPU-registers-if-error-was-checked-by-IRQ.patch | D meta/cfg/kernel-cache/features/edac/EDAC-fix-INTERRUPT-mode-rmmod-failure.patch | M meta/cfg/kernel-cache/features/edac/edac.cfg | M meta/cfg/kernel-cache/features/edac/edac.scc | M meta/cfg/kernel-cache/features/edf/edf.cfg | M meta/cfg/kernel-cache/features/edf/edf.scc | D meta/cfg/kernel-cache/features/edf/sched-SCHED_DEADLINE-policy-implementation.patch | D meta/cfg/kernel-cache/features/edf/sched-add-a-syscall-to-wait-for-the-next-instance.patch | D meta/cfg/kernel-cache/features/edf/sched-add-bandwidth-management-for-sched_dl.patch | D meta/cfg/kernel-cache/features/edf/sched-add-extended-scheduling-interface.patch | D meta/cfg/kernel-cache/features/edf/sched-add-extended-syscalls-for-powerpc-and-mips.patch | D meta/cfg/kernel-cache/features/edf/sched-add-latency-tracing-for-deadline-tasks.patch | D meta/cfg/kernel-cache/features/edf/sched-add-reclaiming-logic-to-deadline-tasks.patch | D meta/cfg/kernel-cache/features/edf/sched-add-resource-limits-for-deadline-tasks.patch | D meta/cfg/kernel-cache/features/edf/sched-add-sched_class-task_dead.patch | D meta/cfg/kernel-cache/features/edf/sched-add-sched_dl-documentation.patch | D meta/cfg/kernel-cache/features/edf/sched-add-special-task-handling-in-SCHED_DEADLINE.patch | D meta/cfg/kernel-cache/features/edf/sched-add-the-sched-debug-bits-for-sched_dl.patch | D meta/cfg/kernel-cache/features/edf/sched-first-draft-of-deadline-inheritance.patch | D meta/cfg/kernel-cache/features/edf/sched-fix-errors-for-api-change.patch | D meta/cfg/kernel-cache/features/edf/sched-send-SIGXCPU-at-deadline-task-overruns.patch | M meta/cfg/kernel-cache/features/ftrace/ftrace.cfg | M meta/cfg/kernel-cache/features/ftrace/ftrace.scc | M meta/cfg/kernel-cache/features/fuse/fuse.cfg | M meta/cfg/kernel-cache/features/fuse/fuse.scc | M meta/cfg/kernel-cache/features/hrt/hrt.cfg | M meta/cfg/kernel-cache/features/hrt/hrt.scc | M meta/cfg/kernel-cache/features/i915/i915.scc | M meta/cfg/kernel-cache/features/initramfs/initramfs-add-wrapper.patch | D meta/cfg/kernel-cache/features/initramfs/initramfs.cfg | M meta/cfg/kernel-cache/features/initramfs/initramfs.scc | M meta/cfg/kernel-cache/features/ipmi/ipmi.scc | D meta/cfg/kernel-cache/features/kexec/MIPS-Update-kexec-to-support-kdump-64-bit-and-SMP.patch | D meta/cfg/kernel-cache/features/kexec/MIPS-kexec-Add-board-specific-cache-flushing.patch | D meta/cfg/kernel-cache/features/kexec/MIPS-kexec-Add-board-specific-handling-of-SMP-system.patch | D meta/cfg/kernel-cache/features/kexec/MIPS-kexec-Add-machine-specific-page-validity-check-.patch | D meta/cfg/kernel-cache/features/kexec/PPC32-kexec-SMP-support-framework.patch | D meta/cfg/kernel-cache/features/kexec/PPC32-kexec-add-extra-way-of-waking-up-secondary-CPU.patch | D meta/cfg/kernel-cache/features/kexec/PPC32-kexec-default-SMP-CPU-takedown.patch | D meta/cfg/kernel-cache/features/kexec/PPC32-kexec-fix-un-reliable-handling-of-SMP-crash.patch | D meta/cfg/kernel-cache/features/kexec/kexec-different-type-comparison-in-crash-kernel.patch | D meta/cfg/kernel-cache/features/kexec/kexec-handle-non-present-IRQ-in-crash-path.patch | D meta/cfg/kernel-cache/features/kexec/kexec-kernel-support-for-PowerPC-Book-E-processors.patch | M meta/cfg/kernel-cache/features/kexec/kexec.scc | D meta/cfg/kernel-cache/features/kexec/mips-arch-changes-to-support-kexec.patch | D meta/cfg/kernel-cache/features/kexec/powerpc-fix-kexec-bug-when-enable-high-mem-support-i.patch | M meta/cfg/kernel-cache/features/kgdb/kgdb.cfg | M meta/cfg/kernel-cache/features/kgdb/kgdb.scc | D meta/cfg/kernel-cache/features/kmemcheck/kmemcheck-Don-t-initialize-cache_change_attribute.patch | D meta/cfg/kernel-cache/features/kmemcheck/kmemcheck-Fix-false-positives.patch | M meta/cfg/kernel-cache/features/kmemcheck/kmemcheck-enable.scc | M meta/cfg/kernel-cache/features/kmemcheck/kmemcheck.cfg | M meta/cfg/kernel-cache/features/kmemcheck/kmemcheck.scc | D meta/cfg/kernel-cache/features/kvm/Eliminate-all-cast-warnings-in-vbus-enet.c-and-pci-b.patch | D meta/cfg/kernel-cache/features/kvm/IOQ-Check-wait-queue-for-waiters-during-signal.patch | D meta/cfg/kernel-cache/features/kvm/KVM-Remove-memslot-refs-feature.patch | D meta/cfg/kernel-cache/features/kvm/KVM-cache-xinterface-memory-slots.patch | D meta/cfg/kernel-cache/features/kvm/KVM-check-mm-in-xinterface.patch | D meta/cfg/kernel-cache/features/kvm/KVM-convert-xinterface-to-use-use_mm-instead-of-get_.patch | D meta/cfg/kernel-cache/features/kvm/KVM-introduce-xinterface-API-for-external-interactio.patch | D meta/cfg/kernel-cache/features/kvm/KVM-synchronize-xinterface-with-version-submitted-to.patch | D meta/cfg/kernel-cache/features/kvm/alacrityvm-incorporate-review-feedback.patch | D meta/cfg/kernel-cache/features/kvm/bracket-vbus-codes-with-CONFIG_VBUS.patch | D meta/cfg/kernel-cache/features/kvm/eventfd-export-eventfd_file_create-function.patch | D meta/cfg/kernel-cache/features/kvm/fix-compiling-error-for-vbus.patch | D meta/cfg/kernel-cache/features/kvm/fix-kernel-crash-due-to-null-pointer.patch | D meta/cfg/kernel-cache/features/kvm/ioq-Add-basic-definitions-for-a-shared-memory-lockle.patch | D meta/cfg/kernel-cache/features/kvm/ioq-add-driver-side-vbus-helpers.patch | D meta/cfg/kernel-cache/features/kvm/ioq-add-vbus-helpers.patch | D meta/cfg/kernel-cache/features/kvm/ioq-clearly-specify-endianness.patch | D meta/cfg/kernel-cache/features/kvm/kvm-add-io-services-to-xinterface.patch | D meta/cfg/kernel-cache/features/kvm/kvm-add-scatterlist-support-to-xinterface.patch | D meta/cfg/kernel-cache/features/kvm/kvm-profiling-x86-compiling-error.patch | M meta/cfg/kernel-cache/features/kvm/kvm.scc | D meta/cfg/kernel-cache/features/kvm/net-add-dataref-destructor-to-sk_buff.patch | D meta/cfg/kernel-cache/features/kvm/powerpc-add-vbus-support.patch | M meta/cfg/kernel-cache/features/kvm/qemu-kvm-enable.scc | D meta/cfg/kernel-cache/features/kvm/shm-signal-provide-an-eventfd-interface.patch | D meta/cfg/kernel-cache/features/kvm/shm-signal-split-eventfd-support-into-different-file.patch | D meta/cfg/kernel-cache/features/kvm/vbus-Add-vbus_enet-driver.patch | D meta/cfg/kernel-cache/features/kvm/vbus-Fix-section-mismatch-warnings-in-pci-bridge.c.patch | D meta/cfg/kernel-cache/features/kvm/vbus-add-IOQ-test-driver.patch | D meta/cfg/kernel-cache/features/kvm/vbus-add-a-kvm-connector.patch | D meta/cfg/kernel-cache/features/kvm/vbus-add-a-vbus-proxy-bus-model-for-vbus_driver-obje.patch | D meta/cfg/kernel-cache/features/kvm/vbus-add-administrative-ioctl-interface-to-complimen.patch | D meta/cfg/kernel-cache/features/kvm/vbus-add-autoprobe-capability-to-guest.patch | D meta/cfg/kernel-cache/features/kvm/vbus-add-bus-registration-notifiers.patch | D meta/cfg/kernel-cache/features/kvm/vbus-add-connection-client-helper-infrastructure.patch | D meta/cfg/kernel-cache/features/kvm/vbus-add-fastcall-support-to-the-kvm-host-logic.patch | D meta/cfg/kernel-cache/features/kvm/vbus-add-missing-static-keywords-to-to_dev-functions.patch | D meta/cfg/kernel-cache/features/kvm/vbus-add-stats-to-pcibridge.patch | D meta/cfg/kernel-cache/features/kvm/vbus-add-support-for-mapping-SG-entries.patch | D meta/cfg/kernel-cache/features/kvm/vbus-add-virtual-bus-definitions.patch | D meta/cfg/kernel-cache/features/kvm/vbus-add-zc-support-to-the-kvm-connector.patch | D meta/cfg/kernel-cache/features/kvm/vbus-allow-long-term-mm-acquisition-via-memctx.patch | D meta/cfg/kernel-cache/features/kvm/vbus-allow-shmsignals-to-be-named.patch | D meta/cfg/kernel-cache/features/kvm/vbus-bus-proxy-fix-sparse-warnings.patch | D meta/cfg/kernel-cache/features/kvm/vbus-client-fix-sparse-warnings.patch | D meta/cfg/kernel-cache/features/kvm/vbus-client-re-add-handle-support.patch | D meta/cfg/kernel-cache/features/kvm/vbus-client-use-a-radix-tree-for-shm-signal.patch | D meta/cfg/kernel-cache/features/kvm/vbus-config-fs-fix-sparse-warnings.patch | D meta/cfg/kernel-cache/features/kvm/vbus-create-a-null-connector.patch | D meta/cfg/kernel-cache/features/kvm/vbus-enable.scc | D meta/cfg/kernel-cache/features/kvm/vbus-enet-fix-l4ro-pool-non-atomic-allocations-in-so.patch | D meta/cfg/kernel-cache/features/kvm/vbus-enet-fix-sparse-warnings.patch | D meta/cfg/kernel-cache/features/kvm/vbus-enet-optimize-tx-complete-events.patch | D meta/cfg/kernel-cache/features/kvm/vbus-export-vbus_find-routine.patch | D meta/cfg/kernel-cache/features/kvm/vbus-fix-busmaster-support.patch | D meta/cfg/kernel-cache/features/kvm/vbus-fix-eventfd-leak-in-kvm-connector.patch | D meta/cfg/kernel-cache/features/kvm/vbus-fix-fastcall-channel-leaks-in-kvm-connector.patch | D meta/cfg/kernel-cache/features/kvm/vbus-fix-kmalloc-from-interrupt-context-to-use-GFP_A.patch | D meta/cfg/kernel-cache/features/kvm/vbus-fix-kobject_init.patch | D meta/cfg/kernel-cache/features/kvm/vbus-fix-lots-of-sparse-dubious-signed-bitfield-warn.patch | D meta/cfg/kernel-cache/features/kvm/vbus-fix-sparse-signed-bitfield-warnings.patch | D meta/cfg/kernel-cache/features/kvm/vbus-fix-various-warnings.patch | D meta/cfg/kernel-cache/features/kvm/vbus-fix-xioevent-leak-in-kvm-connector.patch | D meta/cfg/kernel-cache/features/kvm/vbus-implement-fastcall-hypercalls-in-the-pci-bridge.patch | D meta/cfg/kernel-cache/features/kvm/vbus-kvm-connector-fix-most-sparse-warnings.patch | D meta/cfg/kernel-cache/features/kvm/vbus-kvm-fix-crash-in-release-method-if-intf-is-not-.patch | D meta/cfg/kernel-cache/features/kvm/vbus-macvlan-fix-sparse-warnings.patch | D meta/cfg/kernel-cache/features/kvm/vbus-make-driver-code-properly-declared-as-GPL.patch | D meta/cfg/kernel-cache/features/kvm/vbus-pci-bridge-fix-sparse-warnings.patch | D meta/cfg/kernel-cache/features/kvm/vbus-properly-deregister-the-bus-on-shutdown.patch | D meta/cfg/kernel-cache/features/kvm/vbus-proxy-add-a-pci-to-vbus-bridge.patch | D meta/cfg/kernel-cache/features/kvm/vbus-proxy-also-uses-ioq-so-it-should-select-IOQ.patch | D meta/cfg/kernel-cache/features/kvm/vbus-register-shm-signal-events-as-standard-Linux-IR.patch | D meta/cfg/kernel-cache/features/kvm/vbus-relocate-the-connector-code.patch | D meta/cfg/kernel-cache/features/kvm/vbus-rename-config.c-to-configfs.c-to-make-room-for-.patch | D meta/cfg/kernel-cache/features/kvm/vbus-set-8-byte-alignment-for-all-u64-objects.patch | D meta/cfg/kernel-cache/features/kvm/vbus-shm-signal-shared-memory-signals.patch | D meta/cfg/kernel-cache/features/kvm/vbus-synchronize-with-cleanup-branch.patch | D meta/cfg/kernel-cache/features/kvm/vbus.cfg | D meta/cfg/kernel-cache/features/kvm/vbus.scc | D meta/cfg/kernel-cache/features/kvm/venet-Fixes-for-shutdown-and-re-registration-of-vene.patch | D meta/cfg/kernel-cache/features/kvm/venet-add-Layer-4-Reassembler-Offload-L4RO-support.patch | D meta/cfg/kernel-cache/features/kvm/venet-add-a-tx-complete-event-for-out-of-order-suppo.patch | D meta/cfg/kernel-cache/features/kvm/venet-add-eventq-protocol.patch | D meta/cfg/kernel-cache/features/kvm/venet-add-missing-ethtool-include.patch | D meta/cfg/kernel-cache/features/kvm/venet-add-pre-mapped-tx-descriptor-feature.patch | D meta/cfg/kernel-cache/features/kvm/venet-add-scatter-gather-GSO-support.patch | D meta/cfg/kernel-cache/features/kvm/venet-address-binary-compatibility-issue-introduced-.patch | D meta/cfg/kernel-cache/features/kvm/venet-cache-the-ringlen-values-at-init.patch | D meta/cfg/kernel-cache/features/kvm/venet-fix-gso.hdr_len-to-report-correct-length.patch | D meta/cfg/kernel-cache/features/kvm/venet-fix-kbuild-error.patch | D meta/cfg/kernel-cache/features/kvm/venet-fix-locking-issue-with-dev_kfree_skb.patch | D meta/cfg/kernel-cache/features/kvm/venet-fix-pageq-pointer-bug.patch | D meta/cfg/kernel-cache/features/kvm/venet-macvlan-add-new-driver-to-connect-a-venet-to-a.patch | D meta/cfg/kernel-cache/features/kvm/venet-macvlan-correctly-remove-newline-from-lower-de.patch | D meta/cfg/kernel-cache/features/kvm/venet-only-generate-linkstate-events-when-properly-e.patch | D meta/cfg/kernel-cache/features/kvm/venet-report-actual-used-descriptor-size.patch | D meta/cfg/kernel-cache/features/kvm/venet-tap-Adds-a-venet-compatible-tap-device-to-VBUS.patch | D meta/cfg/kernel-cache/features/kvm/venet-tap-add-the-ability-to-set-the-client-s-mac-ad.patch | D meta/cfg/kernel-cache/features/kvm/venet-tap-make-burstthresh-defeatable.patch | D meta/cfg/kernel-cache/features/kvm/venet-use-an-skblist-for-outstanding-descriptors.patch | D meta/cfg/kernel-cache/features/kvm/venetap-add-eventq-support.patch | D meta/cfg/kernel-cache/features/kvm/venetdev-backpressure-the-RX-path-based-on-outstandi.patch | D meta/cfg/kernel-cache/features/kvm/venetdev-fix-L4RO-resource-leak-on-shutdown.patch | D meta/cfg/kernel-cache/features/kvm/venetdev-fix-build-error.patch | D meta/cfg/kernel-cache/features/kvm/venetdev-fix-txmitigation-disable-feature.patch | D meta/cfg/kernel-cache/features/kvm/venetdev-optimize-rx-empty-wakeup.patch | D meta/cfg/kernel-cache/features/kvm/venetdev-remove-extraneous-whitespace.patch | D meta/cfg/kernel-cache/features/kvm/venetdev-seperate-common-code-out-from-venettap.patch | D meta/cfg/kernel-cache/features/kvm/venetdev-support-common-venet-netdev-routines.patch | D meta/cfg/kernel-cache/features/kvm/venetdev-support-non-linear-SKBs.patch | D meta/cfg/kernel-cache/features/kvm/venettap-acquire-and-switch-to-mm-context-within-kth.patch | D meta/cfg/kernel-cache/features/kvm/venettap-add-pre-mapped-tx-descriptor-support.patch | D meta/cfg/kernel-cache/features/kvm/venettap-add-scatter-gather-support.patch | D meta/cfg/kernel-cache/features/kvm/venettap-add-zerocopy-support.patch | D meta/cfg/kernel-cache/features/kvm/venettap-be-sure-to-initialize-tx-mitigation.patch | D meta/cfg/kernel-cache/features/kvm/venettap-disable-burstthresh-by-default.patch | D meta/cfg/kernel-cache/features/kvm/venettap-fix-BUG_ON-in-packet-decoding.patch | D meta/cfg/kernel-cache/features/kvm/venettap-fix-burstthresh-related-compiler-warning.patch | D meta/cfg/kernel-cache/features/kvm/venettap-fix-decode-return-value-to-properly-detect-.patch | D meta/cfg/kernel-cache/features/kvm/venettap-make-tx-complete-mitigation-configurable.patch | D meta/cfg/kernel-cache/features/kvm/venettap-make-vsg-cache-allocation-static.patch | D meta/cfg/kernel-cache/features/kvm/venettap-relocate-venettap-into-a-subdirectory.patch | D meta/cfg/kernel-cache/features/kvm/venettap-use-NET_IP_ALIGN-for-reserved-space-in-skb.patch | D meta/cfg/kernel-cache/features/kvm/venettap-verify-max-GSO-size.patch | M meta/cfg/kernel-cache/features/latencytop/latencytop.scc | D meta/cfg/kernel-cache/features/logbuf/size-normal.cfg | D meta/cfg/kernel-cache/features/logbuf/size-normal.scc | M meta/cfg/kernel-cache/features/lttng/lttng.cfg | M meta/cfg/kernel-cache/features/netfilter/netfilter.cfg | M meta/cfg/kernel-cache/features/netfilter/netfilter.scc | D meta/cfg/kernel-cache/features/ocf/build-proper-dependency-for-SEC-and-IXDP4XX.patch | D meta/cfg/kernel-cache/features/ocf/move-cryptodev-header-to-the-proper-public-location-.patch | D meta/cfg/kernel-cache/features/ocf/ocf-update-to-linux-26-20100325-for-4.x.patch | M meta/cfg/kernel-cache/features/ocf/ocf.scc | D meta/cfg/kernel-cache/features/oprofile/Cavium-oprofile-kernel-panic.patch | D meta/cfg/kernel-cache/features/oprofile/Fix-oprofile-backtrace-for-IA32-apps-running-on-64-b.patch | D meta/cfg/kernel-cache/features/oprofile/Fix-page-faults-incorrect-syscall-traces-in-oprofile.patch | D meta/cfg/kernel-cache/features/oprofile/Fixes-for-oprofile-for-mips-64-bit-kernels.patch | D meta/cfg/kernel-cache/features/oprofile/Oprofile-add-mxc-platform-pmu-mode-support.patch | D meta/cfg/kernel-cache/features/oprofile/Oprofile-backtrace-enhancements-for-system-call-trac.patch | D meta/cfg/kernel-cache/features/oprofile/Save-rbp-in-interrupt-stack-when-oprofile-was-config.patch | D meta/cfg/kernel-cache/features/oprofile/fix-oprofile-enhanced-backtrace-x86-to-only-trace-re.patch | D meta/cfg/kernel-cache/features/oprofile/oprofile-Enable-backtrace-for-non-integrated-MIPS-bo.patch | D meta/cfg/kernel-cache/features/oprofile/oprofile-VR5500-performance-counter-driver.patch | D meta/cfg/kernel-cache/features/oprofile/oprofile-add-a-kconfig-option-to-enable-backtrace-th.patch | D meta/cfg/kernel-cache/features/oprofile/oprofile-backtrace-across-system-calls-32-64-bit-x86.patch | D meta/cfg/kernel-cache/features/oprofile/oprofile-enhanced-MIPS-stack-crawl-algorithm.patch | D meta/cfg/kernel-cache/features/oprofile/oprofile-export-address-range-symbols-for-stack-craw.patch | D meta/cfg/kernel-cache/features/oprofile/oprofile-export-unwind_stack-for-MIPS.patch | D meta/cfg/kernel-cache/features/oprofile/oprofile-fix-mips-backtrace-logic-following-branch.patch | D meta/cfg/kernel-cache/features/oprofile/oprofile-fix-unresolved-symbols-when-loading-as-a-mo.patch | D meta/cfg/kernel-cache/features/oprofile/oprofile-limit-sampled-cpus.patch | D meta/cfg/kernel-cache/features/oprofile/oprofile-mips-64-fix-oprofile-backtrace.patch | D meta/cfg/kernel-cache/features/oprofile/oprofile-powerpc-fix-to-oprofile-backtrace-causing-d.patch | D meta/cfg/kernel-cache/features/oprofile/oprofile-provide-full-call-stack-across-user-boundar.patch | D meta/cfg/kernel-cache/features/oprofile/oprofile-statistics-per-callstack-for-PPC.patch | D meta/cfg/kernel-cache/features/oprofile/oprofile-x86-fix-to-oprofile-backtrace-causing-deadl.patch | M meta/cfg/kernel-cache/features/oprofile/oprofile.scc | M meta/cfg/kernel-cache/features/powertop/powertop.scc | D meta/cfg/kernel-cache/features/pramfs/pramfs-core-support.patch | M meta/cfg/kernel-cache/features/pramfs/pramfs.scc | M meta/cfg/kernel-cache/features/profiling/profiling.cfg | M meta/cfg/kernel-cache/features/profiling/profiling.scc | D meta/cfg/kernel-cache/features/ramconsole/ramconsole-introduce-RAM-based-console.patch | M meta/cfg/kernel-cache/features/ramconsole/ramconsole.scc | M meta/cfg/kernel-cache/features/revoke/revoke.scc | M meta/cfg/kernel-cache/features/rt/rt.scc | D meta/cfg/kernel-cache/features/serial/8250.cfg | M meta/cfg/kernel-cache/features/serial/8250.scc | M meta/cfg/kernel-cache/features/systemtap/systemtap.cfg | M meta/cfg/kernel-cache/features/systemtap/systemtap.scc | D meta/cfg/kernel-cache/features/unionfs/unionfs-2.5.4-integration.patch | M meta/cfg/kernel-cache/features/unionfs/unionfs.scc | M meta/cfg/kernel-cache/features/usb-net/usb-net.cfg | M meta/cfg/kernel-cache/features/usb-net/usb-net.scc | M meta/cfg/kernel-cache/features/vfat/FAT-Added-FAT_NO_83NAME.patch | M meta/cfg/kernel-cache/features/xip/xip.scc | D meta/cfg/kernel-cache/features/yaffs2/yaffs2-fix-semaphore-self-blocked.patch | D meta/cfg/kernel-cache/features/yaffs2/yaffs2-fix-ugly-strcopy-and-kmalloc.patch | D meta/cfg/kernel-cache/features/yaffs2/yaffs2-import-yaffs2-core-support.patch | M meta/cfg/kernel-cache/features/yaffs2/yaffs2.scc | M meta/cfg/kernel-cache/ktypes/base/base.cfg | M meta/cfg/kernel-cache/ktypes/base/base.scc | M meta/cfg/kernel-cache/ktypes/base/hardware.kcf | M meta/cfg/kernel-cache/ktypes/base/non-hardware.cfg | M meta/cfg/kernel-cache/ktypes/base/non-hardware.kcf | D meta/cfg/kernel-cache/ktypes/preempt-rt/Minor-changes-to-fs-subsytem-to-fix-build-issues.patch | D meta/cfg/kernel-cache/ktypes/preempt-rt/Remove-code-which-crept-in-via-the-rt-rt-2.6.33-mer.patch | D meta/cfg/kernel-cache/ktypes/preempt-rt/Updates-to-unionfs-to-support-preempt-rt.patch | D meta/cfg/kernel-cache/ktypes/preempt-rt/preempt-rt-rt20-applied-to-2.6.34-standard.patch | D meta/cfg/kernel-cache/ktypes/preempt-rt/preempt_rt.cfg | D meta/cfg/kernel-cache/ktypes/preempt-rt/preempt_rt.scc | D meta/cfg/kernel-cache/ktypes/standard/mips.scc | D meta/cfg/kernel-cache/ktypes/standard/omap.scc | D meta/cfg/kernel-cache/ktypes/standard/perf-force-include-of-stdbool.h.patch | M meta/cfg/kernel-cache/ktypes/standard/standard.cfg | M meta/cfg/kernel-cache/ktypes/standard/standard.scc | M meta/cfg/kernel-cache/kver | M meta/cfg/kernel-cache/patches/boot/NFS-allow-nfs-root-mount-to-use-alternate-rpc-ports.patch | M meta/cfg/kernel-cache/patches/boot/boot.scc | M meta/cfg/kernel-cache/patches/boot/mount_root-clarify-error-messages-for-when-no-rootfs.patch | M meta/cfg/kernel-cache/patches/boot/nfs-Allow-default-io-size-to-be-configured.patch | D meta/cfg/kernel-cache/patches/build/Correctly-deal-with-make-that-has-an-argument-which-.patch | D meta/cfg/kernel-cache/patches/build/Improve-kconfig-symbol-hashing.patch | M meta/cfg/kernel-cache/patches/build/arm-serialize-build-targets.patch | M meta/cfg/kernel-cache/patches/build/build.scc | D meta/cfg/kernel-cache/patches/build/kallsyms-mask-trivial-warning.patch | D meta/cfg/kernel-cache/patches/build/kbuild-Allow-quilt-patches-directory-to-be-ignored.patch | D meta/cfg/kernel-cache/patches/build/kbuild-add-Wind-River-creates-files-to-the-ignore-li.patch | D meta/cfg/kernel-cache/patches/build/kbuild-exclude-wrs-directory-from-distclean-processi.patch | D meta/cfg/kernel-cache/patches/build/kbuild-no-git-IDs-from-random-parent-trees.patch | D meta/cfg/kernel-cache/patches/build/kconfig-clean-up-output-of-gperf-for-zconf.hash.c.patch | D meta/cfg/kernel-cache/patches/build/kconfig-shut-up-stupid-gcc-warnings.patch | M meta/cfg/kernel-cache/patches/exports/exports.scc | M meta/cfg/kernel-cache/patches/misc/misc.scc | M meta/cfg/kernel-cache/patches/net/Resolve-jiffies-wrapping-about-arp.patch | D meta/cfg/kernel-cache/patches/net/fix-leap-second-message-hang.patch | M meta/cfg/kernel-cache/patches/net/net.scc | D meta/cfg/kernel-cache/small/BFS-wind-river-fixups.patch | D meta/cfg/kernel-cache/small/add-functions-for-ltt.patch | D meta/cfg/kernel-cache/small/ck-BFS-import.patch | D meta/cfg/kernel-cache/small/ck-bfs-cpufreq-tweaks.patch | D meta/cfg/kernel-cache/small/ck-change-default-HZ-to-1000.patch | D meta/cfg/kernel-cache/small/ck-cleanup-swapiness-tunable.patch | D meta/cfg/kernel-cache/small/ck-expose-vmsplit-and-lowmem.patch | D meta/cfg/kernel-cache/small/ck-force-swappiness-to-be-honest.patch | D meta/cfg/kernel-cache/small/ck-free-swapcache-whenever-we-can.patch | D meta/cfg/kernel-cache/small/ck-idleprio-tasks.patch | D meta/cfg/kernel-cache/small/ck-introduce-above_background_load.patch | D meta/cfg/kernel-cache/small/ck-lru-for-files.patch | D meta/cfg/kernel-cache/small/ck-make-swap-token-active-only-when-swap-is-more-tha.patch | D meta/cfg/kernel-cache/small/ck-no-default-250-HZ.patch | D meta/cfg/kernel-cache/small/ck-raise-maxium-HZ.patch | D meta/cfg/kernel-cache/small/ck-set-the-priority-of-kswapd-to-that-of-the-calling.patch | D meta/cfg/kernel-cache/small/ck-watermarks.patch | M meta/cfg/kernel-cache/small/small-ck.scc | M meta/cfg/kernel-cache/small/small.cfg | Deleted branch meta-temp (was 69364e8). | [INFO] validating against known patches (myqemux86-standard-meta) [##################################################] (completed in 47 seconds) | ERROR: SRCREV 1a3939eb747a635b23b4234f785795c52dce72a8 was specified, but is not reachable | ERROR: Check the BSP description for incorrect branch selection, or other errors. | WARNING: /home/trz/yocto/yocto-bsp-1.7/build/tmp/work/myqemux86-poky-linux/linux-yocto/3.17-rc4+gitAUTOINC+7df849fc7e_1a3939eb74-r0.4/temp/run.do_patch.27470:1 exit 1 from | exit 1 | ERROR: Function failed: do_patch (log file is located at /home/trz/yocto/yocto-bsp-1.7/build/tmp/work/myqemux86-poky-linux/linux-yocto/3.17-rc4+gitAUTOINC+7df849fc7e_1a3939eb74-r0.4/temp/log.do_patch.27470) ERROR: Task 72 (/home/trz/yocto/yocto-bsp-1.7/meta/recipes-kernel/linux/linux-yocto_3.17.bb, do_patch) failed with exit code '1' NOTE: Tasks Summary: Attempted 793 tasks of which 15 didn't need to be rerun and 1 failed. Waiting for 0 running tasks to finish: Summary: 1 task failed: /home/trz/yocto/yocto-bsp-1.7/meta/recipes-kernel/linux/linux-yocto_3.17.bb, do_patch Summary: There was 1 ERROR message shown, returning a non-zero exit code. Created attachment 2131 [details]
myqemux86 3.17 bsp
This patches just fine for me. From your output, you have also patched fine. But the sanity check is telling you that you are NOT building the commit chain that you think you are. What branch does your build end up on ? And does it contain the commit that the error log is indicating ? yow-bashfiel-d3 [/home/bruc...r0.4/linux]> pwd /home/bruce/poky/build/tmp/work/myqemux86-poky-linux/linux-yocto/3.17-rc5+gitAUTOINC+62a1fd6302_724ab25b08-r0.4/linux yow-bashfiel-d3 [/home/bruc...r0.4/linux]> git branch master meta standard/arm-versatile-926ejs standard/base standard/beagleboard standard/beaglebone standard/ck standard/common-pc-64/base standard/common-pc-64/rangeley standard/common-pc/base * standard/common-pc/myqemux86 standard/crownbay standard/edgerouter standard/fsl-mpc8315e-rdb standard/mti-malta32 standard/mti-malta64 standard/preempt-rt/base standard/preempt-rt/qemuppc standard/qemuppc standard/tiny/base standard/tiny/common-pc > git log 10090729fb46 724ab25b0855 Merge tag 'v3.17-rc5' into standard/base 9e82bf014195 Linux 3.17-rc5 > git show 10090729fb46 commit 10090729fb461d7f5c6de0befe35a6faf22c3a4a Author: invalid_git config <unknown@unknown> Date: Sun Sep 21 15:36:55 2014 -0400 diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig index b841180c7c74..18e69317f8d2 100644 yow-bashfiel-d3 [/home/bruc...r0.4/linux]> git branch --contains 1a3939eb747a635b23b4234f785795c52dce72a8 standard/arm-versatile-926ejs standard/base standard/beagleboard standard/beaglebone standard/ck standard/common-pc-64/base standard/common-pc-64/rangeley standard/common-pc/base * standard/common-pc/myqemux86 standard/crownbay standard/edgerouter standard/fsl-mpc8315e-rdb standard/mti-malta32 standard/mti-malta64 standard/preempt-rt/base standard/preempt-rt/qemuppc standard/qemuppc standard/tiny/base standard/tiny/common-pc Bruce (In reply to comment #23) > Created attachment 2131 [details] > myqemux86 3.17 bsp Yeah, we don't even have the same branches, below is what I have. Looks like it might be because the 3.17 recipe is still pointing to linux-yocto-dev. Are you using something local and therefore not seeing the problem. I see there's now a 3.17 repo, changing the recipe from -dev to 3.17 seems to fix the problem.. [trz@empanada linux]$ pwd /home/trz/yocto/yocto-bsp-1.7/build/tmp/work/myqemux86-poky-linux/linux-yocto/3.17-rc4+gitAUTOINC+7df849fc7e_1a3939eb74-r0.4/linux [trz@empanada linux]$ git branch master meta standard/arm-versatile-926ejs standard/base standard/base-orig standard/beagleboard standard/beaglebone standard/ck standard/common-pc-64/base standard/common-pc-64/chiefriver standard/common-pc-64/mohonpeak standard/common-pc-64/romley standard/common-pc/atom-pc standard/common-pc/base * standard/common-pc/myqemux86 standard/crownbay standard/edf standard/edgerouter standard/fishriver standard/fsl-mpc8315e-rdb standard/minnow standard/mti-malta32 standard/mti-malta64 standard/preempt-rt/base standard/preempt-rt/minnow standard/preempt-rt/qemuppc standard/preempt-rt/routerstationpro standard/qemuppc standard/routerstationpro standard/sys940x standard/tiny/base standard/tiny/common-pc standard/tiny/minnow I do have one last set of changes that will go out early this week, and yes, one of them is to use the 3.17 named repository. Good catch. So this one will go away, once I make that switch. This is resolved with the 3.17 linux-yocto tree. Created attachment 2171 [details] Improve applied patch detection The error described in comment #22 is an entirely different issue from what this bug is about. The original error, as described in comment #1 as well as #9 error output is an actual failure during patch because attempt is made to apply already applied patches, because the patch detection fails. The issue is in yocto-kernel-tools; the applied patch detection is failing for kernel trees that were created using the older, quilt-based, yocto-kernel-tools, essentially because the quilt-generated patches can be matched neither on patch-id nor on subject. The attached patch fixes the problem for me. Reopening, see comment #28. Reproduced this on 1.7.RC3 (5367855fe56db0c09b8fa7bb423b9de18d11eecc) ERROR: Function failed: do_patch (log file is located at /home/lucian/work/poky/build/tmp/work/myqemux86-poky-linux/linux-yocto/3.14.19+gitAUTOINC+fb6271a942_902f34d361-r0.13/temp/log.do_patch.2832) ERROR: Logfile of failure stored in: /home/lucian/work/poky/build/tmp/work/myqemux86-poky-linux/linux-yocto/3.14.19+gitAUTOINC+fb6271a942_902f34d361-r0.13/temp/log.do_patch.2832 Log data follows: | DEBUG: Executing shell function do_patch | Deleted branch meta-temp (was d36a7ef). | [INFO] validating against known patches (myqemux86-standard-meta) error: patch failed: drivers/misc/Kconfig:392## ] (-)(88 %)) | error: drivers/misc/Kconfig: patch does not apply | error: patch failed: drivers/misc/Makefile:36 | error: drivers/misc/Makefile: patch does not apply | ERROR. could not update git tree | ERROR: Could not apply patches for myqemux86. | ERROR: Patch failures can be resolved in the devshell (bitbake -c devshell linux-yocto) | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_patch (log file is located at /home/lucian/work/poky/build/tmp/work/myqemux86-poky-linux/linux-yocto/3.14.19+gitAUTOINC+fb6271a942_902f34d361-r0.13/temp/log.do_patch.2832) ERROR: Task 3 (/home/lucian/work/poky/meta/recipes-kernel/linux/linux-yocto_3.14.bb, do_patch) failed with exit code '1' tf, regarding the patch from attachment 2171 [details], I would like to see an Error printed about a previously applied patch, but I do not want the tools to ignore it and attempt to continue. This leads to stale meta-data and builds technical debt.
Lucian, I checked the patch in question from the wiki, and it does not apply cleanly to linux-yocto 3.14 standard/base (and therefor nothing based on that). Once I cleaned up the failed hunks and regenerated the patch, it then applied cleanly. Have you attempted that? The tools, in this case I believe, are accurately reporting that a patch fails to apply. Perhaps the wiki just needs to be updated to mention which kernel the patch applies to and note that it may need to be manually applied and conflicts resolved prior to using it with the yocto-kernel tooling? Is there any documentation on how to refresh the meta data? I'd be happy to refresh the meta data in our tree, but I can't find any instructions on how to do that. (In reply to comment #33) > Is there any documentation on how to refresh the meta data? I'd be happy to > refresh the meta data in our tree, but I can't find any instructions on how > to do that. Which tree are you using? Updating the meta-data is basically the same as creating it. In the case of patches, it's a matter of checking out the branch and applying the patches series, when it fails, investigate why the patch doesn't apply, fix it or delete it, and continue. Generally speaking, you want to ensure your patches and configuration work outside of the bitbake environment before integrating it with the recipes and such. Finally, we discourage the use of patch series for this exact reason, and this is why we provide machine branches in the linux-yocto git repository. If you haven't already, please review the kernel dev manual: http://www.yoctoproject.org/docs/1.6.1/kernel-dev/kernel-dev.html If you find it lacking in some way, please do let us know how so we can improve the docs. That's the thing, we do not have any patches. We have a kernel tree that is based on linux-yocto 3.4.11 from danny, a machine branch for our board branched of standard/base and a trivial bbappend pointing at the machine branch. But the yocto-kernel tree meta branch contains patch series, all of which are already applied in the tree (as far as I know they are below the branch point of our machine branch), and it is these patches/series that is no longer correctly detected with the newer Yocto kernel tools as applied. I suspect my best option is to create a new, empty, meta-<bsp> branch in the repo and point the bbappend at that. tf, I see. Apologies, there are a number of similar but different issues being discussed in this bug. I think I understand the issue now. I will continue the discussion with Bruce this week. (In reply to comment #28) > Created attachment 2171 [details] > Improve applied patch detection > > The error described in comment #22 is an entirely different issue from what > this bug is about. The original error, as described in comment #1 as well as > #9 error output is an actual failure during patch because attempt is made to > apply already applied patches, because the patch detection fails. > > The issue is in yocto-kernel-tools; the applied patch detection is failing > for kernel trees that were created using the older, quilt-based, > yocto-kernel-tools, essentially because the quilt-generated patches can be > matched neither on patch-id nor on subject. > > The attached patch fixes the problem for me. The new tools were explicitly tested in this configuration (old tree, new tools) .. without any errors. The attached patch breaks several of my builds, so it isn't appropriate for the tree in general. I'm on vacation until Tuesday, but will have a look at this then. FWIW, I can build the 3.14 kernel just fine with the myqemux86 bsp attachment. See below: Build Configuration: BB_VERSION = "1.24.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-13.04" TARGET_SYS = "i586-poky-linux" MACHINE = "myqemux86" DISTRO = "poky" DISTRO_VERSION = "1.7" TUNE_FEATURES = "m32 i586" TARGET_FPU = "" meta meta-yocto meta-yocto-bsp = "master:33b65e111dc6766ff5c8da8337276443f22e3de1" meta-kernel-dev = "master:cab83c881b32a18ece4d9de87419b0955ef21f8c" meta-myqemux86 = "master:33b65e111dc6766ff5c8da8337276443f22e3de1" meta-virtualization = "master:7a7254d6d0798bac1f733ede9ba69488d36921d9" meta-virtualization-local = "master:33b65e111dc6766ff5c8da8337276443f22e3de1" meta-networking meta-oe = "master:dca466c074c9a35bc0133e7e0d65cca0731e2acf" meta-skeleton = "master:33b65e111dc6766ff5c8da8337276443f22e3de1" --------------------- > pwd /home/bruce/poky/build/tmp/work/myqemux86-poky-linux/linux-yocto/3.14.19+gitAUTOINC+fb6271a942_902f34d361-r0.4/linux > git whatchanged commit 111efabc0a475414a87cabedfb678778550fcafe Author: invalid_git config <unknown@unknown> Date: Fri Oct 10 02:17:42 2014 -0400 :100644 100644 6cb388e8fb7d... 086c6abeffb6... M drivers/misc/Kconfig :100644 100644 99b9424ce31d... 808a3fc6288a... M drivers/misc/Makefile :000000 100644 000000000000... a0b33f1d1e69... A drivers/misc/yocto-testmod.c commit 902f34d36102a4b2008b776ecae686f80d307e12 Author: Paul Gortmaker <paul.gortmaker@windriver.com> Date: Mon Sep 29 12:44:25 2014 -0400 aufs: apply aufs3-mmap.patch from 3.14 branch Commit cd5f049ed8ae0908d1978562daad2111f1979eeb on branch aufs3.14 of git://git.code.sf.net/p/aufs/aufs3-standalone Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com> :100644 100644 27265a8b43c1... 75427a68a1f9... M fs/buffer.c :100644 100644 b9760628e1fd... 1bd770b4496c... M fs/proc/base.c :100644 100644 d4a35746cab9... 13971813209e... M fs/proc/nommu.c :100644 100644 3bb70c8d2bed... 2550141baa47... M fs/proc/task_mmu.c :100644 100644 678455d2d683... 0ef7ef4d82fc... M fs/proc/task_nommu.c :100644 100644 0523f114f59d... a0aed7a9fb0d... M include/linux/mm.h :100644 100644 02c23f03ed5f... 7a3b89f94774... M include/linux/mm_types.h :100644 100644 f5591302c8b2... dd8b72488ffb... M kernel/fork.c :100644 100644 bddfca7b991c... 24ed155c01e4... M mm/Makefile :100644 100644 7a13f6ac5421... f1805df81f59... M mm/filemap.c :100644 100644 2c5646f11f41... 33a7d7957b6c... M mm/fremap.c :100644 100644 539eeb96b323... 5e700b19a4b5... M mm/madvise.c :100644 100644 d46f9baf9b7c... b27a532aa90c... M mm/memory.c :100644 100644 7dfa9cf952b7... a3379bb617a2... M mm/mmap.c :100644 100644 632df4527c01... 02d770eb9fc7... M mm/msync.c :100644 100644 8740213b1647... ea7e3367683e... M mm/nommu.c :000000 100644 000000000000... fc708d2622df... A mm/prfile.c -------------------------------------------- So again. Rather than talking about bbappends that I can't see, can we upload a bbappend that points to a 3.14 tree (and SRCREV) that is showing the problem. I'll build that over the weekend and see if I can reproduce the problem. Make sure that you are running the very latest kernel tools, since some fuzzy matches was recently disabled. Changing state too neeedinfo so I can get the bbappends that I was asking about at the bottom of my last comment. Today, I've built the following, with bappends and custom BSPs that branch from an existing baseline (standard/base). - linux-yocto_3.4 - linux-yocto_3.14 And there are no issues showing up with the new tools, and the new tree, or the new tools and the existing trees. The switch away from guilt was introduced when 3.4 was still in Yocto, and it was a guilt generated tree, so as I mentioned, the new tools and old trees was an explicitly tested use case. If I can get a look at specifics, I'll be able to generate a fix that resolves this issue, but doesn't break other users. bumping to 1.8 M1, and when we track it down, I'll backport to 1.7.x I re-tested daisy, dizyy and master (b8631416f12b8a904ce3deb036f9d5ce632937b0) branches on Ubuntu 12.04 and Ubuntu 14.04 recently. The kernel is the default kernel 3.14. Here are the results: On Ubuntu 12.04, dizzy and master branches *PASSED*. but daisy branch *FAILED* with same issue in comment #1 On Ubuntu 14.04, All *PASSED* considering I have no way to reproduce this, I'm dropping the priority. There now seems to be a different result depending on what distro is being used to do the build, which is new and which makes no sense. This bug seems to have gotten out of control and nobody has a handle on it any longer and will likely have even less of a handle in M4. So I'd suggest starting from scratch again - what is the problem, and how can it be unequivocally reproduced. The last testing result doesn't clearly state either. (In reply to comment #43) > There now seems to be a different result depending on what distro is being > used to do the build, which is new and which makes no sense. > Or maybe it does make sense - the failure occurs with ubuntu 12.04 but not 14.04 - could it be a different version of git or something else? Does removing git-native from ASSUME_PROVIDED change anything? (In reply to comment #44) > (In reply to comment #43) > > There now seems to be a different result depending on what distro is being > > used to do the build, which is new and which makes no sense. > > > > Or maybe it does make sense - the failure occurs with ubuntu 12.04 but not > 14.04 - could it be a different version of git or something else? > > Does removing git-native from ASSUME_PROVIDED change anything? Yes. After remove git-native from ASSUME_PROVIDED in bitbake.conf. It works! git version information: Ubuntu 12.04: git version 1.7.9.5 Ubuntu 14.04: git version 1.9.1 Daisy brach: git version 1.9.0 And ubuntu 12.04 is a supported distro for daisy. So it looks like the reproducer should be to build the 'myqemux86 bsp' attachment on a ubuntu 12.04 system. Lowering to a medium priority now we understand the issue. We could bump the minimum git version (currently 1.7.8) if we can know which verison of git we need? Have we timed out on this issue ? Since the version of git is now new enough in all the current distros, we would have trouble seeing this now. And this doesn't seem critical enough to warrant a backport. Should we just bump the minimum git version, and call this done ? Saul to talk with Michael about installing minimum git version via backports or buildtools, then bump version and send patch Updated from git version 1.7.9.5 to git version 2.7.2. Should we consider replacing this with a currently supported distro? Michael: Thanks. Yes, I think we should look at replacing 1204 with something more recent. Saul mentioned we have some other autobuilders with older versions of git (older than 1.9.0): Debian 7 - 1.7.10.4 OpenSuSE 131 - 1.8.4.5 Centos 6 - 2.4.2 (from buildtools, 1.7.1 by default) Centos 7 - 1.8.3.1 (couldn't ssh in myself) Of these, I know the centos6 and debian 7 machines are deprecated and due replacement which leaves us with a problem on opensuse131 and centos7. We know 1.7.9.5 doesn't work due to this bug, so the question is does 1.8.3.1 work? Does 1.8.4.5 work? (In reply to comment #51) > Michael: Thanks. Yes, I think we should look at replacing 1204 with > something more recent. Saul mentioned we have some other autobuilders with > older versions of git (older than 1.9.0): > > Debian 7 - 1.7.10.4 > OpenSuSE 131 - 1.8.4.5 > Centos 6 - 2.4.2 (from buildtools, 1.7.1 by default) > Centos 7 - 1.8.3.1 (couldn't ssh in myself) > > Of these, I know the centos6 and debian 7 machines are deprecated and due > replacement which leaves us with a problem on opensuse131 and centos7. > > We know 1.7.9.5 doesn't work due to this bug, so the question is does > 1.8.3.1 work? Does 1.8.4.5 work? I don't have access to machines with those git versions to easily test. I'm not sure that anyone has a setup that can easily reproduce the failure and then start varying the git version to see if it works/fails. I have some other pressing submissions to get ready, but can pick this up later next week if it is still active. Summary of git versions in production now from oldest to newest. centos7.osl.yoctoproject.org git version 1.8.3.1 ubuntu1404.i.yoctoproject.org git version 1.9.1 opensuse132.osl.yoctoproject.org git version 2.1.4 debian8.osl.yoctoproject.org git version 2.1.4 fedora22.osl.yoctoproject.org git version 2.4.3 ubuntu1510.i.yoctoproject.org git version 2.5.0 fedora23.osl.yoctoproject.org git version 2.5.5 opensuse421.i.yoctoproject.org git version 2.6.2 I went and tested this on the centos7 autobuilder and it works. I therefore propose we increase the minimum git version to 1.8.3.1 and call this done. Sent a patch for this, hopefully close soon! |