[oe] Strange do_patch behaviour

Dmitry Vinokurov d.vinokuroff at gmail.com
Wed Aug 26 13:33:30 UTC 2009


Hi,

I'm still working on building OE for Phytec LPC3250 (local.conf 
attached) and faced following thing:

I've created patch file from working 2.6.27.8 kernel sources (make 
distclean and diff -Nurd then), moved it to 
'recipes/linux/linux-2.6.27.8/phy3250/', copied working .config to 
'recipes/linux/linux-2.6.27.8/phy3250/defconfig', created 2.6.27.8 
recipe based on 2.6.27 (attached). When I try to run builded kernel 
('bitbake virtual/kernel') on target board I get kernel panic (not 
syncing: Attempted to kill init). Digged a little and found that 
standard sources with applied patch differs from fetched, unpacked and 
patched by bitbake sources, that lies at 
tmp/work/phy3250-oe-linux-gnueabi/linux-2.6.27.8-r1/linux-2.6.27.8. It's 
rather strange for me, because tail of 'bitbake virtual/kernel -v -DD -c 
patch' is following:
------------
NOTE: Running task 36 of 36 (ID: 3, 
/home/raydan/work/oe/openembedded/recipes/linux/linux_2.6.27.8.bb, do_patch)
DEBUG: Parsing 
/home/raydan/work/oe/openembedded/recipes/linux/linux_2.6.27.8.bb (full)
DEBUG: BB 
/home/raydan/work/oe/openembedded/recipes/linux/linux_2.6.27.8.bb: 
handle(data)
DEBUG: BB linux.inc: handle(data, include)
DEBUG: BB :0: inheriting classes/kernel.bbclass
DEBUG: BB classes/kernel.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/linux-kernel-base.bbclass
DEBUG: BB classes/linux-kernel-base.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/module_strip.bbclass
DEBUG: BB classes/module_strip.bbclass: handle(data, include)
DEBUG: BB :0: inheriting classes/kernel-arch.bbclass
DEBUG: BB classes/kernel-arch.bbclass: handle(data, include)
DEBUG: setVarFlag(kernel_do_compile, depends, ${INITRAMFS_TASK}, data)
DEBUG: setVarFlag(do_menuconfig, nostamp, 1, data)
DEBUG: BB :0: inheriting classes/cml1.bbclass
DEBUG: BB classes/cml1.bbclass: handle(data, include)
DEBUG: setVarFlag(do_deploy, dirs, ${S}, data)
DEBUG: update_data()
DEBUG: update_data()
DEBUG: Executing task do_patch
DEBUG: update_data()
DEBUG: 
mkdirhier(/home/raydan/work/oe/build/tmp/work/phy3250-oe-linux-gnueabi/linux-2.6.27.8-r1)
DEBUG: 
mkdirhier(/home/raydan/work/oe/build/tmp/work/phy3250-oe-linux-gnueabi/linux-2.6.27.8-r1)
NOTE: Applying patch 'phy3250.patch' 
(../openembedded/recipes/linux/linux-2.6.27.8/phy3250/phy3250.patch)
DEBUG: 
mkdirhier(/home/raydan/work/oe/build/tmp/stamps/phy3250-oe-linux-gnueabi)
NOTE: Tasks Summary: Attempted 36 tasks of which 35 didn't need to be 
rerun and 0 failed.
------------
And looks like bitbake did nothing except patching, but actually it does 
(diff between manually and bitbake patched dirs is ~30000 strings, and I 
decided not to attach it:)) and as a result builded kernel fails with 
kernel panic. Diff shows, that '.pc' dir is created (and some files in 
it are forbidden for any access (0000 rights)) and not only it -- some 
other files like in arch/arm or sound/soc/lpc3xxx/ differs too. Tried to 
remove tmp/ and rebuild -- same result.

Could anybody explain this strange behaviour? I thought that patch task 
should only execute 'patch' command.

P.S.: openembedded stable/2009, bitbake 1.8.12-1 from Debian rep.

-- 
Best Regards, 
Dmitry Vinokurov 
<d.vinokuroff at gmail.com>

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: local.conf
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20090826/f0fff76c/attachment-0004.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: linux_2.6.27.8.bb
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20090826/f0fff76c/attachment-0005.ksh>


More information about the Openembedded-devel mailing list