From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Ingo Molnar <mingo@elte.hu>
Cc: nando@ccrma.Stanford.EDU, "Linux-Kernel," <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.19-rc6-rt7: Kernel BUG at kernel/rtmutex.c:672
Date: Tue, 28 Nov 2006 13:36:19 -0800 [thread overview]
Message-ID: <1164749780.15887.56.camel@cmn3.stanford.edu> (raw)
In-Reply-To: <20061128200611.GB25364@elte.hu>
On Tue, 2006-11-28 at 21:06 +0100, Ingo Molnar wrote:
> * Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU> wrote:
>
> > (a normal non-root user was left logged in and was running jackd with
> > realtime privileges, irqs' priority reordered with the rtirq script -
> > I was getting, and still are under -rt8, lots of audio xruns but
> > that's for another thread).
>
> do you get those xruns even with maxcpus=1? I.e. is it an SMP-only
> regression - or is UP affected too? [if it's UP then it would be simpler
> to trace that xrun]
It appears to be smp related, I just booted with maxcpus=1 and I'm
seeing a lot less in terms of xruns (three so far in the range 0.029 to
0.041 ms).
-- Fernando
prev parent reply other threads:[~2006-11-28 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 18:11 Fernando Lopez-Lezcano
2006-11-28 20:05 ` Ingo Molnar
2006-11-28 20:06 ` Ingo Molnar
2006-11-28 21:36 ` Fernando Lopez-Lezcano [this message]
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=1164749780.15887.56.camel@cmn3.stanford.edu \
--to=nando@ccrma.stanford.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®