From: Colin Guthrie <gmane@colin.guthr.ie>
To: alsa-devel@alsa-project.org
Subject: Re: Duplicate wake-ups in pcm_lib.c
Date: Mon, 18 Jan 2010 18:32:02 +0000 [thread overview]
Message-ID: <hj29f0$v5d$1@ger.gmane.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1001071552060.4210@eeebox2.perex-int.cz>
Hi Jaroslav,
'Twas brillig, and Jaroslav Kysela at 07/01/10 14:59 did gyre and gimble:
> The improved and more clean fix in now in my tree:
>
> http://git.alsa-project.org/?p=alsa-kernel.git;a=commitdiff;h=1250932e48d3b698415b1f04775433cf1da688d6
>
> Note that you should apply these 4 patches (in reverse order):
>
> 4: ALSA: pcm_lib - optimize wake_up() calls for PCM I/O
> 3: ALSA: pcm_lib - cleanup & merge hw_ptr update functions
> 2: ALSA: pcm_lib - add possibility to log last 10 DMA ring buffer positions
> 1: ALSA: pcm_lib.c - convert second xrun_debug() parameter to use defines
>
> Patch #3 should definitely fix problems with large avail or delay values
> reported in PA. I finally figured the culprit (and decide to cleanup all
> relevant code rather do just another workaround). In other words, new
> hw_ptr pointer should never be less than previous one now.
Just wanted to ask about the status of this.
We included the fixes in Mandriva cooker kernel for wider testing but
some users are seeing issues.
These four *seem* to be OK, but after also adding the "something must be
really wrong" commit
(http://git.alsa-project.org/?p=alsa-kernel.git;a=commit;h=7b3a177b0d4f92b3431b8dca777313a07533a710)
folks started getting some errors.
We also added the jiffies fix commit
(http://git.alsa-project.org/?p=alsa-kernel.git;a=commit;h=ed69c6a8eef679f2783848ed624897a937a434ac)
but that didn't seem to help.
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?
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/]
next prev parent reply other threads:[~2010-01-18 18:32 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 [this message]
2010-01-18 21:39 ` Jaroslav Kysela
2010-01-20 1:24 ` Colin Guthrie
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='hj29f0$v5d$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).