All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mike Crowe <drmikecrowe@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Debugging custom driver: BUG: pcmC0D0c:0 error
Date: Fri, 20 May 2011 09:05:59 +0200	[thread overview]
Message-ID: <s5hipt57sx4.wl%tiwai@suse.de> (raw)
In-Reply-To: <BANLkTim3_eSbp1Ax9L8w8kEXQVvdtZ9q-w@mail.gmail.com>

At Thu, 19 May 2011 16:34:59 -0400,
Mike Crowe wrote:
> 
> Hi folks,
> 
> I'm digging into a custom, embedded ALSA driver for some hardware we are
> developing.  The basic functionality (interfacing with an soc/wm8990 codec)
> is working fine.
> 
> We have a new library that we are adding which interfaces with the system
> via OSS.  In preparation, I built the vrec/vplay functions, which also use
> OSS, and they work fine with the OSS Emulation layer of ALSA.
> 
> I have enabled verbose printk and debug messages, and am seeing the
> following entries in the log file.  Since I did not have these enabled
> before I started integrating, I'm not sure if this is new, or if they have
> been there for a while.
> 
> Are these a problem, or can I ignore these?
> 
> ALSA sound/core/pcm_lib.c:318: BUG: pcmC0D0c:0, pos = 230989824, buffer size
> = 12304, period size = 769

This one looks broken.  A negative position?

> [ 2018.944000] ALSA sound/core/pcm_lib.c:318: BUG: pcmC0D0c:0, pos = 65536,
> buffer size = 65536, period size = 4096
> [ 2020.304000] ALSA sound/core/pcm_lib.c:318: BUG: pcmC0D0c:0, pos = 65536,
> buffer size = 65536, period size = 4096
> [ 2021.660000] ALSA sound/core/pcm_lib.c:318: BUG: pcmC0D0c:0, pos = 65536,
> buffer size = 65536, period size = 4096

These are just at buffer boundary.  The position must be between 0 and
(buffer_size-1).  If it's on buffer boundary, return zero from pointer
callback.


Takashi

      reply	other threads:[~2011-05-20  7:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19 20:34 Debugging custom driver: BUG: pcmC0D0c:0 error Mike Crowe
2011-05-20  7:05 ` Takashi Iwai [this message]

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=s5hipt57sx4.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=drmikecrowe@gmail.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.