From: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
To: Mark Knecht <markknecht@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
Lee Revell <rlrevell@joe-job.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jan Engelhardt <jengelh@linux01.gwdg.de>
Subject: Re: 2.6.15-rt2 - repeatable xrun - no good data in trace
Date: Tue, 10 Jan 2006 15:04:48 +0100 [thread overview]
Message-ID: <43C3BF00.9000901@stud.feec.vutbr.cz> (raw)
In-Reply-To: <5bdc1c8b0601100555k7538924cx7a17b3e405771691@mail.gmail.com>
Mark Knecht wrote:
> While I have to agree that *if* cdrecord is running at a higher
> priority then Jack would get trumped, I'm not positive yet that we
> know that's true in this specific case. I have not yet received any
> response from the developer of k3b, and while cdrecord is listed in
> the setup of k3b I'm not sure how to test that it is really causing
> the specific failure I saw.
That shouldn't be too hard. While burning a CD, see the priority
cdrecord is running at. You can use:
ps -eo pid,user,args,pri | grep cdrecord
Also see if you have cdrecord installed suid root:
ls -l `which cdrecord`
If you do, you can be pretty sure that it runs at the highest possible
realtime priority. This is hardcoded in cdrecord. It does it if it runs
priviledged.
Michal
prev parent reply other threads:[~2006-01-10 14:04 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
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 [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=43C3BF00.9000901@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 \
--cc=rostedt@goodmis.org \
/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.