Patrik Lundquist schrieb:
> On 1 October 2014 09:27, Armin Steinhoff <armin@steinhoff.de> wrote:
>> Thomas Gleixner schrieb:
>>> On Tue, 30 Sep 2014, Armin Steinhoff wrote:
>>>> How to solve that problem ?
>>> Hint #1: 3.4.0-rc7-rt7-2.16
>> I'm using the vanilla kernel "linux-3.4-rc7.tar.gz" and the related(?)
>> RT patch "patch-3.4-rt7.patch.xz" from "kernel.org"
> Try linux-3.4.97.tar.xz with patch-3.4.97-rt121.patch.xz

Yes, the version 3.4.97 + patch doesn't have any problems with the call
"pthread_setschedparam"! Thanks a lot!

I'm running the PCAP version of a MN node of openPOWERLINK. This app is
a plain userspace app ... it starts on core 0 and core 2
several threads which are using different RT priorities. ( core 1 "not
used" in that case)

But there are some sideeffects to other running processes/threads
related to their assigned priorities.
Here is the priority assignment after a fresh boot:  ps -elf  ->
Prio-After-OS-Restart.txt attached

If the app "demo_mn_console" has started its first RT thread,  a lot of
other processes/threads are jumping to the highest RT priority 99!!
Please have a look to: ps -elf -> Prio-after-app-start.txt

Do we have a problem with the RT kernel ? Or is simply the ps utility
broken ?

Best Regards

--Armin