From: Tim E. R. <ter...@ro...> - 2011-02-11 20:27:22
|
Finally got around to upgrading my OS here. I set @audio - memlock 256000 and added myself to the audio group, as usual. The only thing I haven't done yet is install a RT kernel, but that shouldn't be necessary yet (or is it?) I get these lines when starting MusE: "WARNING: Cannot lock memory:: Cannot allocate memory" (this is from main.cpp where it calls mlockall) "creating thread <Prefetch> failed: Operation not permitted" "creating thread <Midi> failed: Operation not permitted" ... "midi sequencer thread does not start!? Exiting..." Set-up, permissions etc. look the same as my Mandriva 2009.1 box, which works. What am I forgetting? I don't think I had this problem with previous Mandriva releases. I also tried adding myself to some other groups like users and mem. No luck. Thanks. Tim. |
From: Robert J. <spa...@gm...> - 2011-02-11 21:44:15
|
Hi Tim, 2011/2/11 Tim E. Real <ter...@ro...>: > @audio - memlock 256000 I think the error points to that the mem size is too small Are you sure 256MB is enough? I have it much higher. Not entirely sure how this works but the footprint of muse including shared libs can be very big. /Robert |
From: Tim E. R. <ter...@ro...> - 2011-02-11 22:21:22
|
On February 11, 2011 04:44:08 pm Robert Jonsson wrote: > Hi Tim, > > 2011/2/11 Tim E. Real <ter...@ro...>: > > @audio - memlock 256000 > > I think the error points to that the mem size is too small > Are you sure 256MB is enough? I have it much higher. > > Not entirely sure how this works but the footprint of muse including > shared libs can be very big. > > /Robert > Hmm, looks like you are right, I set it to unlimited and that got rid of the mlockall warning, but still fails creating the two threads. Ah, for those, I think I need the RT kernel - I think the code tries to set some privileges on those threads. Will try... Shame though, we should fix this so it at least runs. I'll have a look at the thread code later. Tim. |
From: Robert J. <spa...@gm...> - 2011-02-11 22:39:41
|
2011/2/11 Tim E. Real <ter...@ro...>: > Hmm, looks like you are right, I set it to unlimited and that got rid of the > mlockall warning, but still fails creating the two threads. > > Ah, for those, I think I need the RT kernel - I think the code tries to set > some privileges on those threads. > > Will try... > > Shame though, we should fix this so it at least runs. > I'll have a look at the thread code later. Not sure why it won't run but an RT kernel is definitely not required. The exposed features are the same. I've run MusE many times (including right now on this laptop) without an RT kernel and there are no such errors. Do you have any rt line in limits.conf? @audio - rtprio 95 I think that is what allows the audio-group to set realtime scheduling Regards, Robert |
From: Tim E. R. <ter...@ro...> - 2011-02-11 22:54:57
|
On February 11, 2011 05:39:34 pm Robert Jonsson wrote: > 2011/2/11 Tim E. Real <ter...@ro...>: > > Hmm, looks like you are right, I set it to unlimited and that got rid of > > the mlockall warning, but still fails creating the two threads. > > > > Ah, for those, I think I need the RT kernel - I think the code tries to > > set some privileges on those threads. > > > > Will try... > > > > Shame though, we should fix this so it at least runs. > > I'll have a look at the thread code later. > > Not sure why it won't run but an RT kernel is definitely not required. > The exposed features are the same. > I've run MusE many times (including right now on this laptop) without > an RT kernel and there are no such errors. > > Do you have any rt line in limits.conf? > @audio - rtprio 95 > I think that is what allows the audio-group to set realtime scheduling > > Regards, > Robert > My mistake, forgot this one. It was at default @audio - rtprio 50 But I set it at 80 like the other OS, and still no luck. I think it might be that stock kernel. Will try installing a better one... Tim. |
From: Geoff K. <gs...@gm...> - 2011-02-11 23:51:52
|
FWIW I'm using stock fedora kernel and it works well. On Feb 11, 2011 5:55 PM, "Tim E. Real" <ter...@ro...> wrote: On February 11, 2011 05:39:34 pm Robert Jonsson wrote: > 2011/2/11 Tim E. Real <ter...@ro...>... My mistake, forgot this one. It was at default @audio - rtprio 50 But I set it at 80 like the other OS, and still no luck. I think it might be that stock kernel. Will try installing a better one... Tim. ------------------------------------------------------------------------------ The ultimate all-in-... |
From: Tim E. R. <ter...@ro...> - 2011-02-12 05:11:29
|
On February 11, 2011 06:51:45 pm you wrote: > FWIW I'm using stock fedora kernel and it works well. > > On Feb 11, 2011 5:55 PM, "Tim E. Real" <ter...@ro...> wrote: > > On February 11, 2011 05:39:34 pm Robert Jonsson wrote: > > 2011/2/11 Tim E. Real <ter...@ro...>... > > My mistake, forgot this one. It was at default @audio - rtprio 50 > But I set it at 80 like the other OS, and still no luck. > > I think it might be that stock kernel. Will try installing a better one... > > Tim. Yep it was the kernel. Installed a tmb kernel and it works. Likely the code attempting to set FIFO scheduling on the threads. May have been down this route before (repeatedly). My memory fades... Thanks for the help you guys. Yeah, I know, other distros don't have this problem with stock kernels. Must try to fix this in MusE to ease the pain for users of such kernels. Fall back on another type of scheduling. My stock kernel says: "This kernel is compiled for desktop use, single or multiple x86_64 processor(s)/core(s) using HZ_1000, voluntary preempt, CFS cpu scheduler and cfq i/o scheduler." --- @ Orcan: (Hey look at the nice MusE Qt > 4.6 theme icons I have now, he he!) Stock packages included a totally busted-ass KDevelop-4.0.0 Had to turn on the backport repos and got KDevelop 4.1 and a bunch of other updates. Now *this* KDevelop is what I've been waiting for! Whee... Now it is time to truly transfer all production to that (faster) machine. @ Geoff B: Well, I guess I'm a long-time die hard Mandi fan for reasons. You get used to a certain distro. Ever notice when you install a new favourite distro version, you always seem to utter the same cursing pattern? And I'd like to predict right now that I'll be swearing again, he he... Cheers. Tim. |