linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: tiwai@suse.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: sound skipping regression introduced in 2.6.30-rc8
Date: Thu, 11 Jun 2009 04:28:48 -0700 (PDT)	[thread overview]
Message-ID: <20090611.042848.193715083.davem@davemloft.net> (raw)
In-Reply-To: <s5hzlcflw2d.wl%tiwai@suse.de>

From: Takashi Iwai <tiwai@suse.de>
Date: Wed, 10 Jun 2009 21:37:14 +0200

> Could you set CONFIG_SND_PCM_XRUN_DEBUG=y and do
> 	# echo 1 > /proc/asound/card0/pcm0p/xrun_debug
> then check your app?  Does it work better, and get any kernel messages?

Yes, the skipping goes away and I get hw_ptr skipping kernel messages:

[61581.519051] PCM: hw_ptr skipping! (pos=10240, delta=15368, period=1024, jdelta=0/32)
[61584.420358] PCM: hw_ptr skipping! (pos=2048, delta=16328, period=1024, jdelta=2/34)
[61593.956318] PCM: hw_ptr skipping! (pos=1024, delta=15368, period=1024, jdelta=0/32)
[61596.964300] PCM: hw_ptr skipping! (pos=14336, delta=15368, period=1024, jdelta=0/32)
[61600.036292] PCM: hw_ptr skipping! (pos=14336, delta=15368, period=1024, jdelta=0/32)
[61605.454947] PCM: hw_ptr skipping! (pos=12288, delta=15368, period=1024, jdelta=0/32)

> Also, it'd be helpful if you can check whether the problem exists in
> the current sound git tree (for-linus branch), too.
>   git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git for-linus

I'm building this to test right now, will report when I try it out.

  reply	other threads:[~2009-06-11 11:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10 18:28 sound skipping regression introduced in 2.6.30-rc8 David Miller
2009-06-10 19:37 ` Takashi Iwai
2009-06-11 11:28   ` David Miller [this message]
2009-06-11 12:02   ` David Miller
2009-06-11 13:32     ` Bartlomiej Zolnierkiewicz
2009-06-11 13:56       ` Takashi Iwai
2009-06-11 14:14         ` Bartlomiej Zolnierkiewicz
2009-06-11 14:23           ` Takashi Iwai
2009-06-11 15:40             ` Bartlomiej Zolnierkiewicz
2009-06-11 16:07               ` Takashi Iwai
2009-06-11 17:36                 ` Bartlomiej Zolnierkiewicz
2009-06-11 14:02     ` Takashi Iwai
2009-06-10 19:37 ` Sven Köhler
2009-06-11  0:58   ` Takashi Iwai
2009-06-11  6:47     ` Sven Köhler
2009-06-11  8:18       ` Takashi Iwai
2009-06-11 21:38         ` Sven Köhler
2009-06-12  1:52           ` Takashi Iwai
2009-06-12 11:44             ` Bartlomiej Zolnierkiewicz
2009-06-15  8:30               ` Takashi Iwai
2009-06-15  8:39                 ` Takashi Iwai
2009-06-15  9:25                   ` David Miller
2009-06-15  9:48                     ` Takashi Iwai
2009-06-15  9:58                       ` Takashi Iwai
2009-06-15 10:11                         ` David Miller
2009-06-15 10:26                           ` Takashi Iwai
2009-06-15 18:25                         ` Sven Köhler
2009-06-15 19:15                           ` Bartlomiej Zolnierkiewicz
2009-06-15 10:09                       ` David Miller
2009-06-15  9:18                 ` David Miller

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=20090611.042848.193715083.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).