From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - utils 0001722]: aplay deadlocks
Date: Sat, 7 Jan 2006 09:00:50 +0100 [thread overview]
Message-ID: <df2143cf86ac41a227c61d97d5bb5299@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1722>
======================================================================
Reported By: erador
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 1722
Category: aplay/arecord
Reproducibility: always
Severity: block
Priority: normal
Status: new
======================================================================
Date Submitted: 01-07-2006 03:25 CET
Last Modified: 01-07-2006 09:00 CET
======================================================================
Summary: aplay deadlocks
Description:
Installing the nVidia display driver worsens this issue. (Not sure why).
But with that running playing anything in any application in X, causes
ALSA to freeze, it cannot be unloaded, and processes cannot be killed. It
produces about 15 aplay instances, all of which are unkillable.
So I went back to the normal nv driver, sound works and things are
normal.
I was going to test out the surround40 profile, so I thought I'd play
something via aplay, it was a working mp3, I don't know if that's
supported or not? Either way it deadlocks alsa and generates lots of
deadlocked aplay instances.
I'm using the emu10k1 driver, and xorg.
======================================================================
----------------------------------------------------------------------
rlrevell - 01-07-06 09:00
----------------------------------------------------------------------
We can't help you with binary only drivers. Please report this problem to
Nvidia.
Issue History
Date Modified Username Field Change
======================================================================
01-07-06 03:25 erador New Issue
01-07-06 03:26 erador Issue Monitored: erador
01-07-06 09:00 rlrevell Note Added: 0007510
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2006-01-07 8:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 8:00 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-07 8:01 [ALSA - utils 0001722]: aplay deadlocks bugtrack
2006-01-07 2:25 bugtrack
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=df2143cf86ac41a227c61d97d5bb5299@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.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