Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: andoru <andoru.blah@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: Invalid PCM pointer with CMI8738 and pcm.c buffer	underuns
Date: Sat, 5 Apr 2014 23:16:02 +0000 (UTC)	[thread overview]
Message-ID: <loom.20140406T010044-863@post.gmane.org> (raw)
In-Reply-To: CAN8ccia5hZi36dCaQ+pdSH7QaHzNopLKmcHbvK_Rfj93mgeQdA@mail.gmail.com

Raymond Yau <superquad.vortex2 <at> gmail.com> writes:


> http://www.alsa-project.org/main/index.php/XRUN_Debug
> 
> # Enable basic debugging and dump stack, check hardware pointer on the
> period update
> # Usefull to just see, if PCM stream is stopped for a reason (usually wrong
> audio process timing from scheduler)
> # And to check the values from driver
> 
> echo 11 > /proc/asound/card0/pcm0p/xrun_debug

Argh, seems the kernel I'm using doesn't have the debug options.
Any other ways around this?

> Check the system log whether the hwptr position are correct in first nine
> periods and xrun  occur on 10th period since the buffer contain 9.27
> periods when running vlc?

Which system log? Or maybe this is related to the above? I can't find
anything in any file under /var/log/ that contains anything you're talking
about. 
 
>
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/plain/Documentation
>/sound/alsa/CMIPCI.txt
> 
> cat /proc/asound/card0/cmipci
> 
> What is the model of your sound card ?

____________________________________________________
$ cat /proc/asound/card0/cmipci
C-Media CMI8738 (model 55) at 0xe000, irq 18

00: 02 00 01 00
04: d0 0d 00 00
08: 83 00 09 00
0c: 00 00 01 0a
10: c0 00 00 00
14: 00 60 c0 00
18: 00 01 80 0e
1c: 00 00 ee ee
20: 10 40 f9 00
24: 8f ff ff 06
90: 20 09 00 00
____________________________________________________


> Does it support 4 and 6 channels in windows ?

6 channels. I don't use more than 2 channels anyway.

  reply	other threads:[~2014-04-05 23:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04 16:15 Invalid PCM pointer with CMI8738 and pcm.c buffer underuns andoru
2014-04-05  6:21 ` Raymond Yau
2014-04-05 18:29   ` andoru
2014-04-05 21:55     ` Raymond Yau
2014-04-05 23:16       ` andoru [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-04-28 21:28 Andoru
2014-04-29  6:04 ` Takashi Iwai
2014-04-29 13:06   ` Andoru
2014-04-29 14:26     ` Takashi Iwai
2014-04-20 15:04 Andoru
2014-04-28 16:00 ` Takashi Iwai
2014-04-29  1:12   ` Andoru
2014-04-10 19:05 andoru
2014-04-12  4:38 ` Raymond Yau
2014-04-12 17:56   ` Andoru
2014-04-12 23:38   ` Andoru
     [not found] <CAAvHfitJ2B1sr7_6h=ww_SVGgsuy4iNLGc3CjDyiNtwdpJTSUw@mail.gmail.com>
2014-04-01 11:37 ` Clemens Ladisch
2014-04-01 18:48   ` andoru
2014-04-01 22:58     ` Raymond Yau
2014-04-02  2:24     ` andoru
2014-03-26 16:02 andoru
     [not found] ` <CAN8ccib45znh-JbH57EhfbPNQg_fginmX9Tbr=yKMmd4D=iygQ@mail.gmail.com>
     [not found]   ` <CAN8cciZkGx5XBO+u0b7V9YN8VU_rz8ckL8B=6oBFJr+-Yg8cxw@mail.gmail.com>
2014-03-26 23:23     ` Raymond Yau
2014-03-27 20:44       ` andoru
2014-03-28  4:46         ` Raymond Yau
2014-03-28  8:42           ` Clemens Ladisch
2014-03-28 14:28             ` andoru
2014-03-28 15:21               ` Clemens Ladisch

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=loom.20140406T010044-863@post.gmane.org \
    --to=andoru.blah@gmail.com \
    --cc=alsa-devel@alsa-project.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