From: Benny Sjostrand <gorm@cucumelo.org>
To: alsa-devel@lists.sourceforge.net
Subject: Bug in pcm_lib.c ?? (using Xmms)
Date: Sun, 08 Dec 2002 13:45:40 +0100 [thread overview]
Message-ID: <3DF33EF4.5060207@cucumelo.org> (raw)
Hi!
Just updated CVS tree and recompiled. Everything works OK execpt that I
got this message in log
when using Xmms with ALSA-plugin and OSS-plugin. Using aplay the message
dont apear.
Dec 8 13:40:16 cactus kernel: ALSA ../alsa-kernel/core/pcm_lib.c:176:
BUG: stream = 0, pos = 0x4000, buffer size = 0x4000, period size = 0x200
Dec 8 13:40:16 cactus kernel: ALSA ../alsa-kernel/core/pcm_lib.c:176:
BUG: stream = 0, pos = 0x4000, buffer size = 0x4000, period size = 0x200
Dec 8 13:40:16 cactus kernel: ALSA ../alsa-kernel/core/pcm_lib.c:110:
BUG: stream = 0, pos = 0x4000, buffer size = 0x4000, period size = 0x200
Dec 8 13:40:16 cactus kernel: ALSA ../alsa-kernel/core/pcm_lib.c:176:
BUG: stream = 0, pos = 0x4000, buffer size = 0x4000, period size = 0x200
Dec 8 13:40:16 cactus kernel: ALSA ../alsa-kernel/core/pcm_lib.c:176:
BUG: stream = 0, pos = 0x4000, buffer size = 0x4000, period size = 0x200
Dec 8 13:40:16 cactus kernel: ALSA
../../alsa-kernel/pci/cs46xx/dsp_spos_scb_lib.c:226:
cs46xx_dsp_proc_free_scb_desc: freeing PCMReader_SCB0
Dec 8 13:40:16 cactus kernel: ALSA
../../alsa-kernel/pci/cs46xx/dsp_spos_scb_lib.c:226:
cs46xx_dsp_proc_free_scb_desc: freeing SrcTask_SCB0
With the ALSA-plugin I got the message only one time, with the
OSS-plugin it apears about a 1000 of times.
(have not done any changes to the cs46xx driver yet, except what's in
current CVS ;) )
/Benny
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next reply other threads:[~2002-12-08 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-08 12:45 Benny Sjostrand [this message]
2002-12-08 18:13 ` Bug in pcm_lib.c ?? (using Xmms) Jaroslav Kysela
2002-12-08 22:25 ` Benny Sjostrand
2002-12-09 0:59 ` Benny Sjostrand
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=3DF33EF4.5060207@cucumelo.org \
--to=gorm@cucumelo.org \
--cc=alsa-devel@lists.sourceforge.net \
/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.