[yocto] A lot of, seemingly, hung tasks

Chris Hallinan challinan at gmail.com
Mon Apr 11 18:52:55 PDT 2016


I have very occasionally hit hung tasks, but I was usually able to identify
the exact task which was hanging, it was never "many".  Note that some
tasks which may appear "hung" may be waiting for a dependency to complete.
You could try some brute force debugging...set these in local.conf:

BB_NUMBER_THREADS = "1"
PARALLEL_MAKE = "-j1"

Then try building again, and yes it will take a long time.

if something is actually hanging, it would be useful to know what task, not
only the bitbake "task" but the actual process as reported by ps.  A
bitbake "task" can spawn many processes as it works to complete it's job.

In the past, once I found the hanging process, strace usually helped me
discover why.

You mention a "low-end" 2-core machine...RAM is everything.  If you're
running Linux out of memory, you get what you deserve <grin>

Remember, poky-tiny refers to the resulting distribution you are building,
not the machine you want to build it on ;)

-Chris



On Mon, Apr 11, 2016 at 9:38 PM, Ronald Oakes <ronaldo at brc2.com> wrote:

> It looks like it is hanging fairly consistently during the
> gcc-cross-initial-x86_64-5.2.0-r0 do_compile or do_install steps.
> I've tried stopping, cleaning, and just building
> gcc-cross-initial-x86_64, but it still hangs.
>
> I'm going to try a 32 bit build just to see if I can get past this.
>
> Ron Oakes
>
> On Mon, Apr 11, 2016 at 12:35 PM, Andre McCurdy <armccurdy at gmail.com>
> wrote:
> > On Mon, Apr 11, 2016 at 11:22 AM, Ronald Oakes <ronaldo at brc2.com> wrote:
> >> Over the weekend, I upgraded my connected development platform to
> >> Debian 8.4.0 from Centos 7.
> >>
> >> However, today I have yet to make a successful poky-tiny build for
> >> either coreI7-64 or qemux86-64.  In each case, I've aborted the build
> >> after one or more tasks has stopped doing anything for 30 minutes or
> >> more.
> >>
> >> I define "stopped doing anything" as having not touched a file in 30
> >> minutes, while the CPU utilization (on this 2 core, low end, ASUS
> >> VivoPC) drops very low.
> >>
> >> I've tried re-running the offending recipes and tasks individually,
> >> and cleaning and restarting from scratch, but I keep ending up with
> >> something hung.
> >>
> >> Any ideas what is up, and, more importantly, what I should do to
> resolve it?
> >
> > Have you used bitbake with the "--debug" option or run "ps axf" or
> > similar to see which tasks or commands are hanging?
> >
> >> Ron Oakes
> >> --
> >> _______________________________________________
> >> yocto mailing list
> >> yocto at yoctoproject.org
> >> https://lists.yoctoproject.org/listinfo/yocto
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
Life is like Linux - it never stands still.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20160411/3a6a28d2/attachment.html>


More information about the yocto mailing list