Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#31756 - [systemd] Uses 100% CPU
Attached to Project:
Arch Linux
Opened by Adam Hani Schakaki (krzd) - Monday, 01 October 2012, 20:54 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 02 October 2012, 16:58 GMT
Opened by Adam Hani Schakaki (krzd) - Monday, 01 October 2012, 20:54 GMT
Last edited by Dave Reisner (falconindy) - Tuesday, 02 October 2012, 16:58 GMT
|
DetailsDescription:
After updating to systemd, two random processes are using 100% CPU after booting. Its always different processes, but that always means, that it will use 2 Threads completely. Downgrading to 192 solves it again. Additional info: * systemd 193-1 Steps to reproduce: * Upgrade systemd to 193-1 * Reboot |
This task depends upon
Closed by Dave Reisner (falconindy)
Tuesday, 02 October 2012, 16:58 GMT
Reason for closing: Not a bug
Tuesday, 02 October 2012, 16:58 GMT
Reason for closing: Not a bug
Comment by Dave Reisner (falconindy) -
Tuesday, 02 October 2012, 00:03 GMT
You have a failing service. Please look at your journal.
Comment by Adam Hani Schakaki (krzd) -
Tuesday, 02 October 2012, 16:11 GMT
True, altough i couldn't really identify it. Anyway using the new linux 3.6-1 there is now problem with systemd 193-1. So wierd problem, but somehow solved.
Comment by Dave Reisner (falconindy) -
Tuesday, 02 October 2012, 16:58 GMT
Yes, and next time this happens you'll see a lot of "service foo failed to start" spam in your journal. This has nothing to do with the kernel.