From: Jonathan Andrews <jon@jonshouse.co.uk>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Huang Shijie <shijie8@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Random process lockup on ARM board: alsa-lib-1.0.25, FUTEX_WAIT_PRIVATE
Date: Wed, 07 Mar 2012 21:22:48 +0000 [thread overview]
Message-ID: <1331155368.14407.109.camel@jonspc> (raw)
In-Reply-To: <4F57C007.5050006@linux.intel.com>
On Wed, 2012-03-07 at 12:07 -0800, Darren Hart wrote:
>
> On 02/29/2012 01:12 AM, Huang Shijie wrote:
> > Hi ,
> >
> > I meet a similar problem with the latest futex code.
> >
> > I play the video and the processes will hang at the futex.
>
> Are either of you able to bisect the kernel?
I'm not a kernel hacker what do you mean ?
> At the very least can you
> find two kernels where it works and where it does not?
>
> Hanging on FUTEX_WAIT_PRIVATE can be the symptom for higher level
> problems including userspace locking issues and race conditions.
My workload is UDP network audio. I have compiled my code with and
without ALSA support. The version without ALSA seems to run forever, the
version with ALSA works on ARM for between a few minutes and a few
hours. On Intel the same futex stall problem occurs, but it may take
runtime of days.
I have two processes running. One RX process that takes UDP packets from
the network mixes them and presents them to ALSA as an audio stream, the
second process takes audio from the sound device and transmits it as a
UDP audio stream. The two processes are independent.
My workload is atypical as I need to both transmit and receive audio via
UDP on a 27/7 basis.
So far I have experienced the problem on 3 kernels, but I have tried
only 3 kernels it may be all 2.6 kernels that suffer.
My development PC is "Linux jonspc 2.6.32.26-175.fc12.i686 #1 SMP Wed
Dec 1 21:52:04 UTC 2010 i686 athlon i386 GNU/Linux"
My ARM board target:
ARM / # uname -a
Linux (none) 3.2.5 #2 Wed Feb 22 17:11:52 GMT 2012 armv4tl GNU/Linux
And my ARM target running its older kernel was (2.6.36).
I have an strace of the process running and stalling on the PC.
The file is 2GB, its not a fast link sorry.
http://www.jonshouse.co.uk/download/a_stop.txt
Many thanks,
Jon
next prev parent reply other threads:[~2012-03-07 21:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1329393691.6830.20.camel@jonspc>
[not found] ` <1329512682.29051.1.camel@jonspc>
[not found] ` <1329570128.6670.0.camel@jonspc>
[not found] ` <4F400BBF.9020707@ladisch.de>
[not found] ` <1329603022.1089.57.camel@jonspc>
[not found] ` <4F41FC28.1070605@ladisch.de>
[not found] ` <1329926198.22918.10.camel@jonspc>
[not found] ` <4F45167A.6080706@ladisch.de>
2012-02-24 0:29 ` Random process lockup on ARM board: alsa-lib-1.0.25, FUTEX_WAIT_PRIVATE Jonathan Andrews
2012-02-29 9:12 ` Huang Shijie
2012-03-07 20:07 ` Darren Hart
2012-03-07 21:22 ` Jonathan Andrews [this message]
2012-03-08 3:42 ` Darren Hart
2012-03-08 2:28 ` Huang Shijie
2012-03-08 3:36 ` Darren Hart
2012-03-08 4:24 ` Huang Shijie
2012-03-08 7:40 ` Darren Hart
2012-03-08 8:43 ` Huang Shijie
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=1331155368.14407.109.camel@jonspc \
--to=jon@jonshouse.co.uk \
--cc=dvhart@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shijie8@gmail.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