From: "Frank Svendsbøe" <frank.svendsboe@gmail.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Scott Wood <scottwood@freescale.com>, Detlev Zundel <dzu@denx.de>
Subject: Re: Problem with futex call on 8xx
Date: Sat, 26 Sep 2009 14:52:29 +0200 [thread overview]
Message-ID: <1ba63b520909260552q6c4da364t7c41082165a9fb@mail.gmail.com> (raw)
In-Reply-To: <1ba63b520909260500k3b7a0ed1l2d75116053ae5522@mail.gmail.com>
I'll answer myself, since I just found the solution to the problem -
with help from 'kos_tom'
at #uclibc on freenode.
The problem is caused by a missing 'CONFIG_FUTEX=3Dy' in the defconfig
for our target.
The system we're developing is based on the Adder port by Scott Wood, which=
is
also missing this, so a patch should be committed for this and
possible other 8xx targets
as well.
Best regards,
Frank
On Sat, Sep 26, 2009 at 2:00 PM, Frank Svendsb=F8e
<frank.svendsboe@gmail.com> wrote:
> Hi
> I'm having a problem with ~100% CPU load on MPC8xx when calling
> pthread_cond_wait.
> Running strace, I get:
>
> futex(0x10040d5c, FUTEX_WAIT, 1, NULL) =A0=3D -1 ENOSYS (Function not imp=
lemented)
>
> .. and this call is inifinitely repeating, which explains the high load.
>
> I'm running Linux 2.6.26-rc2 (not newer due to the slowdown problem
> introduced by commit
> 8d30c14cab30d405a05f2aaceda1e9ad57800f36, as pointed out by Rex Feany
> this week), and
> glibc v2.6 (part of ELDK 4.2).
>
> Is this a problem due to an error in the futex implementation in
> glibc, or a kernel problem?
>
> Best regards,
> Frank
>
prev parent reply other threads:[~2009-09-26 12:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-26 12:00 Problem with futex call on 8xx Frank Svendsbøe
2009-09-26 12:52 ` Frank Svendsbøe [this message]
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=1ba63b520909260552q6c4da364t7c41082165a9fb@mail.gmail.com \
--to=frank.svendsboe@gmail.com \
--cc=dzu@denx.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.com \
/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