[oe] bitbake freeze :(

[Khem Raj]

On Tue, Sep 22, 2009 at 6:22 AM, Steffen Sledz <sledz at dresearch.de> wrote:
> Since a few days i see this crazy behavior. Sometimes bitbake freezes (everytime at the same stages if it freezes) when building a target (e.g. with "bitbake drapptempl"). top tells me that a "make all" process is running and consuming all resources of one cpu. The last lines of an strace show always something like this:
>
> ...
> 5909  stat64(".deps/drapptempl-main.Po", {st_mode=S_IFREG|0644, st_size=8, ...}) = 0
> 5909  lstat64(".deps/drapptempl-main.Tpo", {st_mode=S_IFREG|0644, st_size=32496, ...}) = 0
> 5909  lstat64(".deps/drapptempl-main.Po", {st_mode=S_IFREG|0644, st_size=8, ...}) = 0
> 5909  rename(".deps/drapptempl-main.Tpo", ".deps/drapptempl-main.Po") = 0
> 5909  close(0)                          = 0
> 5909  close(1)                          = 0
> 5909  close(2)                          = 0
> 5909  exit_group(0)                     = ?
> 5898  <... wait4 resumed> [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 5909
> 5898  --- SIGCHLD (Child exited) @ 0 (0) ---
> 5898  sigreturn()                       = ? (mask now [])
> 5898  rt_sigprocmask(SIG_BLOCK, [HUP INT QUIT TERM XCPU], NULL, 8) = 0
> 5898  rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
> 5898  stat64("drapptempl-main.o", {st_mode=S_IFREG|0644, st_size=107848, ...}) = 0
>
> The recipe for the freezing task looks like this:
>
>  DESCRIPTION = "HydraIP Linux Application Template"
>  SECTION = "console/utils"
>  PRIORITY = "optional"
>  DEPENDS = "libdrhip"
>
>  #SRCREV = "1390"
>  SRCREV = "${AUTOREV}"
>  PR = "r1"
>
>  SRC_URI="svn://something.else/repos/HydraIP/trunk/LINUX;module=drapptempl;proto=https"
>
>  PV = "svnr${SRCREV}"
>  S = "${WORKDIR}/drapptempl"
>
>  EXTRA_OECONF = "--with-libdrhip-path=${STAGING_DIR_TARGET}"
>
>  inherit autotools
>
> Any idea what's going wrong here? Or how to isolate the problem?

you could try couple of things. Firstly try to isolate if its a
bitbake problem or not
likely its not but still make sure. You can go into the workdir and
run the task script
run.do_<task> whatever it is stuck at. If it succeeeds then you know
its a problem with
bitbake if not then the build mechanism for this particular package
has problem. You might
try to disable parallel build i.e. use -j 1 to make sure that its not
some parallel build
issue.

>
> Steffen
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>