From: Armin Steinhoff <armin@steinhoff.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: Operation not permitted / pthread_setschedparam / EOD
Date: Thu, 09 Oct 2014 10:35:18 +0200 [thread overview]
Message-ID: <543648C6.3040606@steinhoff.de> (raw)
In-Reply-To: <alpine.DEB.2.11.1410070237190.4383@nanos>
Thomas Gleixner schrieb:
[ clip]
>that it is calling setpriority() with the arguments
> which = 2 (PRIO_USER)
> who = 0 (root)
> prio = 0x14 (20)
>And that's exactly what is causing your problem.
OK, thanks a lot!!
I jumped back to PREEMPT_RT after several years and wonder:
- why isn't on kernel.org a direct link to this project? There is only a reference to an outdated page of RTwiki
- why is in the "latest News" of RTwiki (from 2012 / Reporting Bugs)) mentioned:
"As always, please search the existing bug list and consider posting the issue to the linux-rt-users <https://rt.wiki.kernel.org/index.php/Mailinglists> mailing list before opening a new defect." ?
Do we have to add: "If you do so, you must be prepared to get personal attacks from kernel developers ??
- why is it neccessary to scroll down 4 screens of a 27" monitor to find the released "vanilla" kernels in 3.x?
I gave up after the second screen and used then a "testing" kernel -> and that's at the end the root of the chaos!
Are you sure that the current representation of the PREEMPT_RT project will convince customers or developers to use it?
Next station in my test work is Minix 3.0: true mikrokernel system, drivers in user space ...
--Armin
next prev parent reply other threads:[~2014-10-09 8:35 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
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 ` Armin Steinhoff [this message]
2014-10-09 9:41 ` Operation not permitted / pthread_setschedparam / EOD 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=543648C6.3040606@steinhoff.de \
--to=armin@steinhoff.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).