From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0002070]: Hard lockup from aplay with low buffersizes on Tascam us-122 (snd_usb_usx2y)
Date: Wed, 26 Apr 2006 16:23:03 +0200 [thread overview]
Message-ID: <a0f6f855f969d1fbdbcf0621089b54ce@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2070>
======================================================================
Reported By: jaime
Assigned To: karsten
======================================================================
Project: ALSA - driver
Issue ID: 2070
Category: USB - usb-usx2y
Reproducibility: always
Severity: crash
Priority: normal
Status: assigned
Distribution: Gentoo ~x86
Kernel Version: 2.6.17-rc1
======================================================================
Date Submitted: 04-25-2006 23:07 CEST
Last Modified: 04-26-2006 16:23 CEST
======================================================================
Summary: Hard lockup from aplay with low buffersizes on
Tascam us-122 (snd_usb_usx2y)
Description:
Hi.
Here's the original I'm playing (440Hz sine wave):
www.carbon.eclipse.co.uk/origSine.wav
aplay --buffer-size=1024 origSine.wav sounds great:
www.carbon.eclipse.co.uk/aplay1024.wav
aplay --buffer-size=512 origSine.wav sounds bad:
www.carbon.eclipse.co.uk/aplay512.wav
aplay --buffer-size=256 origSine.wav sounds very bad:
www.carbon.eclipse.co.uk/aplay256.wav
aplay --buffer-size=128 origSine.wav gives only a very short click,
and then locks up the machine completely:
www.carbon.eclipse.co.uk/aplay128.wav
I've tried this using different usb cards/controllers, and I get the
same problem, so I think it is an alsa driver problem.
Thank you for any help you can offer.
======================================================================
----------------------------------------------------------------------
jaime - 04-26-06 16:23
----------------------------------------------------------------------
Hello again. I've just upgraded to:
Linux 2.6.17-rc2 with Alsa 1.0.11 and I still get the same problem.
Let me know if there is any more info I can provide. :-)
Issue History
Date Modified Username Field Change
======================================================================
04-25-06 23:07 jaime New Issue
04-25-06 23:07 jaime Distribution => Gentoo ~x86
04-25-06 23:07 jaime Kernel Version => 2.6.17-rc1
04-26-06 16:23 jaime Note Added: 0009514
======================================================================
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next reply other threads:[~2006-04-26 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 14:23 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-03 0:31 [ALSA - driver 0002070]: Hard lockup from aplay with low buffersizes on Tascam us-122 (snd_usb_usx2y) bugtrack
2006-05-02 19:14 bugtrack
2006-04-30 19:12 bugtrack
2006-04-30 17:35 bugtrack
2006-04-26 21:29 bugtrack
2006-04-26 21:19 bugtrack
2006-04-25 21:07 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=a0f6f855f969d1fbdbcf0621089b54ce@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