From: Mike Galbraith <efault@gmx.de>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Len Brown <lenb@kernel.org>,
Venki Pallipadi <venkatesh.pallipadi@intel.com>,
Dave Jones <davej@redhat.com>
Subject: Re: 2.6.24-rt1: timing problems (was [git pull] x86/hrtimer/acpi fixes)
Date: Sun, 27 Jan 2008 05:46:08 +0100 [thread overview]
Message-ID: <1201409168.5295.26.camel@homer.simson.net> (raw)
In-Reply-To: <1201399193.18590.11.camel@cmn3.stanford.edu>
On Sat, 2008-01-26 at 17:59 -0800, Fernando Lopez-Lezcano wrote:
> Hi Ingo... back to testing.
> History:
>
> 2.6.23.x + rt has not been very usable for audio applications.
> 2.6.24-rt1: same so far.
>
> Why: Jack keeps printing "delayed..." messages and has xruns which means
> that somehow the timing is delayed more than what jack would think
> reasonable. As in the case with an old timing bug, the problem
> dissapears when booting the kernel with idle=poll. Other users of Planet
> CCRMA are able to replicate the behavior, which goes away with idle=poll
> or booting the machine with only one core. As a workaround I have been
> packaging 2.6.22.x but now I'm not able to use that as the old rt14
> patch, suitably tweaked results in a non working kernel.
>
> So it looks like, again, timing is getting skewed when the jack process
> jumps between cpus and thus jack sees timing jumps that are just not
> happenning.
>
> This is with a build based on 2.6.24 using as a base the latest Fedora
> rawhide source package plus 2.6.24-rt1.
Do you have a simple testcase? (one which doesn't entail installing
ccrma and becoming an audiophile)
-Mike
next prev parent reply other threads:[~2008-01-27 4:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 18:36 [git pull] x86/hrtimer/acpi fixes Ingo Molnar
2007-12-07 18:49 ` Fernando Lopez-Lezcano
2007-12-07 18:59 ` Ingo Molnar
2007-12-07 19:29 ` Fernando Lopez-Lezcano
2007-12-07 19:48 ` Fernando Lopez-Lezcano
2007-12-07 19:59 ` Ingo Molnar
2007-12-08 1:08 ` Fernando Lopez-Lezcano
2007-12-08 9:17 ` Ingo Molnar
2008-01-27 1:59 ` 2.6.24-rt1: timing problems (was [git pull] x86/hrtimer/acpi fixes) Fernando Lopez-Lezcano
2008-01-27 4:46 ` Mike Galbraith [this message]
2008-01-28 18:26 ` Fernando Lopez-Lezcano
2008-01-29 0:47 ` Fernando Lopez-Lezcano
2007-12-09 18:01 ` [git pull] x86/hrtimer/acpi fixes Pavel Machek
2007-12-09 18:10 ` Guillaume Chazarain
2007-12-09 18:47 ` Ingo Molnar
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=1201409168.5295.26.camel@homer.simson.net \
--to=efault@gmx.de \
--cc=davej@redhat.com \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nando@ccrma.Stanford.EDU \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
/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