From: Robert J. <rj...@sp...> - 2004-11-05 22:34:22
|
fredagen den 5 november 2004 22.48 skrev Thorsten Wilms: > On Fri, Nov 05, 2004 at 10:03:01PM +0100, Robert Jonsson wrote: > > I see below that the error Werner talked about is not printed. Would it > > be possible for you to print out the chrt data for the threads MusE > > starts? > > Muse running as normal user: > > / # for n in `pidof muse`; do chrt -p $n; done > pid 29649's current scheduling policy: SCHED_OTHER > pid 29649's current scheduling priority: 0 > pid 29648's current scheduling policy: SCHED_FIFO > pid 29648's current scheduling priority: 9 > pid 29646's current scheduling policy: SCHED_FIFO > pid 29646's current scheduling priority: 10 > pid 29643's current scheduling policy: SCHED_OTHER > pid 29643's current scheduling priority: 0 > > Muse as root: > > / # for n in `pidof muse`; do chrt -p $n; done > pid 29001's current scheduling policy: SCHED_FIFO > pid 29001's current scheduling priority: 80 > pid 29000's current scheduling policy: SCHED_OTHER > pid 29000's current scheduling priority: 0 > pid 28999's current scheduling policy: SCHED_FIFO > pid 28999's current scheduling priority: 99 > pid 28998's current scheduling policy: SCHED_FIFO > pid 28998's current scheduling priority: 9 > pid 28994's current scheduling policy: SCHED_FIFO > pid 28994's current scheduling priority: 99 > pid 28990's current scheduling policy: SCHED_OTHER > pid 28990's current scheduling priority: 0 Great printout. This clearly shows major problems with FIFO threads. Two threads are missing altogether and one has incorrect priority. About the timing problems you reported earlier, do you hear them when running MusE as root also? If you use larger buffers that is... I think this printout suggests it should work just fine if MusE is started by root... it would be very good to know if this is not the case. > > > The (admittedly ambiguous) errors below: > > > MusE: creating watchdog thread failed:: Success > > > creating thread failed:: Success > > > > point to a permission error that probably leads to that midi does not > > work at all. > > But midi works (with aplaymidi for example). Yes, it's not really a midi error. MusE uses realtime priority threads for a lot of things, one of them being the midi thread. It seems MusE fails to create these threads --> no music. > > > Do you run MusE with setuid, givertcap or the new realtime module for > > 2.6? The recommended way would be to use the realtime module if running > > 2.6. > > Using the realtime lsm is the plan. > > > It seems you have built MusE with givertcap support, this error should > > not be printed otherwise. > > When using the realtime module no extra compile flags are needed. > > Oops, I have. Will try if recompling without changes anything. Ok, great. /Robert -- http://spamatica.se/music/ |