linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carsten Emde <C.Emde@osadl.org>
To: Armin Steinhoff <armin@steinhoff.de>,
	Patrik Lundquist <patrik.lundquist@gmail.com>
Cc: rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: Operation not permitted / pthread_setschedparam
Date: Sat, 04 Oct 2014 12:49:34 +0200	[thread overview]
Message-ID: <542FD0BE.10508@osadl.org> (raw)
In-Reply-To: <542D0689.8050602@steinhoff.de>

Armin,

> [..] 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 ?
Let me try to summarize your observations and suspicions:
1. After booting your RT kernel, everything works as expected.
2. The ps utility works as expected.
3. There are no bug reports that the RT kernel autonomously and at
random fiddles around with task priorities.
4. There are no bug reports that the ps utility - one of the most
frequently used utilities - suddenly may start to display erroneous
priority numbers.

5. At a given time, you start your application that apparently modifies
task priorities *in some way*.
6. Shortly afterwards you are observing that other not intended tasks
changed their priority as well.

7. Your first suspicion is that we may have a problem with the RT kernel.
8. And your second suspicion is that the ps utility is broken.

Doesn't come another suspicion to mind?

	-Carsten.

  reply	other threads:[~2014-10-04 11:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 10:40 Operation not permitted / pthread_setschedparam Armin Steinhoff
2014-09-30 11:44 ` Harry van Haaren
2014-09-30 12:32   ` Armin Steinhoff
2014-09-30 17:22     ` Armin Steinhoff
2014-09-30 23:09 ` Thomas Gleixner
2014-10-01  7:27   ` Armin Steinhoff
2014-10-01  7:49     ` Patrik Lundquist
2014-10-02  8:02       ` Armin Steinhoff
2014-10-04 10:49         ` Carsten Emde [this message]
2014-10-04 12:36           ` Armin Steinhoff
2014-10-04 12:50             ` Armin Steinhoff
2014-10-04 23:56             ` Thomas Gleixner
2014-10-05 11:07               ` Armin Steinhoff
2014-10-05 11:47               ` Armin Steinhoff
2014-10-05 14:34               ` Armin Steinhoff
     [not found]               ` <54312C88.8060609@steinhoff.de>
2014-10-05 20:54                 ` Thomas Gleixner
2014-10-06  8:03                   ` Armin Steinhoff
2014-10-06 13:34                   ` Armin Steinhoff
2014-10-07  1:33                     ` Thomas Gleixner
2014-10-07  7:57                       ` Armin Steinhoff
2014-10-09  8:35                       ` Operation not permitted / pthread_setschedparam / EOD Armin Steinhoff
2014-10-09  9:41                         ` Pavel Vasilyev
2014-10-09 12:22                           ` Crowd Funding ? Armin Steinhoff
2014-10-09 21:59                             ` Richard Weinberger
2014-10-10 12:14                               ` Armin Steinhoff
2014-10-11 10:04                                 ` Armin Steinhoff
2014-10-05 10:13             ` Operation not permitted / pthread_setschedparam Armin Steinhoff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=542FD0BE.10508@osadl.org \
    --to=c.emde@osadl.org \
    --cc=armin@steinhoff.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=patrik.lundquist@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).