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
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?
* 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
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):
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
* 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
Am Mittwoch, 29. November 2006 08:06 schrieb Ingo Molnar:
> * Karsten Wiese <[EMAIL PROTECTED]> wrote:
> > After estimated 15 minutes more it bugged again.
> > Related dmesg translates to linux error
> > -EXDEV
> > propably caused by the following lines:
> >
> >
> > static int
Am Mittwoch, 29. November 2006 08:06 schrieb Ingo Molnar:
* Karsten Wiese [EMAIL PROTECTED] wrote:
After estimated 15 minutes more it bugged again.
Related dmesg translates to linux error
-EXDEV
propably caused by the following lines:
snip
static int
* 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 |#1): new 1107 us
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
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 26 us
* 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 the reason
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?
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 least the
* 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
* 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
* Karsten Wiese <[EMAIL PROTECTED]> wrote:
> After estimated 15 minutes more it bugged again.
> Related dmesg translates to linux error
> -EXDEV
> propably caused by the following lines:
>
>
> static int uhci_result_isochronous(struct uhci_hcd *uhci, struct urb *urb)
hm. Below are all
* Hu Gang <[EMAIL PROTECTED]> wrote:
> > thanks, applied. I'll let the PPC -rt folks sort out the hack effects.
> > Do you have CONFIG_HIGH_RES_TIMERS enabled?
> no.
>
>
> [hugang@:~]$ uname -a
> Linux hugang.soulinfo.com 2.6.19-rc6-rt8 #2 PREEMPT Wed Nov 29 0
* Karsten Wiese <[EMAIL PROTECTED]> wrote:
> Am Montag, 27. November 2006 10:49 schrieb Ingo Molnar:
> > i have released the 2.6.19-rc6-rt8 tree, which can be downloaded from
>
> I saw usb transport errors here before rebooting with
> nmi_watchdog=0
> conta
On Wed, 29 Nov 2006 07:41:09 +0100
Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
> * Hu Gang <[EMAIL PROTECTED]> wrote:
>
> > On Mon, 27 Nov 2006 10:49:27 +0100
> > Ingo Molnar <[EMAIL PROTECTED]> wrote:
> >
> > > i have released
* Hu Gang <[EMAIL PROTECTED]> wrote:
> On Mon, 27 Nov 2006 10:49:27 +0100
> Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
> > i have released the 2.6.19-rc6-rt8 tree, which can be downloaded from
> > the usual place:
> >
> > http://redhat.com
On Mon, 27 Nov 2006 10:49:27 +0100
Ingo Molnar <[EMAIL PROTECTED]> wrote:
> i have released the 2.6.19-rc6-rt8 tree, which can be downloaded from
> the usual place:
>
> http://redhat.com/~mingo/realtime-preempt/
attached patch to making it compile and works in my Powe
Am Dienstag, 28. November 2006 23:40 schrieb Karsten Wiese:
> Am Montag, 27. November 2006 10:49 schrieb Ingo Molnar:
> > i have released the 2.6.19-rc6-rt8 tree, which can be downloaded from
>
> I saw usb transport errors here before rebooting with
> nmi_watchdog=0
>
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
Am Montag, 27. November 2006 10:49 schrieb Ingo Molnar:
> i have released the 2.6.19-rc6-rt8 tree, which can be downloaded from
I saw usb transport errors here before rebooting with
nmi_watchdog=0
contained in kernel command line.
Testcase stalled within 2 minutes before change,
ti
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
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
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
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,
* 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
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
* 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
:52:00.756 XRUN callback (200).
alsa_pcm: xrun of at least 0.732 msecs
11:52:29.894 XRUN callback (201).
The test machine is an Athlon X2 4400 running FC6 x86_64 booting into a
rebuilt 2.6.19-rc6-rt8 rpm package based on Ingo's packages
(same .config except for 4KSTACKS=off
On Mon, 2006-11-27 at 10:49 +0100, Ingo Molnar wrote:
> i have released the 2.6.19-rc6-rt8 tree, which can be downloaded from
> the usual place:
>
> http://redhat.com/~mingo/realtime-preempt/
Hi, yesterday I have done a "yum -y update" and have installed rt7.
I test
i have released the 2.6.19-rc6-rt8 tree, which can be downloaded from
the usual place:
http://redhat.com/~mingo/realtime-preempt/
lots of fixes are included in -rt8. In particular the inode/dentry leak
found and fixed by Karsten Wiese (and the related OOMs reported by
others) should
i have released the 2.6.19-rc6-rt8 tree, which can be downloaded from
the usual place:
http://redhat.com/~mingo/realtime-preempt/
lots of fixes are included in -rt8. In particular the inode/dentry leak
found and fixed by Karsten Wiese (and the related OOMs reported by
others) should
On Mon, 2006-11-27 at 10:49 +0100, Ingo Molnar wrote:
i have released the 2.6.19-rc6-rt8 tree, which can be downloaded from
the usual place:
http://redhat.com/~mingo/realtime-preempt/
Hi, yesterday I have done a yum -y update and have installed rt7.
I test it with success, boot without
:52:00.756 XRUN callback (200).
alsa_pcm: xrun of at least 0.732 msecs
11:52:29.894 XRUN callback (201).
The test machine is an Athlon X2 4400 running FC6 x86_64 booting into a
rebuilt 2.6.19-rc6-rt8 rpm package based on Ingo's packages
(same .config except for 4KSTACKS=off
* 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-latency
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
* 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.2.21):
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, qjackctl
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 is a sample
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 patch and
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 the output
Am Montag, 27. November 2006 10:49 schrieb Ingo Molnar:
i have released the 2.6.19-rc6-rt8 tree, which can be downloaded from
I saw usb transport errors here before rebooting with
nmi_watchdog=0
contained in kernel command line.
Testcase stalled within 2 minutes before change,
ticks
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 [EMAIL
Am Dienstag, 28. November 2006 23:40 schrieb Karsten Wiese:
Am Montag, 27. November 2006 10:49 schrieb Ingo Molnar:
i have released the 2.6.19-rc6-rt8 tree, which can be downloaded from
I saw usb transport errors here before rebooting with
nmi_watchdog=0
contained in kernel command
On Mon, 27 Nov 2006 10:49:27 +0100
Ingo Molnar [EMAIL PROTECTED] wrote:
i have released the 2.6.19-rc6-rt8 tree, which can be downloaded from
the usual place:
http://redhat.com/~mingo/realtime-preempt/
attached patch to making it compile and works in my PowerBook G4.
Index: linux
* Hu Gang [EMAIL PROTECTED] wrote:
On Mon, 27 Nov 2006 10:49:27 +0100
Ingo Molnar [EMAIL PROTECTED] wrote:
i have released the 2.6.19-rc6-rt8 tree, which can be downloaded from
the usual place:
http://redhat.com/~mingo/realtime-preempt/
attached patch to making it compile
On Wed, 29 Nov 2006 07:41:09 +0100
Ingo Molnar [EMAIL PROTECTED] wrote:
* Hu Gang [EMAIL PROTECTED] wrote:
On Mon, 27 Nov 2006 10:49:27 +0100
Ingo Molnar [EMAIL PROTECTED] wrote:
i have released the 2.6.19-rc6-rt8 tree, which can be downloaded from
the usual place
* Karsten Wiese [EMAIL PROTECTED] wrote:
Am Montag, 27. November 2006 10:49 schrieb Ingo Molnar:
i have released the 2.6.19-rc6-rt8 tree, which can be downloaded from
I saw usb transport errors here before rebooting with
nmi_watchdog=0
contained in kernel command line.
so
* Hu Gang [EMAIL PROTECTED] wrote:
thanks, applied. I'll let the PPC -rt folks sort out the hack effects.
Do you have CONFIG_HIGH_RES_TIMERS enabled?
no.
[hugang@:~]$ uname -a
Linux hugang.soulinfo.com 2.6.19-rc6-rt8 #2 PREEMPT Wed Nov 29 09:29:43 UTC
2006 ppc GNU/Linux
[hugang
* Karsten Wiese [EMAIL PROTECTED] wrote:
After estimated 15 minutes more it bugged again.
Related dmesg translates to linux error
-EXDEV
propably caused by the following lines:
snip
static int uhci_result_isochronous(struct uhci_hcd *uhci, struct urb *urb)
hm. Below are all the
* 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 using the
* 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
56 matches
Mail list logo
