Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Chris Rankin <rankincj@yahoo.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Lots of BUG alerts with latest CVS and Audigy2
Date: Thu, 10 Mar 2005 19:16:21 -0500	[thread overview]
Message-ID: <1110500181.15895.1.camel@mindpipe> (raw)
In-Reply-To: <20050311001056.21034.qmail@web52903.mail.yahoo.com>

On Fri, 2005-03-11 at 00:10 +0000, Chris Rankin wrote:
> Hi,
> 
> I don't know what this means, but it's a very persistent error!
> 
> Mar  9 23:06:22 volcano kernel: BUG (or not enough voices), number 1, next free 30!
> Mar  9 23:06:53 volcano last message repeated 556 times
> Mar  9 23:07:07 volcano last message repeated 268 times
> 
> Mar 11 00:06:23 volcano kernel: BUG (or not enough voices), number 1, next free 38!
> Mar 11 00:06:54 volcano last message repeated 546 times
> 
> I am using the latest alsa CVS, with Linux 2.6.11-SMP (dual P4 with HT). My soundcard is an Audigy
> 2.

Ugh.  That is a bug in the voice allocator.  It was thought to be fixed.

Can you provide a method to reproduce the problem?

Lee



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-03-11  0:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11  0:10 Lots of BUG alerts with latest CVS and Audigy2 Chris Rankin
2005-03-11  0:16 ` Lee Revell [this message]
2005-03-11 19:35 ` Lee Revell
  -- strict thread matches above, loose matches on Subject: below --
2005-03-11 23:56 Chris Rankin
2005-03-12  0:08 ` Lee Revell

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=1110500181.15895.1.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=rankincj@yahoo.com \
    /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