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: Thu, 7 Apr 2005 00:07:46 +0200 [thread overview]
Message-ID: <df9d6d4a5b63e3790ac3859a13a5b2bb@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<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: new
Distribution: Fedora Core 2
Kernel Version: 2.6.5-1.358
======================================================================
Date Submitted: 06-06-2004 23:49 CEST
Last Modified: 04-07-2005 00:07 CEST
======================================================================
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?
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
======================================================================
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-04-06 22:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 22:07 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-31 3:09 [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=df9d6d4a5b63e3790ac3859a13a5b2bb@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