[PlanetCCRMA] Reliable version of Fedora using rt-kernel?

John S. Dey john at jsdey.com
Mon Nov 14 16:42:11 PST 2011


Fernando,

I added the file as indicated below.  I rebooted.  The message from qjackctl was the same:  Can not use real-time scheduling.  Any other ideas?  Thanks.

John
On Nov 14, 2011, at 6:03 PM, Fernando Lopez-Lezcano wrote:

> On 11/14/2011 02:46 PM, John S. Dey wrote:
>> Hi Fernando,
>> 
>> Thanks for your response and thanks for the new rt-kernel for fc15.  I did discover that I could run the prior rt as root and get decent results.  With the new kernel also running root I run with a latency of 5.33ms (64/4) with an occasional xrun using aeolus driven by aplaymidi.  As user (robo12) however, I get a message from qjackctl that says: Cannot use real-time scheduling  ...  and xruns occur.  I did add robo12 to jackuser group as Mark suggested.  Any further thoughts or suggestions would be appreciated.
> 
> You could try adding this file:
> 
> /etc/security/limits.d/99-planetccrma.conf
> 
> ----
> # Default limits for users of jack-audio-connection-kit
> # for Planet CCRMA kernels
> 
> * - rtprio 99
> * - memlock 4194304
> ----
> 
> (the limit for the default Fedora install is too low for the rt kernel + jack combination)
> Let us know how it goes!
> -- Fernando
> 
> 
>> DEBUG:
>> 
>> [robo12 at robo12 ~]$ cat /proc/asound/cards
>>  0 [Intel          ]: HDA-Intel - HDA Intel
>>                       HDA Intel at 0xee400000 irq 49
>> 29 [ThinkPadEC     ]: ThinkPad EC - ThinkPad Console Audio Control
>>                       ThinkPad Console Audio Control at EC reg 0x30, fw 79HT50WW-1.07
>> 
>> [robo12 at robo12 init.d]$ sudo ./rtirq status
>> [sudo] password for robo12:
>> 
>>   PID CLS RTPRIO  NI PRI %CPU STAT COMMAND	
>>    84 FF      80   - 120  0.0 S    irq/8-rtc0	
>>   915 FF      75   - 115  0.0 S    irq/49-hda_inte	
>>    76 FF      70   - 110  0.0 S    irq/16-uhci_hcd	
>>    77 FF      69   - 109  0.0 S    irq/17-uhci_hcd	
>>    78 FF      68   - 108  0.0 S    irq/18-uhci_hcd	
>>    79 FF      67   - 107  0.0 S    irq/19-uhci_hcd	
>>    81 FF      65   - 105  0.0 S    irq/1-i8042	
>>    80 FF      64   - 104  0.3 S    irq/12-i8042	
>>    28 FF      50   -  90  0.0 S    irq/9-acpi	
>>    44 FF      50   -  90  0.0 S    irq/40-PCIe PME	
>>    45 FF      50   -  90  0.0 S    irq/41-PCIe PME	
>>    46 FF      50   -  90  0.0 S    irq/42-PCIe PME	
>>    47 FF      50   -  90  0.0 S    irq/43-PCIe PME	
>>    48 FF      50   -  90  0.0 S    irq/44-PCIe PME	
>>    49 FF      50   -  90  0.0 S    irq/41-pciehp	
>>    50 FF      50   -  90  0.0 S    irq/42-pciehp	
>>    51 FF      50   -  90  0.0 S    irq/43-pciehp	
>>    52 FF      50   -  90  0.0 S    irq/44-pciehp	
>>    60 FF      50   -  90  1.5 S    irq/45-ahci	
>>    67 FF      50   -  90  0.0 S    irq/14-ata_piix	
>>    69 FF      50   -  90  0.0 S    irq/15-ata_piix	
>>    75 FF      50   -  90  0.0 S    irq/19-ehci_hcd	
>>   209 FF      50   -  90  0.2 S    irq/46-radeon	
>>   403 FF      50   -  90  0.0 S    irq/16-yenta	
>>   903 FF      50   -  90  0.4 S    irq/48-iwl3945	
>>  1178 FF      50   -  90  0.0 S    irq/47-p2p1	
>>     3 FF       1   -  41  3.0 S    ksoftirqd/0	
>>    18 FF       1   -  41  2.9 S    ksoftirqd/1	
>> 
>> [robo12 at robo12 init.d]$
>> [robo12 at robo12 ~]$ cat /proc/asound/cards
>>  0 [Intel          ]: HDA-Intel - HDA Intel
>>                       HDA Intel at 0xee400000 irq 49
>> 29 [ThinkPadEC     ]: ThinkPad EC - ThinkPad Console Audio Control
>>                       ThinkPad Console Audio Control at EC reg 0x30, fw 79HT50WW-1.07
>> 
>> 
>> qjackctl messages
>> 
>> 17:15:41.870 Patchbay deactivated.
>> 17:15:41.872 Statistics reset.
>> 17:15:41.878 ALSA connection change.
>> Cannot connect to server socket err = No such file or directory
>> Cannot connect to server socket
>> jack server is not running or cannot be started
>> 17:15:41.891 ALSA connection graph change.
>> 17:15:48.695 JACK is starting...
>> 17:15:48.696 /usr/bin/jackd -dalsa -dhw:0 -r48000 -p64 -n4 -P
>> Cannot connect to server socket err = No such file or directory
>> Cannot connect to server socket
>> jack server is not running or cannot be started
>> no message buffer overruns
>> 17:15:48.774 JACK was started with PID=3254.
>> no message buffer overruns
>> jackdmp 1.9.7
>> Copyright 2001-2005 Paul Davis and others.
>> Copyright 2004-2011 Grame.
>> jackdmp 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 server starting in realtime mode with priority 60
>> control device hw:0
>> control device hw:0
>> audio_reservation_init
>> Acquire audio card Audio0
>> creating alsa driver ... hw:0|-|64|4|48000|0|0|nomon|swmeter|-|32bit
>> control device hw:0
>> configuring for 48000Hz, period = 64 frames (1.3 ms), buffer = 4 periods
>> ALSA: final selected sample format for playback: 16bit little-endian
>> ALSA: use 4 periods for playback
>> Cannot use real-time scheduling (RR/60)(1: Operation not permitted)
>> AcquireSelfRealTime error
>> 17:15:50.986 JACK connection change.
>> 17:15:50.989 Server configuration saved to "/home/robo12/.jackdrc".
>> 17:15:50.989 Statistics reset.
>> 17:15:50.997 Client activated.
>> 17:15:51.006 JACK connection graph change.
>> _____________________________________________________
>> On Nov 13, 2011, at 6:23 PM, Fernando Lopez-Lezcano wrote:
>> 
>>> On 11/13/2011 12:05 PM, John S. Dey wrote:
>>>> Hi Fernando,
>>>> 
>>>> Thanks for getting back to me. No. You're presumption was incorrect. I
>>>> hadn't install rtirq. I have now but it didn't make much different.
>>> 
>>> (it does not necessarily make a difference, basically it tries to give better priority to the soundcard hardware interrupts, to test you have to reboot or - as root - do a "/sbin/service rtirq start" from a terminal... just in case you did not)
>>> 
>>> -- Fernando
>>> 
>>> 
>>>> On Nov 12, 2011, at 9:17 PM, Fernando Lopez-Lezcano wrote:
>>>> 
>>>>> On 11/12/2011 02:06 PM, John S. Dey wrote:
>>>>>> Hi,
>>>>>> 
>>>>>> I'm currently using 3.0.7-1.rt20.1.fc15.ccrma.x86_64.rt as my kernel
>>>>>> on fc15 running on a thinkpad T60p with ATI graphics. I haven't been
>>>>>> able to find settings for jackd that produce reliable real time
>>>>>> performance. In the past I could achieve latency as presented in
>>>>>> qjackctl of less than 10ms. Now I get xruns with latencies of 40ms
>>>>>> and more. The stock kernel is just as good.
>>>>> 
>>>>> What soundcard do you have and what parameters did you use for jack?
>>>>> (just curious).
>>>>> 
>>>> cat /proc/asound/cards
>>>> 
>>>> 0 [Intel ]: HDA-Intel - HDA Intel
>>>> HDA Intel at 0xee400000 irq 49
>>>> 1 [Set ]: USB-Audio - C-Media USB Headphone Set
>>>> C-Media USB Headphone Set at usb-0000:00:1d.0-2, full speed
>>>> 29 [ThinkPadEC ]: ThinkPad EC - ThinkPad Console Audio Control
>>>> ThinkPad Console Audio Control at EC reg 0x30, fw 79HT50WW-1.07
>>>> 
>>>> I have varied Frames/Period and Periods/Buffer (2,3 and 4) but haven't
>>>> been able to get
>>>> stable results better that what is shown. I ran with both sound cards
>>>> shown above. The rt kernel wasn't any better that the up to date stock
>>>> kernel.
>>>> 
>>>> Thanks,
>>>> 
>>>> John
>> 




More information about the PlanetCCRMA mailing list