From: Logarithmus <Logarithmus@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: rtkit: doesn't work on musl
Date: Sun, 21 Feb 2021 04:05:59 +0100 [thread overview]
Message-ID: <20210221030559.cLur3BCItJfhHiV-oktS1BEgheC4P_izyiJH0UaZ8vk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28728@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]
New comment by Logarithmus on void-packages repository
https://github.com/void-linux/void-packages/issues/28728#issuecomment-782787488
Comment:
It seems that the problem is both with `musl` & missing `CONFIG_RT_GROUP_SCHED` kernel option.
> Currently I'm investigating these stability issues with `pipewire`. It seems that `pipewire` is trying to use `rtkit` to make audio/video processing run in real time. Unfortunately, it fails to do so:
> ```
> 2020-11-16T03:49:59.73350 daemon.err: Nov 16 03:49:59 rtkit-daemon[3165]: Failed to make ourselves RT: Function not implemented
> 2020-11-16T03:49:59.73602 daemon.warn: Nov 16 03:49:59 rtkit-daemon[3165]: Warning: failed to read scheduler policy: Function not implemented
> 2020-11-16T03:49:59.73620 daemon.debug: Nov 16 03:49:59 rtkit-daemon[3165]: Supervising 0 threads of 0 processes of 1 users.
> 2020-11-16T03:49:59.73645 daemon.debug: Nov 16 03:49:59 rtkit-daemon[3165]: Supervising 0 threads of 0 processes of 1 users.
> 2020-11-16T03:49:59.74118 daemon.err: Nov 16 03:49:59 rtkit-daemon[3165]: Failed to make ourselves RT: Function not implemented
> ```
> After a bit of searching, I've found these bugs:
> https://bugzilla.redhat.com/show_bug.cgi?id=1229700
> https://bugs.gentoo.org/show_bug.cgi?id=569546
>
> I've built `linux5.9` for `x86_64` with `CONFIG_RT_GROUP_SCHED` disabled.
> For some strange reason, nothing changed, the error persists. Luckily, screen sharing works without `rtkit`.
> I guess that those rare issues with screen sharing, which were described above, may be caused by `rtkit` not working.
next prev parent reply other threads:[~2021-02-21 3:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-13 12:23 [ISSUE] " st3r4g
2021-02-13 15:09 ` ericonr
2021-02-21 3:05 ` Logarithmus
2021-02-21 3:05 ` Logarithmus [this message]
2021-02-21 8:35 ` st3r4g
2021-02-21 8:36 ` st3r4g
2021-02-21 8:37 ` st3r4g
2021-02-21 13:15 ` Logarithmus
2021-02-21 13:16 ` Logarithmus
2021-02-21 13:17 ` Logarithmus
2021-02-21 13:25 ` st3r4g
2021-02-21 13:48 ` Logarithmus
2021-02-26 10:34 ` 12101111
2021-02-26 16:47 ` st3r4g
2021-04-18 22:13 ` yemouu
2021-04-21 15:28 ` ericonr
2021-05-15 20:38 ` ericonr
2021-05-15 21:36 ` ericonr
2021-05-20 9:10 ` st3r4g
2021-05-20 9:15 ` st3r4g
2021-05-20 9:17 ` st3r4g
2021-05-20 14:05 ` ericonr
2022-05-04 2:15 ` github-actions
2022-05-19 2:15 ` [ISSUE] [CLOSED] " github-actions
2022-06-04 2:08 ` github-actions
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=20210221030559.cLur3BCItJfhHiV-oktS1BEgheC4P_izyiJH0UaZ8vk@z \
--to=logarithmus@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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).