Bug 471759 - plymouthd causing high load
Summary: plymouthd causing high load
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: plymouth
Version: rawhide
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-11-15 22:35 UTC by Noel
Modified: 2008-11-16 00:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-11-16 00:28:46 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Noel 2008-11-15 22:35:41 UTC
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):
plymouth-0.6.0-0.2008.11.10.5.fc10.x86_64

How reproducible:
Every time I reboot the server

Steps to Reproduce:
1. top
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Ray Strode [halfline] 2008-11-15 22:51:12 UTC
This is after boot up is finished?

You're probably hitting bug 471498.

Does updating to the plymouth here:

http://koji.fedoraproject.org/koji/buildinfo?buildID=69803

and then running

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

fix things for you?

Comment 2 Noel 2008-11-16 00:28:46 UTC
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.