Description of problem: After I suspend/resume my machine, I see a message saying "The canary thread is apparently starving. Taking action." in /var/log/messages. I see this messages on F13 and also when booting a recent (kde) nightly. Version-Release number of selected component (if applicable): rtkit-0.10-1.fc15.x86_64 How Reproducible: * Suspend + Resume. * View /var/log/messages # grep rtkit /var/log/messages Mar 16 15:26:38 localhost rtkit-daemon[2184]: Successfully made thread 2183 of process 2183 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11. Mar 16 15:26:38 localhost rtkit-daemon[2184]: Successfully made thread 2194 of process 2183 (/usr/bin/pulseaudio) owned by '500' RT at priority 5. Mar 16 15:26:38 localhost rtkit-daemon[2184]: Successfully made thread 2195 of process 2183 (/usr/bin/pulseaudio) owned by '500' RT at priority 5. Mar 16 15:26:38 localhost rtkit-daemon[2184]: Successfully made thread 2196 of process 2183 (/usr/bin/pulseaudio) owned by '500' RT at priority 5. Mar 16 15:26:38 localhost rtkit-daemon[2184]: Successfully made thread 2197 of process 2197 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11. Mar 16 15:26:38 localhost rtkit-daemon[2184]: Successfully made thread 2199 of process 2199 (/usr/bin/pulseaudio) owned by '500' high priority at nice level -11. Mar 16 15:34:41 localhost rtkit-daemon[2184]: The canary thread is apparently starving. Taking action. Mar 16 15:34:41 localhost rtkit-daemon[2184]: Demoting known real-time threads. Mar 16 15:34:41 localhost rtkit-daemon[2184]: Successfully demoted thread 2196 of process 2183 (/usr/bin/pulseaudio). Mar 16 15:34:41 localhost rtkit-daemon[2184]: Successfully demoted thread 2195 of process 2183 (/usr/bin/pulseaudio). Mar 16 15:34:41 localhost rtkit-daemon[2184]: Successfully demoted thread 2194 of process 2183 (/usr/bin/pulseaudio). Mar 16 15:34:41 localhost rtkit-daemon[2184]: Successfully demoted thread 2183 of process 2183 (/usr/bin/pulseaudio). Mar 16 15:34:41 localhost rtkit-daemon[2184]: Demoted 4 threads.
Persists in F16: pulseaudio-0.9.23-1.fc16.x86_64 rtkit-0.10-1.fc16.x86_64 kernel-3.1.0-7.fc16.x86_64
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
No change: pulseaudio-0.9.23-1.fc16.x86_64 rtkit-0.10-1.fc16.x86_64 kernel-3.4.6-1.fc16.x86_64
Changing to NEW as requested by Oliver. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
We are kinda waiting for a sane kernel interface to be notified about system suspends, so that we can exclude scheduling issues causes by suspends from our usual logic.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
This still happens on F18, although less frequently now.
Updated for F17: pulseaudio-1.1-9.fc17.x86_64 rtkit-0.10-2.fc17.x86_64 kernel-3.8.13-100.fc17.x86_64
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
I still get this on F19.
See recent discussion on bug #1013775 comment #16 onwards (but note that that bug concentrates on a solution for RHEL6)
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Not tested on F21, but the fix proposed on bug #1013775 comment #19 onwards is not yet present in the fedora packages. On that basis, I'm updating the version. If anyone tests on F21 and finds different, please yell.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.