2039 2012-02-28 18:21:56 +0000 Sometimes unable to kill bitbake with Ctrl-C 2012-03-13 11:54:31 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake unspecified x86 Multiple RESOLVED FIXED Patches our for review High major 1.2 M4 1 scott.a.garman richard.purdie poky.bs.watcher poky.watcher sgw --- --- --- oldest_to_newest 18785 0 scott.a.garman 2012-02-28 18:21:56 +0000 I'm able to reproduce this problem on hm1 using today's master branch of Poky. 1. Bitbake something non-sensical (e.g, a typo - 'bitbake usod') 2. Hit Ctrl-C repeatedly during the parsing stage. The result I see is the process hangs, and I cannot get back to my shell. If from another terminal I run killall bitbake, it gives me a bash prompt again on my terminal, but ps still shows a ton of bitbake usod processes running, which I most efficiently kill with killall python. This bug was encountered during the Yocto Developer Day intro hands-on labs, which were using Fedora 16 host OSes with all the software updates applied. hm1 runs openSUSE 11.4 with Python v 2.7. 18957 1 richard.purdie 2012-03-11 14:39:02 +0000 There appear to be two issues here, one is the shutdown() parsing function in cooker.py being called twice which will result in a hard lockup. The second is that the codeparser cache manipulation can take a long time on a many core system giving the illusion of a hang. I've sent patches for both issues to bitbake-devel along with a third patch which lowers the size of the cache file significantly. 18986 2 richard.purdie 2012-03-13 11:54:31 +0000 Fixed in http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=7bf0a790b23833a1b426d2349885459112fb5d7c and the previous commit.