Messages in this thread | | | Date | Tue, 10 Jan 2006 15:04:48 +0100 | From | Michal Schmidt <> | Subject | Re: 2.6.15-rt2 - repeatable xrun - no good data in trace |
| |
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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |