From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000151]: Lockup on Envy24ht/ice1724 when recording with some format/rate combos
Date: Mon, 6 Jun 2005 11:00:52 +0200 [thread overview]
Message-ID: <5dd96bb9a9499681ffb8018be5d660d6@bugtrack.alsa-project.org> (raw)
The following issue has been RESOLVED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=151>
======================================================================
Reported By: patricklang
Assigned To: perex
======================================================================
Project: ALSA - driver
Issue ID: 151
Category: PCI - ice1724
Reproducibility: always
Severity: crash
Priority: normal
Status: resolved
Distribution: Slackware 9.1
Kernel Version: 2.6.4
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 03-23-2004 06:05 CET
Last Modified: 06-06-2005 11:00 CEST
======================================================================
Summary: Lockup on Envy24ht/ice1724 when recording with some
format/rate combos
Description:
arecord -f S32_LE -r 48000 -c 2 file.wav
(also other rates like 96000)
records just fine, but crashes after a while. S16_LE/44100 and S32_LE
lock or crash (with stack trace) almost immediately. S32_LE/48k and
S32_LE/96k seem stable (at least for the 20-30 seconds I recorded)
======================================================================
----------------------------------------------------------------------
tiwai - 05-24-05 12:29
----------------------------------------------------------------------
The version reported here is way too old...
Try 1.0.9rc4.
----------------------------------------------------------------------
perex - 06-06-05 11:00
----------------------------------------------------------------------
No response from reporter. It might be a system specific PCI bus related
problem.
Issue History
Date Modified Username Field Change
======================================================================
03-23-04 06:05 patricklang New Issue
03-23-04 06:05 patricklang Distribution => Slackware 9.1
03-23-04 06:05 patricklang Kernel Version => 2.6.4
03-23-04 19:02 perex Status new => assigned
03-23-04 19:02 perex Assigned To => perex
05-08-05 14:24 ungod Note Added: 0004609
05-24-05 12:29 tiwai Note Added: 0004719
06-06-05 11:00 perex Status assigned => resolved
06-06-05 11:00 perex Resolution open => fixed
06-06-05 11:00 perex Note Added: 0004902
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
next reply other threads:[~2005-06-06 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 9:00 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-24 10:29 [ALSA - driver 0000151]: Lockup on Envy24ht/ice1724 when recording with some format/rate combos bugtrack
2005-05-08 12:24 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=5dd96bb9a9499681ffb8018be5d660d6@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