From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: bitbake freeze :(
Date: Tue, 22 Sep 2009 14:38:17 -0400 [thread overview]
Message-ID: <20090922183817.GC18271@denix.org> (raw)
In-Reply-To: <f96d234e0909221128v65e7f834wc1687fe5fdf5136b@mail.gmail.com>
On Tue, Sep 22, 2009 at 02:28:22PM -0400, Cliff Brake wrote:
> On Tue, Sep 22, 2009 at 9:22 AM, Steffen Sledz <sledz@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.
>
> I had an issue recently where opkg was prompting the user to overwrite
> a file in the rootfs phase. I would ctrl-C bitbake when it appeared
> to be hung, but soon learned there were additional bitbake processes
> still running. When I ran killall bitbake, the error message showed
> up. You might find something by running bitbake with -DDDD.
Now, that you mentioned it, I have also seen it before! There was a file clash
between 2 recipes providing the same file, so opkg was waiting for the user
input asking to overwrite the file during the rootfs step. But opkg I/O is
being redirected, so it appears that bitbake is hung. I found out about the
problem from the rootfs log file in the tmp/work directory, where the
output is being redirected to... :)
--
Denys
next prev parent reply other threads:[~2009-09-22 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 13:22 bitbake freeze :( Steffen Sledz
2009-09-22 17:51 ` Khem Raj
2009-09-23 7:32 ` Steffen Sledz
2009-09-23 23:44 ` Khem Raj
2009-09-22 18:28 ` Cliff Brake
2009-09-22 18:38 ` Denys Dmytriyenko [this message]
2009-09-23 7:19 ` Steffen Sledz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090922183817.GC18271@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox