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: Fri, 11 Mar 2005 14:35:53 -0500 [thread overview]
Message-ID: <1110569754.18889.5.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!
Please try a newer CVS checkout (from today or tomorrow). I believe the
"Oops in emu10k1_efx_playback_prepare" bug could have also caused this
error.
Also, the above error message is a little buggy, as the condition does
not always represent an error.
Were you using the wavetable synth at the time?
Also, if you get the error again please post the contents
of /proc/asound/card0/voices.
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
next prev parent reply other threads:[~2005-03-11 19:35 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
2005-03-11 19:35 ` Lee Revell [this message]
-- 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=1110569754.18889.5.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.