alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Colin Guthrie <gmane@colin.guthr.ie>
To: alsa-devel@alsa-project.org
Subject: Re: Duplicate wake-ups in pcm_lib.c
Date: Wed, 20 Jan 2010 01:24:10 +0000	[thread overview]
Message-ID: <hj5lvn$is9$1@ger.gmane.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1001182233280.4324@eeebox2.perex-int.cz>

Hi,

'Twas brillig, and Jaroslav Kysela at 18/01/10 21:39 did gyre and gimble:
> On Mon, 18 Jan 2010, Colin Guthrie wrote:
>> This is handled in our bug report here:
>> https://qa.mandriva.com/show_bug.cgi?id=57010
>>
>> For reference relating to comment 12:
>> 2.6.32.3-1mnb: First introduced the above 4 fixes.
>> 2.6.32.3-2mnb: included 7b3a177
>> 2.6.32.4-0.rc1.1mnb: included ed69c6a
>>
>> Is there something more that needs done?
> 
> Thanks for feedback. Please, provide debug information:
> 
> http://www.alsa-project.org/main/index.php/XRUN_Debug
> 
> Use 101 or 29 values for xrun_debug and try to put ksyslog messages 
> to a relation with the audiable problems.

Just following up on this on behalf of a colleage.

He's set the 101 value and this annoyingly seems to fix his problem
(well, no glitches to the ear anyway!).

However he does get the following messages:

kernel: PCM: hw_ptr skipping! [Q] (pos=1024, delta=8192, period=1024,
jdelta=0/170/0, hw_ptr=140116992/140116992)

When he does the 29 value it spams the log >one every second and he
didn't try too long to get it to fail before he switched to 101. I can
get the full log of the above too if it's useful or run the 29 test and
capture the output if it'll still help even tho it's not showing the error.

Col

-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mandriva Linux Contributor [http://www.mandriva.com/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]

  reply	other threads:[~2010-01-20  1:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-23 20:28 Duplicate wake-ups in pcm_lib.c pl bossart
2009-12-24  8:43 ` Jaroslav Kysela
2009-12-25  6:59   ` Raymond Yau
2010-01-07  4:59   ` pl bossart
2010-01-07 14:59     ` Jaroslav Kysela
2010-01-11  4:11       ` Raymond Yau
2010-01-11  7:18         ` Jaroslav Kysela
2010-01-13  6:58           ` Raymond Yau
2010-01-13  7:20             ` Jaroslav Kysela
2010-01-20  7:38               ` Raymond Yau
2010-01-20 10:42                 ` Jaroslav Kysela
2010-01-26  7:25                   ` Raymond Yau
2010-01-26  8:23                     ` Jaroslav Kysela
2010-01-11 18:36       ` pl bossart
2010-01-11 18:45         ` pl bossart
2010-01-11 18:54           ` Jaroslav Kysela
2010-01-11 18:51         ` Jaroslav Kysela
2010-01-11 20:46           ` pl bossart
2010-01-12 11:15             ` Jaroslav Kysela
2010-01-18 18:32       ` Colin Guthrie
2010-01-18 21:39         ` Jaroslav Kysela
2010-01-20  1:24           ` Colin Guthrie [this message]
2010-01-20 15:12             ` Colin Guthrie
2010-01-25 11:52               ` Colin Guthrie
2010-01-27 10:46                 ` Colin Guthrie

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='hj5lvn$is9$1@ger.gmane.org' \
    --to=gmane@colin.guthr.ie \
    --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;
as well as URLs for NNTP newsgroup(s).