From: dfoley <dfoley@telus.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: soc underrun problem
Date: Wed, 18 Mar 2009 11:51:08 -0700 [thread overview]
Message-ID: <49C1429C.6060302@telus.net> (raw)
In-Reply-To: <s5h7i2ne49y.wl%tiwai@suse.de>
Takashi Iwai wrote:
> At Tue, 17 Mar 2009 21:56:06 -0700,
> dfoley wrote:
>> I'm currently having a problem with playing wave files
>>
>> root@tsi-tpcxx:~# aplay /usr/share/sounds/alsa/Front_Center.wav
>> Playing WAVE '/usr/share/sounds/alsa/Front_Center.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
>> mapped channel 10 to 2
>> underrun!!! (at least 130.662 ms long)
>> underrun!!! (at least 140.809 ms long)
>>
>> I've narrowed it down to the commit ed3da3d9a0ef13c6fe1414ec73c9c1be12747b62 in linux-next/sound-2.6-tiwai.git.
>> ALSA: Rewrite hw_ptr updaters
>>
>> The audio works fine, when I reverse this commit.
>
> Could you build with CONFIG_SND_DEBUG_XRUN and set below?
> echo 1 > /proc/asound/card0/pcm0p/xrun_debug
>
> It will show you why the playback skips. It means usually the pointer
> callback is unstable. The commit changed the xrun check more
> strictly.
>
>
> Takashi
root@tsi-tpcxx:~# echo 1 > /proc/asound/card0/pcm0p/xrun_debug
root@tsi-tpcxx:~# aplay /usr/share/sounds/alsa/Front_Center.wav
Playing WAVE '/usr/share/sounds/alsa/Front_Center.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono
mapped channel 10 to 2
hda_codec: Lost interrupts? (stream=0, delta=20004, intr_ptr=2048)
XRUN: pcmC0D0p
underrun!!! (at least 58.490 ms long)
hda_codec: Lost interrupts? (stream=0, delta=20003, intr_ptr=2048)
XRUN: pcmC0D0p
underrun!!! (at least 58.254 ms long)
hda_codec: Lost interrupts? (stream=0, delta=20004, intr_ptr=2048)
next prev parent reply other threads:[~2009-03-18 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 4:56 soc underrun problem dfoley
2009-03-18 6:25 ` Takashi Iwai
2009-03-18 18:51 ` dfoley [this message]
2009-03-19 7:40 ` Takashi Iwai
2009-03-19 7:40 ` Takashi Iwai
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=49C1429C.6060302@telus.net \
--to=dfoley@telus.net \
--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 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.