public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Andrews <jon@jonshouse.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Random process lockup on ARM board: alsa-lib-1.0.25, FUTEX_WAIT_PRIVATE
Date: Fri, 24 Feb 2012 00:29:57 +0000	[thread overview]
Message-ID: <1330043397.4669.44.camel@jonspc> (raw)
In-Reply-To: <4F45167A.6080706@ladisch.de>

Using kernel 3.2.5 with alsa-lib 1.0.25, all compiled with generic
Debian arm-linux-gnueabi toolchain.

arm-linux-gnueabi-gcc (Debian 4.3.2-1.1) 4.3.2
Was used to build kernel, alsa-lib and application.

Changing gcc version, kernel version or alsa-lib version makes the
problem worse or better, but ALL versions seem to suffer this problem. I
have also seen it once on Intel (but only once so far).

Something seeks broken at a lower layer than im using.  I simply don't
have the skill to debug it.

The hardware is a USB cm109 audio adapter, but the problem seems to show
on more than this one driver.

The audio application writing to alsa will freezes at random intervals,
infrequent at the moment, last one was after runtime 20H 37M 29S.  Two
processes are running, one reading from the sound device and one writing
to the sound device. I am not using threading or anything very clever
just generic alsa functions.

This is the only diagnostic I can generate so far as running the
application under strace slows it to the point it no longer functions
enough to generate the problem.

ARM / # strace -p 417
Process 417 attached - interrupt to quit
futex(0x175734, FUTEX_WAIT_PRIVATE, 2, NULL^C <unfinished ...>
Process 417 detached

ARM / # uname -a
Linux (none) 3.2.5 #2 Wed Feb 22 17:11:52 GMT 2012 armv4tl GNU/Linux
ARM / # uptime
 22:36:19 up 22:36,  0 users,  load average: 0.15, 0.16, 0.18
ARM / # cat /proc/cpuinfo 
Processor       : ARM920T rev 0 (v4l)
BogoMIPS        : 199.06
Features        : swp half thumb crunch 
CPU implementer : 0x41
CPU architecture: 4T
CPU variant     : 0x1
CPU part        : 0x920
CPU revision    : 0


Any help welcome.

Thanks,
Jon



       reply	other threads:[~2012-02-24  0:29 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               ` Jonathan Andrews [this message]
2012-02-29  9:12                 ` Random process lockup on ARM board: alsa-lib-1.0.25, FUTEX_WAIT_PRIVATE Huang Shijie
2012-03-07 20:07                   ` Darren Hart
2012-03-07 21:22                     ` Jonathan Andrews
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=1330043397.4669.44.camel@jonspc \
    --to=jon@jonshouse.co.uk \
    --cc=linux-kernel@vger.kernel.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