Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000809]: asfxload + aconnect called before dsp used causes dsp to be locked
Date: Wed, 12 Jan 2005 18:50:30 +0100	[thread overview]
Message-ID: <ef65de31783cc2b925ee2e8eb4081908@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=809> 
======================================================================
Reported By:                vinyvat
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   809
Category:                   PCI - emu10k1
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Distribution:               Debian testing
Kernel Version:             2.6.8.1
======================================================================
Date Submitted:             01-12-2005 09:34 CET
Last Modified:              01-12-2005 18:50 CET
======================================================================
Summary:                    asfxload + aconnect called before dsp used causes
dsp to be locked
Description: 
PS: This bug is present in the alsa version in stock kernel 2.6.8.1 up to
1.0.8-rc2.

For convienience I like to have my wavetable loaded and midi connections
setup during bootup so I can use my midi keyboard by just turning on the
computer.

This worked OK with stock kernel 2.6.3 ( and whatever alsa version came
with it ).

Recently upgraded to stock 2.6.8.1 which had the modprobe
snd-emu10k1-synth freeze bug, but was able to work around this by
launching my wavetable loading script post the modprobe. Play back from my
keyboard worked great.

This is when I began to notice apps that accessed the dsp reporting that
they were locked out ( and did not produce any sound ). First would be
arts when kde started up, and then any dvd playing app ( ogle, mplayer,
xine, all of them setup to use alsa ).

Strangely though, alsaplayer still worked despite the fact that the other
apps didn't - could it be using some other way of plugin to the emu10k1
mixer ? 

Have tried upgrading to alsa-driver-1.0.7 ( which didn't play any
wavetable sounds at all - strange ), then to alsa-driver-1.0.8-rc2 ( which
does play wavetable sounds ) but none of these fixes this problem.

If I change the order of things - have artsd start up, start a dvd
playback, and then call asfxload + aconnect, then everything is mixed and
sounds great.
======================================================================

----------------------------------------------------------------------
 tiwai - 01-12-05 15:16 
----------------------------------------------------------------------
Please elaborate the procedure causing the problem.
Which command sequences did the crash?

----------------------------------------------------------------------
 vinyvat - 01-12-05 18:50 
----------------------------------------------------------------------
Done a little more testing, and this bug is dependant on the size of the
SF2. the One I put in the "reproduction" notes is huge -
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=31#127 Mb whereas
if I use a smaller one the bug does not happen.

Will update with exact reproduction steps when I get from work.

Issue History
Date Modified  Username       Field                    Change              
======================================================================
01-12-05 09:34 vinyvat        New Issue                                    
01-12-05 09:34 vinyvat        Distribution              => Debian testing  
01-12-05 09:34 vinyvat        Kernel Version            => 2.6.8.1         
01-12-05 15:16 tiwai          Note Added: 0003171                          
01-12-05 18:50 vinyvat        Note Added: 0003175                          
======================================================================




-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

             reply	other threads:[~2005-01-12 17:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12 17:50 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-30 22:04 [ALSA - driver 0000809]: asfxload + aconnect called before dsp used causes dsp to be locked bugtrack
2005-09-14 14:19 bugtrack
2005-01-13 17:58 bugtrack
2005-01-13 11:41 bugtrack
2005-01-13  5:42 bugtrack
2005-01-12 14:16 bugtrack
2005-01-12  8:34 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=ef65de31783cc2b925ee2e8eb4081908@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