All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
To: Mark Knecht <markknecht@gmail.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>, Lee Revell <rlrevell@joe-job.com>
Subject: Re: 2.6.15-rt2 - repeatable xrun - no good data in trace
Date: Sun, 08 Jan 2006 23:11:21 +0100	[thread overview]
Message-ID: <43C18E09.9060600@stud.feec.vutbr.cz> (raw)
In-Reply-To: <5bdc1c8b0601081404n2a163ce1ya21919800546dfc8@mail.gmail.com>

Mark Knecht wrote:
> On 1/8/06, Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
>>>>  I did run across a way that I can create a repeatable xrun on my
>>>>AMD64 machine by burning a CD in k3b while Jack is running.
>>>>Unfortunately I do not see any good trace data in dmesg when I do it.
>>>Maybe your cdrecord is running with realtime priority higher than Jack?
>>>Michal
>>cdrecord does run with SCHED_RR/99 when started with proper privileges.
>>
> Ah, then it's likely that this isn't a real problem and it would be
> expected to cause an xrun?

By running cdrecord with a higher priority than Jack, you're telling the 
system that burning the CD is more important than not getting xruns in Jack.

> Anyway, it seems strange that the trace doesn't show anything. I
> suppose that's because cdrecord just grabs a lot of time at a higher
> priority than Jack and Jack ends up not getting serivces at all for
> 5-10mS?

I guess that's exactly what's happening.

> OK, back to the drawing board about debugging my problems!

Try running cdrecord as a normal user and don't give it SUID root.

Michal

  reply	other threads:[~2006-01-08 22:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-08 20:52 2.6.15-rt2 - repeatable xrun - no good data in trace Mark Knecht
2006-01-08 21:04 ` Michal Schmidt
2006-01-08 21:49   ` Jan Engelhardt
2006-01-08 22:04     ` Mark Knecht
2006-01-08 22:11       ` Michal Schmidt [this message]
2006-01-08 22:21         ` Mark Knecht
2006-01-10 10:05       ` Ingo Molnar
2006-01-10 13:49         ` Steven Rostedt
2006-01-10 13:55           ` Mark Knecht
2006-01-10 14:04             ` Michal Schmidt

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=43C18E09.9060600@stud.feec.vutbr.cz \
    --to=xschmi00@stud.feec.vutbr.cz \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markknecht@gmail.com \
    --cc=mingo@elte.hu \
    --cc=rlrevell@joe-job.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.