From: Rich Pixley <rich.pixley@palm.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: SetScene tasks hang forever?
Date: Wed, 02 May 2012 12:16:04 -0700 [thread overview]
Message-ID: <4FA187F4.9040003@palm.com> (raw)
In-Reply-To: <4FA17FA7.9030805@windriver.com>
On 5/2/12 11:40 , Mark Hatle wrote:
> On 5/2/12 1:21 PM, Rich Pixley wrote:
>> I'm seeing a lot of builds apparently hanging forever, (the ones that
>> work seem to work within seconds - the ones that hang seem to hang for
>> at least 10's of minutes), with:
>>
>> rich@dolphin> nice tail -f Log
>> MACHINE = "qemux86"
>> DISTRO = ""
>> DISTRO_VERSION = "oe-core.0"
>> TUNE_FEATURES = "m32 i586"
>> TARGET_FPU = ""
>> meta = "master:35b5fb2dd2131d4c7dc6635c14c6e08ea6926457"
>>
>> NOTE: Resolving any missing task queue dependencies
>> NOTE: Preparing runqueue
>> NOTE: Executing SetScene Tasks
>>
>> If I run top, I see one processor pinned at 98 - 99% utilization running
>> python, but no other clues.
>>
>> Can anyone point me to doc, explain what's going on here, or point me in
>> the right direction to debug this?
> The only time I've seen "hang-like" behavior the system actually opened a
> devshell and was awaiting input. But based on your log, it doesn't look like
> that is the case.
>
> Run bitbake with -DDD option, you will get considerably more debug information
> and it might help point out what it thinks it is doing.
NOTE: Executing SetScene Tasks
DEBUG: Stamp for underlying task
12(virtual:native:/home/rich/projects/webos/openembedded-core/meta/recipes-devtools/opkg/opkg_svn.bb,
do_populate_sysroot) is current, so skipping setscene variant
DEBUG: Stamp for underlying task
16(virtual:native:/home/rich/projects/webos/openembedded-core/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb,
do_populate_sysroot) is current, so skipping setscene variant
DEBUG: Stamp for underlying task
20(virtual:native:/home/rich/projects/webos/openembedded-core/meta/recipes-devtools/makedevs/makedevs_1.0.0.bb,
do_populate_sysroot) is current, so skipping setscene variant
DEBUG: Stamp for underlying task
24(/home/rich/projects/webos/openembedded-core/meta/recipes-core/eglibc/ldconfig-native_2.12.1.bb,
do_populate_sysroot) is current, so skipping setscene variant
DEBUG: Stamp for underlying task
32(virtual:native:/home/rich/projects/webos/openembedded-core/meta/recipes-devtools/genext2fs/genext2fs_1.4.1.bb,
do_populate_sysroot) is current, so skipping setscene variant
DEBUG: Stamp for underlying task
36(virtual:native:/home/rich/projects/webos/openembedded-core/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.1.bb,
do_populate_sysroot) is current, so skipping setscene variant
DEBUG: Stamp for underlying task
40(virtual:native:/home/rich/projects/webos/openembedded-core/meta/recipes-devtools/qemu/qemu_0.15.1.bb,
do_populate_sysroot) is current, so skipping setscene variant
DEBUG: Stamp for underlying task
44(/home/rich/projects/webos/openembedded-core/meta/recipes-devtools/qemu/qemu-helper-native_1.0.bb,
do_populate_sysroot) is current, so skipping setscene variant
And then the spinning hang.
--rich
next prev parent reply other threads:[~2012-05-02 19:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 18:21 SetScene tasks hang forever? Rich Pixley
2012-05-02 18:40 ` Mark Hatle
2012-05-02 19:16 ` Rich Pixley [this message]
2012-05-02 19:40 ` Mark Hatle
2012-05-02 19:45 ` Rich Pixley
2012-05-02 19:48 ` Mark Hatle
2012-05-02 23:06 ` Richard Purdie
2012-05-06 17:36 ` Rich Pixley
2012-05-07 16:38 ` Rich Pixley
2012-05-08 12:34 ` Richard Purdie
2012-05-09 17:51 ` Rich Pixley
2012-05-09 19:52 ` Richard Purdie
2012-05-09 23:04 ` Rich Pixley
2012-05-09 23:26 ` Richard Purdie
2012-05-10 0:03 ` Rich Pixley
2012-05-09 20:32 ` Richard Purdie
2012-05-09 23:20 ` Rich Pixley
2012-05-09 23:32 ` Richard Purdie
2012-05-10 0:00 ` Rich Pixley
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=4FA187F4.9040003@palm.com \
--to=rich.pixley@palm.com \
--cc=openembedded-core@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