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: Tue, 2 May 2006 21:14:26 +0200 [thread overview]
Message-ID: <dfb1c1af97df47ded8be74a2003d0ccb@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: 05-02-2006 21:14 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.
======================================================================
----------------------------------------------------------------------
karsten - 04-30-06 21:12
----------------------------------------------------------------------
ah, glad to read nrpacks=1 helps.
I guess its not necessary to further debug this:
the driver should be changed to only allow buffersizes >= 1024,
when nrpacks!=1.
(nrpacks!=1 is a means to make things work in slowish pc anyhow.)
In the meantime,
just modify your /etc/modprobe.conf so nrpacks=1 will always be applied.
Thanks, Karsten
----------------------------------------------------------------------
jaime - 05-02-06 21:14
----------------------------------------------------------------------
Hi Karsten.
I know that you said that it's not worth debugging this, but I'm still
trying to get a stack trace, just to find out what's causing the lockup.
I'm managed to get a serial console working on another machine, and using
the nmi_watchdog, I get the following out 5 seconds after I start aplay:
BUG: NMI Watchdog detected LOCKUP on CPU0, eip c03393a4, registers:
Modules linked in: snd_usb_usx2y snd_usb_lib snd_rawmidi snd_seq_device
..]�.u�.}��...0.
That's all I get, and that was after I'd set the console logging level to
8 (using /proc/sys/kernel/printk).
I've read a lot in the last few days, but I'm not sure what is the best
tool to use, to get that elusive stack trace. What do you recommend?
Thanks
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
04-26-06 23:19 karsten Note Added: 0009526
04-26-06 23:29 karsten Note Added: 0009527
04-26-06 23:31 karsten Note Edited: 0009527
04-30-06 19:35 jaime Note Added: 0009550
04-30-06 21:12 karsten Note Added: 0009551
05-02-06 21:14 jaime Note Added: 0009578
======================================================================
-------------------------------------------------------
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-05-02 19:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 19:14 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-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-26 14:23 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=dfb1c1af97df47ded8be74a2003d0ccb@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