From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+w=401wt.eu-S1752686AbZFKN4U@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752686AbZFKN4U (ORCPT <rfc822;w@1wt.eu>);
	Thu, 11 Jun 2009 09:56:20 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751463AbZFKN4N
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Thu, 11 Jun 2009 09:56:13 -0400
Received: from cantor.suse.de ([195.135.220.2]:40514 "EHLO mx1.suse.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751457AbZFKN4M (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Thu, 11 Jun 2009 09:56:12 -0400
Date: Thu, 11 Jun 2009 15:56:14 +0200
Message-ID: <s5hocsu50xt.wl%tiwai@suse.de>
From: Takashi Iwai <tiwai@suse.de>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: David Miller <davem@davemloft.net>, linux-kernel@vger.kernel.org
Subject: Re: sound skipping regression introduced in 2.6.30-rc8
In-Reply-To: <200906111532.34169.bzolnier@gmail.com>
References: <20090610.112804.193703669.davem@davemloft.net>
	<s5hzlcflw2d.wl%tiwai@suse.de>
	<20090611.050220.179261434.davem@davemloft.net>
	<200906111532.34169.bzolnier@gmail.com>
User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/22.3
 (x86_64-suse-linux-gnu) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

At Thu, 11 Jun 2009 15:32:33 +0200,
Bartlomiej Zolnierkiewicz wrote:
> 
> On Thursday 11 June 2009 14:02:20 David Miller wrote:
> > From: Takashi Iwai <tiwai@suse.de>
> > Date: Wed, 10 Jun 2009 21:37:14 +0200
> > 
> > > 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
> > 
> > Same behavior as 2.6.30, but debugging messages are formatted differently
> > :-)
> > 
> > [ 1109.062182] PCM: Lost interrupts? (stream=0, delta=16384, intr_ptr=73728)
> > [ 1125.126123] PCM: Lost interrupts? (stream=0, delta=16384, intr_ptr=861184)
> > [ 1131.398094] PCM: Lost interrupts? (stream=0, delta=16384, intr_ptr=1178624)
> > [ 1135.579406] PCM: Lost interrupts? (stream=0, delta=16384, intr_ptr=1395712)
> > [ 1145.115367] PCM: Lost interrupts? (stream=0, delta=16384, intr_ptr=1869824)
> > [ 1152.688670] PCM: Lost interrupts? (stream=0, delta=16384, intr_ptr=2249728)
> 
> [ Just another data point. ]
> 
> I'm experiencing similar problem with the sound in recent -next kernels.

Which driver?

> Though the only debug data that I'm getting with xrun_debug == 1 is:
> 
> XRUN: pcmC0D0p:0
> XRUN: pcmC0D0p:0
> XRUN: pcmC0D0p:0
> XRUN: pcmC0D0p:0
> XRUN: pcmC0D0p:0
> 
> with xrun_debug == 3:
> XRUN: pcmC0D0p:0
> Pid: 4718, comm: audacious Not tainted 2.6.30-next-20090611-07944-gc1b019d-dirty #21
> Call Trace:

The semantics of xrun_debug proc file was a bit changed.  Now it's
bit flags, and 4 corresponds to the additional jiffies check (1 is to 
show the debug message, 2 to show stack trace).

Try to set 5 to xrun_debug.  Do you get other messages?


thanks,

Takashi