From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000325]: Attempted use of arecord causes complete system lockup. Only a hard reset recovers.
Date: Sat, 31 Dec 2005 04:09:07 +0100 [thread overview]
Message-ID: <3fa6b8df0921a0f7fb7cc72c3e5c91da@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=325>
======================================================================
Reported By: meg
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 325
Category: ISA - sb16/sbawe
Reproducibility: always
Severity: crash
Priority: normal
Status: closed
Distribution: Fedora Core 2
Kernel Version: 2.6.5-1.358
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 06-06-2004 23:49 CEST
Last Modified: 12-31-2005 04:09 CET
======================================================================
Summary: Attempted use of arecord causes complete system
lockup. Only a hard reset recovers.
Description:
This is a bone stock Fedora Core 2 system. The sound card is a SB16 P&P.
Any attempted use of arecord, either from a console or xterm, results in a
complete system lockup. It is 100% reproducible. aplay can play a test
sound. alsamixer seems to work as well. The microphone can be heard
through the speakers and can be adjusted using alsamixer.
======================================================================
----------------------------------------------------------------------
jdthood - 04-07-05 00:07
----------------------------------------------------------------------
Submitter: Was there any improvement in later ALSA releases?
----------------------------------------------------------------------
rlrevell - 12-31-05 04:09
----------------------------------------------------------------------
No response
Issue History
Date Modified Username Field Change
======================================================================
06-06-04 23:49 meg New Issue
06-06-04 23:49 meg Distribution => Fedora Core 2
06-06-04 23:49 meg Kernel Version => 2.6.5-1.358
06-07-04 06:02 meg Issue Monitored: meg
04-07-05 00:07 jdthood Note Added: 0004352
12-31-05 04:09 rlrevell Status new => closed
12-31-05 04:09 rlrevell Note Added: 0007340
======================================================================
-------------------------------------------------------
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:[~2005-12-31 3:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-31 3:09 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-06 22:07 [ALSA - driver 0000325]: Attempted use of arecord causes complete system lockup. Only a hard reset recovers 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=3fa6b8df0921a0f7fb7cc72c3e5c91da@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