Agreed - proposed fix in 5.4.0-32-generic also works for me. twiggy2@twiggy2:~$ journalctl -b -u rtkit-daemon -- Logs begin at Wed 2020-05-06 22:30:38 BST, end at Tue 2020-05-19 19:32:24 BST. -- May 19 19:32:11 twiggy2 systemd[1]: Starting RealtimeKit Scheduling Policy Service... May 19 19:32:11 twiggy2 systemd[1]: Started RealtimeKit Scheduling Policy Service. May 19 19:32:11 twiggy2 rtkit-daemon[1047]: Successfully called chroot. May 19 19:32:11 twiggy2 rtkit-daemon[1047]: Successfully dropped privileges. May 19 19:32:11 twiggy2 rtkit-daemon[1047]: Successfully limited resources. May 19 19:32:11 twiggy2 rtkit-daemon[1047]: Running. May 19 19:32:11 twiggy2 rtkit-daemon[1047]: Successfully made thread 1037 of process 1037 owned by '1000' high priority at nice level -11. May 19 19:32:11 twiggy2 rtkit-daemon[1047]: Supervising 1 threads of 1 processes of 1 users.
Rest of boot logs appear fine. Thank you ! ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in linux package in Ubuntu: Fix Committed Status in linux-azure package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Invalid Status in linux-riscv package in Ubuntu: Invalid Status in rtkit package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-gcp source package in Focal: Fix Committed Status in linux-kvm source package in Focal: Fix Committed Status in linux-oracle source package in Focal: Fix Committed Status in linux-riscv source package in Focal: Fix Committed Status in rtkit source package in Focal: Confirmed Bug description: SRU Justification Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the lowlatency kernel since we expected most RT users to use that kernel. However we are getting RT regressions with the generic kernel. Digging deeper into this option, it seems to be pretty specialized and to require quite a bit of workload-specific configuration/tuning to be useful, so it doesn't really seem to make sense for a general-purpose kernel. Fix: Turn this option back off. Test Case: See comment #4. Regression Potential: This was turned on to support some docker functionality, so this functionality will no longer be available. We've had this option off for all releases prior to focal, so this seems acceptable. --- These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
