On Wed, 2006-11-29 at 20:51 +0100, Ingo Molnar wrote:
> * Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
>
> > > ok, i reproduced something similar on one of my boxes and it turned
> > > out to be a tracer bug. I've uploaded -rt10, could you try it? (The
> > > xruns will likely remain, but at
On Wed, 2006-11-29 at 20:51 +0100, Ingo Molnar wrote:
> * Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
> Also, can you see the xruns/latencies with latencytest too? (That one
> might be easier to reproduce for me.)
I can do that. Is this the old latency test script?
(http://www.gardena.net/b
* Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
> > ok, i reproduced something similar on one of my boxes and it turned
> > out to be a tracer bug. I've uploaded -rt10, could you try it? (The
> > xruns will likely remain, but at least the tracer should be more
> > usable now to find out th
On Wed, 2006-11-29 at 14:43 +0100, Ingo Molnar wrote:
> * Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
>
> > > > > (japa-4096 |#0): new 17 us maximum-latency wakeup.
> > > > > ( beagled-3412 |#1): new 19 us maximum-latency wakeup.
> > > > > ( IRQ 18-1081 |#1): new
On Wed, 29 Nov 2006, Ingo Molnar wrote:
please talk to John and Thomas about GTOD interfaces. Right now the
solution used by the latency tracer is working out pretty OK - but if
something better comes along i can use that too. It's not a burning
issue though, unless you know of some bug. (i'm no
* Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
> > > > (japa-4096 |#0): new 17 us maximum-latency wakeup.
> > > > ( beagled-3412 |#1): new 19 us maximum-latency wakeup.
> > > > ( IRQ 18-1081 |#1): new 26 us maximum-latency wakeup.
> > > > ( snd-4040 |
* Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
> > I'll turn off the machine and cold boot it...)
>
> No difference, actually it looks like the regression re-regresses if I
> enable the trace... Arghhh.
yeah, that happens sometimes if some race is particularly narrow :-/
> Toggling /proc
* Daniel Walker <[EMAIL PROTECTED]> wrote:
> > i fixed this in -rt8: the latency tracer now uses the time of day
> > clocksource - pmtimer in this case. (that means function tracing is
> > slower than with the TSC, but latency figures are more reliable.)
>
> I have a patch set to make the usin
On Tue, 2006-11-28 at 13:35 -0800, Fernando Lopez-Lezcano wrote:
> On Tue, 2006-11-28 at 13:04 -0800, Fernando Lopez-Lezcano wrote:
> > On Tue, 2006-11-28 at 12:37 -0800, Fernando Lopez-Lezcano wrote:
> > > On Tue, 2006-11-28 at 21:09 +0100, Ingo Molnar wrote:
> > > > * Fernando Lopez-Lezcano <[EMA
On Tue, 2006-11-28 at 21:14 +0100, Ingo Molnar wrote:
> * Lee Revell <[EMAIL PROTECTED]> wrote:
>
> > On Tue, 2006-11-28 at 11:58 -0800, Fernando Lopez-Lezcano wrote:
> > > Hi, I'm trying out the latest -rt patch and getting alsa xruns when
> > > using jackd and jack clients. This is a sample from
On Tue, 2006-11-28 at 13:04 -0800, Fernando Lopez-Lezcano wrote:
> On Tue, 2006-11-28 at 12:37 -0800, Fernando Lopez-Lezcano wrote:
> > On Tue, 2006-11-28 at 21:09 +0100, Ingo Molnar wrote:
> > > * Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
> > >
> > > > Hi, I'm trying out the latest -rt pa
On Tue, 2006-11-28 at 12:37 -0800, Fernando Lopez-Lezcano wrote:
> On Tue, 2006-11-28 at 21:09 +0100, Ingo Molnar wrote:
> > * Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
> >
> > > Hi, I'm trying out the latest -rt patch and getting alsa xruns when
> > > using jackd and jack clients. This i
On Tue, 2006-11-28 at 21:09 +0100, Ingo Molnar wrote:
> * Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
>
> > Hi, I'm trying out the latest -rt patch and getting alsa xruns when
> > using jackd and jack clients. This is a sample from the output of
> > qjackctl / jackd (jack 0.102.25, qjackct
* Lee Revell <[EMAIL PROTECTED]> wrote:
> On Tue, 2006-11-28 at 11:58 -0800, Fernando Lopez-Lezcano wrote:
> > Hi, I'm trying out the latest -rt patch and getting alsa xruns when
> > using jackd and jack clients. This is a sample from the output of
> > qjackctl / jackd (jack 0.102.25, qjackctl 0.
On Tue, 2006-11-28 at 11:58 -0800, Fernando Lopez-Lezcano wrote:
> Hi, I'm trying out the latest -rt patch and getting alsa xruns when
> using jackd and jack clients. This is a sample from the output of
> qjackctl / jackd (jack 0.102.25, qjackctl 0.2.21):
Any improvement if you disable high res ti
* Fernando Lopez-Lezcano <[EMAIL PROTECTED]> wrote:
> Hi, I'm trying out the latest -rt patch and getting alsa xruns when
> using jackd and jack clients. This is a sample from the output of
> qjackctl / jackd (jack 0.102.25, qjackctl 0.2.21):
> (japa-4096 |#0): new 17 us maximum-la
Hi, I'm trying out the latest -rt patch and getting alsa xruns when
using jackd and jack clients. This is a sample from the output of
qjackctl / jackd (jack 0.102.25, qjackctl 0.2.21):
alsa_pcm: xrun of at least 0.034 msecs
11:38:03.681 XRUN callback (154).
delay of 18710.000 usecs e
17 matches
Mail list logo
