** Changed in: rtkit (Ubuntu)
Status: Confirmed => Invalid
** Changed in: rtkit (Ubuntu Focal)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rtkit in Ubuntu.
This bug was fixed in the package linux-azure - 5.4.0-1022.22
---
linux-azure (5.4.0-1022.22) focal; urgency=medium
* focal/linux-azure: 5.4.0-1022.22 -proposed tracker (LP: #1887060)
[ Ubuntu: 5.4.0-42.46 ]
* focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
*
This bug was fixed in the package linux-gcp - 5.4.0-1021.21
---
linux-gcp (5.4.0-1021.21) focal; urgency=medium
* focal/linux-gcp: 5.4.0-1021.21 -proposed tracker (LP: #1887062)
[ Ubuntu: 5.4.0-42.46 ]
* focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
* linux
This bug was fixed in the package linux-oracle - 5.4.0-1021.21
---
linux-oracle (5.4.0-1021.21) focal; urgency=medium
* focal/linux-oracle: 5.4.0-1021.21 -proposed tracker (LP: #1887065)
[ Ubuntu: 5.4.0-42.46 ]
* focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
*
This bug was fixed in the package linux - 5.4.0-42.46
---
linux (5.4.0-42.46) focal; urgency=medium
* focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
* linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix
This bug was fixed in the package linux-riscv - 5.4.0-27.31
---
linux-riscv (5.4.0-27.31) focal; urgency=medium
* focal/linux-riscv: 5.4.0-27.31 -proposed tracker (LP: #1878798)
* Add support for Ambiq micro AM1805 RTC chip (LP: #1876667)
- [config] riscv: disable am-1805
This bug was fixed in the package linux-kvm - 5.4.0-1015.15
---
linux-kvm (5.4.0-1015.15) focal; urgency=medium
[ Ubuntu: 5.4.0-37.41 ]
* CVE-2020-0543
- SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
- SAUCE: x86/cpu: Add a steppings field to
** Changed in: rtkit (Ubuntu Focal)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rtkit in Ubuntu.
https://bugs.launchpad.net/bugs/1875665
Title:
rtkit-daemon[*]: Failed to make
This bug was fixed in the package linux-riscv - 5.4.0-27.31
---
linux-riscv (5.4.0-27.31) focal; urgency=medium
* focal/linux-riscv: 5.4.0-27.31 -proposed tracker (LP: #1878798)
* Add support for Ambiq micro AM1805 RTC chip (LP: #1876667)
- [config] riscv: disable am-1805
This bug was fixed in the package linux-kvm - 5.4.0-1015.15
---
linux-kvm (5.4.0-1015.15) focal; urgency=medium
[ Ubuntu: 5.4.0-37.41 ]
* CVE-2020-0543
- SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
- SAUCE: x86/cpu: Add a steppings field to
This bug was fixed in the package linux-oracle - 5.4.0-1015.15
---
linux-oracle (5.4.0-1015.15) focal; urgency=medium
[ Ubuntu: 5.4.0-37.41 ]
* CVE-2020-0543
- SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
- SAUCE: x86/cpu: Add a steppings field
This bug was fixed in the package linux-gcp - 5.4.0-1015.15
---
linux-gcp (5.4.0-1015.15) focal; urgency=medium
[ Ubuntu: 5.4.0-37.41 ]
* CVE-2020-0543
- SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
- SAUCE: x86/cpu: Add a steppings field to
This bug was fixed in the package linux-azure - 5.4.0-1016.16
---
linux-azure (5.4.0-1016.16) focal; urgency=medium
[ Ubuntu: 5.4.0-37.41 ]
* CVE-2020-0543
- SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
- SAUCE: x86/cpu: Add a steppings field
This bug was fixed in the package linux - 5.4.0-37.41
---
linux (5.4.0-37.41) focal; urgency=medium
* CVE-2020-0543
- SAUCE: x86/speculation/spectre_v2: Exclude Zhaoxin CPUs from SPECTRE_V2
- SAUCE: x86/cpu: Add a steppings field to struct x86_cpu_id
- SAUCE: x86/cpu:
Yes. It would appear that the fix/config change was not rolled into
5.4.0-33-generic. RT_GROUP_SCHED is still enabled in generic build but
not lowlatency kernel build.
twiggy@twiggy:/ $ zgrep CONFIG_RT_GROUP_SCHED /boot/config-5.4.0-33-generic
CONFIG_RT_GROUP_SCHED=y
twiggy@twiggy:/ $
The fix does not work for me:
uname -r
5.4.0-33-generic
ournalctl -b0 -u rtkit-daemon
-- Logs begin at Wed 2020-04-29 18:57:09 EEST, end at Thu 2020-06-04 18:41:05
EEST. --
Jun 04 18:26:06 n552vw systemd[1]: Starting RealtimeKit Scheduling Policy
Service...
Jun 04 18:26:06 n552vw systemd[1]:
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
I am running the 5.4.0-32-generic kernel from focal-proposed, and rtkit-
daemon seems to be working normally now.
: kai@dipper kai; uname -r
5.4.0-32-generic
: kai@dipper kai; journalctl -b0 -u rtkit-daemon
-- Logs begin at Fri 2020-01-03 16:35:36 EST, end at Tue 2020-05-19 11:02:23
EDT. --
May
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
** Changed in: linux-azure (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: linux-gcp (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: linux-kvm (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: linux-oracle (Ubuntu Focal)
Status: New =>
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rtkit in Ubuntu.
https://bugs.launchpad.net/bugs/1875665
Title:
rtkit-daemon[*]: Failed to make ourselves
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-gcp (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oracle (Ubuntu)
Importance:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rtkit (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rtkit in Ubuntu.
** Description changed:
+ 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
Seems like this kernel config change should be reverted for now. We can
consider turning it back on later if rtkit receives changes to work
better with this option.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance:
Should this be fixed with a change to the kernel build config, or, is
this actually indicative of rtkit being not cgroup aware ?
I haven't considered the implications for configuring rtkit cgroup
aware, or even if it makes sense to. I.e. should each application that
requires RT scheduling be made
Seth, could you comment on that? It was unfortunate that this kernel
change landed late in the cycle and created this issue, would reverting
in the next upload be an option?
** Tags added: desktop-lts-wishlist
** Changed in: rtkit (Ubuntu)
Importance: Low => High
** Changed in: rtkit
In the generic kernel CONFIG_RT_GROUP_SCHED is still enabled. It was
only disabled for the lowlatency kernel.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rtkit in Ubuntu.
https://bugs.launchpad.net/bugs/1875665
Title:
Attached is the output from journalctl -b 0, where the error occurs.
Apologies - no vagrant skills here, but I can confirm Kai's replication
method - kvm qemu clean 20.04 server install, then add pulseaudio,
docker.io, reboot and the issue occurs.
** Attachment added: "20.04 boot log showing
seems like from the other bug that it got turn off again in -26.30 which
is the revision in use by the report here according to the apport
report?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rtkit in Ubuntu.
Enabling, but not configuring CONFIG_RT_GROUP_SCHED seems likely to be the
cause of this:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?h=master-next=9b039fc517876d312e7fa0955571101a299c91f5
Some discussion of this WRT lowlatency kernel is here:
Could you add a 'journalctl -b 0' log from a session having the issue?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rtkit in Ubuntu.
https://bugs.launchpad.net/bugs/1875665
Title:
rtkit-daemon[*]: Failed to make ourselves RT:
** Changed in: rtkit (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rtkit in Ubuntu.
https://bugs.launchpad.net/bugs/1875665
Title:
rtkit-daemon[*]: Failed to make ourselves RT:
I have the same issue, 18.04 -> 20.04 via upgrade. RTKit now failing to
give pulseaudio RT priority.
Issue resulting is some choppy audio - under heavy load. Pulseaudio not
RT priority
20.04 clean install:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
At this point it's just these log messages.
--
You received this bug notification because you are a member of Desktop
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
Does it lead to any user visible problem or only to those warnings?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rtkit in Ubuntu.
https://bugs.launchpad.net/bugs/1875665
Title:
rtkit-daemon[*]: Failed to make ourselves RT:
In a virtual machine I can reproduce this by installing pulseaudio and
docker.io.
I'm attaching a Vagrantfile that reproduces the issue for me.
:; vagrant up
:; vagrant ssh -t -- journalctl -u rtkit-daemon
** Attachment added: "vagrantfile to reproduce issue"
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Changed in: rtkit (Ubuntu)
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: rtkit (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rtkit in Ubuntu.
https://bugs.launchpad.net/bugs/1875665
39 matches
Mail list logo
