Bug 471759 - plymouthd causing high load
plymouthd causing high load
Product: Fedora
Classification: Fedora
Component: plymouth (Show other bugs)
x86_64 Linux
medium Severity low
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-11-15 17:35 EST by Noel
Modified: 2008-11-15 19:28 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-11-15 19:28:46 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Noel 2008-11-15 17:35:41 EST
Description of problem:
Seems that plymouthd is eating a lot of CPU, is it something to worry about?

top - 02:04:31 up 37 days, 10:43,  1 user,  load average: 1.11, 1.31, 1.28
Tasks: 207 total,   3 running, 204 sleeping,   0 stopped,   0 zombie
Cpu(s):  5.3%us, 24.8%sy,  0.0%ni, 69.2%id,  0.0%wa,  0.0%hi,  0.7%si,  0.0%st
Mem:   7534916k total,  7459808k used,    75108k free,   215108k buffers
Swap: 16771064k total,  1291076k used, 15479988k free,  4060748k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND                                                                   
  572 root      20   0 24004 1748   32 R 96.9  0.0  52537:00 plymouthd 

Version-Release number of selected component (if applicable):

How reproducible:
Every time I reboot the server

Steps to Reproduce:
1. top
Actual results:

Expected results:

Additional info:
Comment 1 Ray Strode [halfline] 2008-11-15 17:51:12 EST
This is after boot up is finished?

You're probably hitting bug 471498.

Does updating to the plymouth here:


and then running

/usr/libexec/plymouth/plymouth-update-initrd (as root)

fix things for you?
Comment 2 Noel 2008-11-15 19:28:46 EST
Fixed, yes most probably I hit bug 471498, updating to the latest version fixed the problem.

Thanks for the  quick answer.

Note You need to log in before you can comment on or make changes to this bug.