public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Raymond <rayau@netvigator.com>
To: alsa-devel@lists.sourceforge.net
Cc: openvortex-dev@nongnu.org
Subject: Re: [ALSA - driver 0001047]: module hangs at seemingly random times
Date: Sun, 31 Jul 2005 15:59:26 +0800	[thread overview]
Message-ID: <42EC84DE.4050306@netvigator.com> (raw)
In-Reply-To: <50ce26d334ea87a34d7e9e58d1d69a87@bugtrack.alsa-project.org>


If there are 16 instances of aplay playing mono stream.

What error will be returned by snd_pcm_open() for the 17th instance of 
aplay ?



alsa-kernel/pci/au88x0/au8810.h

#define NR_ADB   0x10

alsa-kernel/pci/au88x0/au8830.h

#define NR_ADB   0x20


alsa-kernel/pci/au88x0/au88x0.c

	if ((err = snd_vortex_new_pcm(chip, VORTEX_PCM_ADB, NR_ADB)) < 0) {
		snd_card_free(card);
		return err;
	}



bugtrack@alsa-project.org wrote:
> A NOTE has been added to this issue.
> ======================================================================
> <https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1047> 
> ======================================================================
> Reported By:                alien999999999
> Assigned To:                mjander
> ======================================================================
> Project:                    ALSA - driver
> Issue ID:                   1047
> Category:                   PCI - au88x0
> Reproducibility:            sometimes
> Severity:                   block
> Priority:                   normal
> Status:                     assigned
> Distribution:               Mandrake
> Kernel Version:             2.6.7
> ======================================================================
> Date Submitted:             04-12-2005 20:43 CEST
> Last Modified:              04-12-2005 20:51 CEST
> ======================================================================
> Summary:                    module hangs at seemingly random times
> Description: 
> sometimes i start playing a song, and it starts playing a few second or so
> and hangs, then i kill the application and modprobe -r all sound modules
> and modprobe them again to make it work again.
> 
> BUT: sometimes not only that happens, but also when i try to kill the apps
> it will not kill. when that happens, all kill, killall, top, ps aux
> commands hang at the command line and cannot be killed by CTRL-C or
> otherwise, i have been able to see that when i stopped my display
> managener I did an lsmod and it gave something like this:
> 
> snd-pcm-oss            59752  11
> snd-mixer-oss          20480  1 snd-pcm-oss
> snd-au8810             43760  220
> snd-ac97-codec         83408  1 snd-au8810
> snd-pcm               108172  112 snd-pcm-oss,snd-au8810,snd-ac97-codec
> snd-page-alloc         10384  1 snd-pcm
> gameport                3840  1 snd-au8810
> snd-mpu401-uart        11904  1 snd-au8810
> 
> 
> as you can see the snd-au8810 module seem to have an impossible number of
> "dependencies" (i think has to do with the number of unclosed sound-apps
> trying to be played; this could be since gaim is programmed to execute an
> 'aplay %s')
> 
> i've had this major crash below only 3 times; and the logs didn't detect
> anything specific at the time. the only thing the logs mentioned at that
> time was an ntpd sync going on; so the only thing i can think of is that
> at a certain moment when a sync is going on, some kind of lock is holding
> cause this to happen... the only thing that i can do to fix this is
> reset...
> 
> it is interesting to note that i also have an snd-emu10k1 as second card,
> which never gave problems like this, and i am always able to "modprobe -r
> snd-emu10k1" ...
> ======================================================================
> 
> ----------------------------------------------------------------------
>  alien999999999 - 04-12-05 20:48 
> ----------------------------------------------------------------------
> i forgot to note that i have the mdk 10.1 x86_64 distro and my version has
> a few 64bit fixes to get past kernel hangs and kernel oopses
> 
> ----------------------------------------------------------------------
>  alien999999999 - 04-12-05 20:51 
> ----------------------------------------------------------------------
> i have attached the changed files (since i don't have a CVS version of alsa
> to diff against)
> 
> these files are located in the alsa-driver-1.0.8/alsa-kernel/pci/au88x0/
> path
> 
> Issue History
> Date Modified  Username       Field                    Change              
> ======================================================================
> 04-12-05 20:43 alien999999999 New Issue                                    
> 04-12-05 20:43 alien999999999 Distribution              => Mandrake        
> 04-12-05 20:43 alien999999999 Kernel Version            => 2.6.7           
> 04-12-05 20:48 alien999999999 Note Added: 0004461                          
> 04-12-05 20:49 alien999999999 File Added: au88x0.c                         
> 04-12-05 20:49 alien999999999 File Added: au88x0.h                         
> 04-12-05 20:50 alien999999999 File Added: au88x0_core.c                    
> 04-12-05 20:50 alien999999999 File Added: au88x0_mixer.c                    
> 04-12-05 20:51 alien999999999 Note Added: 0004462                          
> ======================================================================
> 
> 
> 


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

  parent reply	other threads:[~2005-07-31  7:59 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12 18:51 [ALSA - driver 0001047]: module hangs at seemingly random times bugtrack
2005-04-30 10:24 ` Raymond
2005-06-18 13:51 ` Raymond
2005-07-31  7:59 ` Raymond [this message]
2005-07-31 12:38   ` [Openvortex-dev] " Alien
2005-07-31 17:15     ` Raymond
  -- strict thread matches above, loose matches on Subject: below --
2006-07-31 10:23 bugtrack
2006-07-13 14:16 bugtrack
2006-06-29 15:38 bugtrack
2006-06-29  7:55 bugtrack
2006-06-29  2:41 bugtrack
2006-06-28  1:46 bugtrack
2006-06-27  6:22 bugtrack
2006-06-26 12:55 bugtrack
2006-06-26  0:46 bugtrack
2006-06-25  5:04 bugtrack
2006-04-11 16:54 bugtrack
2006-04-11 16:36 bugtrack
2006-04-10 17:05 bugtrack
2006-04-10 17:01 bugtrack
2006-04-10 14:45 bugtrack
2006-04-10 14:43 bugtrack
2006-04-10 14:40 bugtrack
2006-04-10 14:07 bugtrack
2006-03-29 15:48 bugtrack
2006-03-26  7:55 bugtrack
2006-03-22  3:09 bugtrack
2006-03-22  3:00 bugtrack
2006-03-22  1:38 bugtrack
2006-03-22  1:28 bugtrack
2006-03-21 17:01 bugtrack
2006-03-21  1:02 bugtrack
2006-03-01  6:39 bugtrack
2006-02-13 15:41 bugtrack
2006-02-05  4:28 bugtrack
2006-01-19 12:51 bugtrack
2006-01-18 14:51 bugtrack
2006-01-17 11:27 bugtrack
2006-01-14  3:53 bugtrack
2006-01-13 17:18 bugtrack
2006-01-13 12:51 bugtrack
2006-01-06 16:17 bugtrack
2006-01-05  6:21 bugtrack
2006-01-04 21:08 bugtrack
2006-01-03  3:04 bugtrack
2005-10-27  0:27 bugtrack
2005-08-24  9:13 bugtrack
2005-04-12 18:48 bugtrack
2005-04-12 18:43 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=42EC84DE.4050306@netvigator.com \
    --to=rayau@netvigator.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=openvortex-dev@nongnu.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