FS#46000 - [linux] 4.2.x CONFIG_RT_GROUP_SCHED enabled!?

Attached to Project: Arch Linux
Opened by Tom (hungerfish) - Sunday, 16 August 2015, 15:58 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 03 September 2015, 13:07 GMT
Task Type General Gripe
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I found "Failed to make ourselves RT: Operation not permitted" in my logs and after some searching found https://bugzilla.redhat.com/show_bug.cgi?id=1229700
I checked, and indeed CONFIG_RT_GROUP_SCHED seems to be enabled in Arch's config.
While this doesn't seem to be causing problems, going by the linked bug report, it makes little sense to have it enabled!?


Additional info:
* package version : 4.1.4-1-ARCH (x86_64)
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Thursday, 03 September 2015, 13:07 GMT
Reason for closing:  Fixed
Additional comments about closing:  4.2.0-1
Comment by patrick (potomac) - Monday, 17 August 2015, 19:29 GMT
in what circumstances this problem can occur ? ( if it's really a problem )

because I don't have this error message "Failed to make ourselves RT: Operation not permitted" with kernel 4.1.6 from testing repository ( but I don't use pulseaudio )

what is the default setting about this feature "CONFIG_RT_GROUP_SCHED" for the others linux distros ?




Comment by Tom (hungerfish) - Thursday, 27 August 2015, 09:06 GMT
I couldn't really say, this is from a few boots back with the error:
Aug 16 17:15:31 BrilliantBert systemd[1]: Started RealtimeKit Scheduling Policy Service.
Aug 16 17:15:31 BrilliantBert rtkit-daemon[1012]: Successfully called chroot.
Aug 16 17:15:31 BrilliantBert rtkit-daemon[1012]: Successfully dropped privileges.
Aug 16 17:15:31 BrilliantBert rtkit-daemon[1012]: Successfully limited resources.
Aug 16 17:15:31 BrilliantBert rtkit-daemon[1012]: Running.
Aug 16 17:15:31 BrilliantBert rtkit-daemon[1012]: Canary thread running.
Aug 16 17:15:31 BrilliantBert rtkit-daemon[1012]: Failed to make ourselves RT: Operation not permitted
Aug 16 17:15:31 BrilliantBert rtkit-daemon[1012]: Watchdog thread running.

And this is from today, without the error:
Aug 27 09:43:14 BrilliantBert systemd[1]: Started RealtimeKit Scheduling Policy Service.
Aug 27 09:43:14 BrilliantBert rtkit-daemon[934]: Successfully called chroot.
Aug 27 09:43:14 BrilliantBert rtkit-daemon[934]: Successfully dropped privileges.
Aug 27 09:43:14 BrilliantBert rtkit-daemon[934]: Successfully limited resources.
Aug 27 09:43:14 BrilliantBert rtkit-daemon[934]: Running.
Aug 27 09:43:14 BrilliantBert rtkit-daemon[934]: Watchdog thread running.
Aug 27 09:43:14 BrilliantBert rtkit-daemon[934]: Canary thread running.
Aug 27 09:43:14 BrilliantBert rtkit-daemon[934]: Successfully made thread 932 of process 932 (/usr/bin/pulseaudio) owned by '1000' high priority at nice level -11.
Aug 27 09:43:14 BrilliantBert rtkit-daemon[934]: Supervising 1 threads of 1 processes of 1 users.

If you don't use pulseaudio, I guess you shouldn't see this anyway. As to the 'default setting', read the linked bugreport.
Also see https://bugzilla.redhat.com/show_bug.cgi?id=655321

I just saw this in my logs, googled and found the linked bugreport and thought it a good idea to report here, as mentioned before, I don't think its causing actual problems (yet..)

Loading...