[PlanetCCRMA] R.T. Scheduling errors on JACK startup, FC5

[Mike Jewell]

Well, just to close the loop on my question to help anyone else
searching these archives, I'll post what I did to solve this.

I downloaded the full archives so I could search it easier.  Then,
searching backwards from the present for "real-time scheduling", I read
the most recent posts and Fernando's replies.  Seemed like I had
everything he was talking about including the CCRMA kernel, pam and
rtirq.  I checked /etc/security/limits.conf and it looked good per
Fernando's post:

/etc/security/limits.conf
# or (default) allow everyone access
*               -       rtprio          99
*               -       nice            -10
*               -       memlock         4000000


So, what do you do when you can't think of anything else?
...reboot......  (of course).

I KNOW I've rebooted several times during and since all this installing
and upgrading using yum but, I admit, it's easy to loose track of it
all.  I guess I hadn't rebooted since getting the last few listed
upgrades in yumex done (great tool, btw) so I tried one more reboot and,
drum roll....

The errors went away.    8^)

Lesson:  I suppose always reboot after doing upgrades.  It can't hurt
and may solve some problems.


Mike Jewell
One-Up Audio




On Wed, 2006-10-11 at 06:38 -0700, Mike Jewell wrote:
> Oops.  Here's the output.  (see below)
> 
> 
> On Tue, 2006-10-10 at 17:29 -0700, Mike Jewell wrote:
> > Hi CCRMAites,
> > 
> > I just upgraded to Fedora Core 5 and the CCRMA kernel, etc. from FC3.
> > 
> > Here's my kernel info from uname -a:
> > 
> > Linux doc 2.6.16-1.2080.16.rdt.rhfc5.ccrmasmp #1 SMP PREEMPT Tue Jul 25
> > 13:39:30 EDT 2006 i686 i686 i386 GNU/Linux
> > 
> > When I start JACK with QjackCtl I get these messages about "real-time
> > scheduling".  If I run it as root, I don't get these messages.
> > 
> > 
> > I thought the CCRMA patched kernel was supposed to allow any user to use
> > this feature.  Do I have to enable it somewhere else?
> > 
> > 
> > Please forgive me if this was answered multiple times before.  I tried
> > searching the archives with no success.
> > 
> > Thanks,
> > 
> > Mike Jewell
> > One-Up Audio
> 
> 
> 17:17:49.205 Patchbay deactivated.
> 17:17:49.477 Statistics reset.
> 17:17:49.656 MIDI connection graph change.
> 17:17:49.682 MIDI connection change.
> 17:19:34.180 Startup script...
> 17:19:34.180 artsshell -q terminate
> 17:19:34.403 Startup script terminated with exit status=256.
> 17:19:34.403 JACK is starting...
> 17:19:34.403 jackd -R -dalsa -dhw:0 -r44100 -p2048 -n2
> 17:19:34.415 JACK was started with PID=20185 (0x4ed9).
> jackd 0.101.1
> Copyright 2001-2005 Paul Davis and others.
> jackd comes with ABSOLUTELY NO WARRANTY
> This is free software, and you are welcome to redistribute it
> under certain conditions; see the file COPYING for details
> JACK compiled with System V SHM support.
> cannot lock down memory for jackd (Cannot allocate memory)
> loading driver ..
> apparent rate = 44100
> creating alsa driver ... hw:0|hw:0|2048|2|44100|0|0|nomon|swmeter|-|
> 32bit
> control device hw:0
> configuring for 44100Hz, period = 2048 frames, buffer = 2 periods
> nperiods = 2 for capture
> nperiods = 2 for playback
> JACK: unable to mlock() port buffers: Cannot allocate memory
> cannot use real-time scheduling (FIFO at priority 20) [for thread
> -1230541920, from thread -1230541920] (1: Operation not permitted)
> cannot use real-time scheduling (FIFO at priority 10) [for thread
> -1241031776, from thread -1241031776] (1: Operation not permitted)
> 17:19:36.511 Server configuration saved to "/home/uslim/.jackdrc".
> 17:19:36.524 Statistics reset.
> 17:19:36.537 Client activated.
> 17:19:36.570 Audio connection change.
> 17:19:36.585 Audio connection graph change.
> cannot lock down memory for RT thread (Cannot allocate memory)
> cannot use real-time scheduling (FIFO at priority 9) [for thread
> -1212429408, from thread -1212429408] (1: Operation not permitted)
> 
> _______________________________________________
> PlanetCCRMA mailing list
> PlanetCCRMA@ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
>