From: Jonathan Andrews <jon@jonshouse.co.uk>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: Random process lockup on ARM board: alsa-lib-1.0.25, FUTEX_WAIT_PRIVATE
Date: Thu, 08 Mar 2012 21:42:16 +0000 [thread overview]
Message-ID: <1331242936.3126.24.camel@jonspc> (raw)
In-Reply-To: <4F591943.8040308@ladisch.de>
On Thu, 2012-03-08 at 21:40 +0100, Clemens Ladisch wrote:
> Jonathan Andrews wrote:
> > Using the static libasound without pthreads now.
> >
> > Process still stalls in same way:
> >
> > ARM / # strace -p 408
> > Process 408 attached - interrupt to quit
> > futex(0x15a684, FUTEX_WAIT, 2, NULL
>
> So it's not a call from alsa-lib.
The alsa code is a conditional compile, as is that for the /dev/dsp
device. Only the alsa version fails, the version that just takes data
from the network and mixes it does not fail.
cc udp-many-way-audio-rx.c -DARM -DALSA -lasound -lrt -lm -o udp-many-way-audio-rx_alsa_arms --static
Fails randomly
cc udp-many-way-audio-rx.c -DARM -DDUMMY -DSTATIC -o udp-many-way-audio-rx_dummy_arms --static
Dummy version, never fails. Still has network code and my audio mixer.
Its not as if I'm linking in a lot of libs...
> > An strace of a stall (intel this time) is here. Its 2GB and on a slow
> > link (sorry).
> > http://www.jonshouse.co.uk/download/a_stop.txt
>
> If only there were a tool to compress files ...
Ok, i'm pretty tired I admit it .... 30MB
http://www.jonshouse.co.uk/download/a_stop.txt.gz
>
> > The futex address 0xae5320 occurs only once at the end of the text file
> > so I have no idea what sets it up.
>
> Can't you attach gdb to your process?
I need to build an arm version, will work on that next.
> Or at least log where in your program you are?
I did that, best I can tell it enters one of these two functions but
never exists. Makes sense as these are the two conditional compiles
wrapped around #ifdef ALSA in the main loop.
http://www.jonshouse.co.uk/download/udp-many-way-audio-playsample-alsa.c
> (If strace has too much overhead, write to a variable, and run a thread
> that waits for keyboard input and prints the variable.)
The strace (now gzipped) is the same process as the arm running (and
then stalling) on the PC. It still stalls, just takes (on average)
longer to stall on the faster machine ......
Thanks,
Jon
next prev parent reply other threads:[~2012-03-08 21:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 12:01 Random process lockup on ARM board: alsa-lib-1.0.25, FUTEX_WAIT_PRIVATE Jonathan Andrews
2012-02-17 21:04 ` Jonathan Andrews
2012-02-18 13:02 ` Jonathan Andrews
2012-02-18 20:36 ` Clemens Ladisch
[not found] ` <1329603022.1089.57.camel@jonspc>
2012-02-20 7:54 ` Clemens Ladisch
[not found] ` <1329926198.22918.10.camel@jonspc>
2012-02-22 16:23 ` Clemens Ladisch
[not found] ` <1329933773.24266.44.camel@jonspc>
2012-03-08 8:53 ` Clemens Ladisch
[not found] ` <1331199625.22455.7.camel@jonspc>
[not found] ` <4F588213.2030600@ladisch.de>
[not found] ` <1331203724.22455.44.camel@jonspc>
2012-03-08 11:43 ` Clemens Ladisch
2012-03-08 13:04 ` Jonathan Andrews
2012-03-08 13:47 ` Jonathan Andrews
2012-03-08 14:35 ` Clemens Ladisch
2012-03-08 15:14 ` Jonathan Andrews
2012-03-08 15:34 ` Takashi Iwai
2012-03-08 16:42 ` Jonathan Andrews
2012-03-08 19:05 ` Jonathan Andrews
2012-03-08 20:40 ` Clemens Ladisch
2012-03-08 21:42 ` Jonathan Andrews [this message]
2012-03-14 13:18 ` Jonathan Andrews
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=1331242936.3126.24.camel@jonspc \
--to=jon@jonshouse.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).