On Thu, Jan 17, 2013 at 08:01:18AM +0000, Peter Robinson wrote:
On Thu, Jan 17, 2013 at 5:51 AM, Daniel Veillard
<veillard(a)redhat.com> wrote:
> How do I find out the stuck process leading to this extra load ?
try atop. I find it gives a lot of extra information about processes
Hum, compared to a normal 'desktop' box, it list one process
as being in #tslpu state, i.e. sleep ininteruptible, and I wonder if
that's what is accounted for it. There is basically only 2 processes
active in the system: atop and ksoftirqd/0 which is basically the
kernel interrupt handler (well there is also ssh but it usually doesn't
even shows up).
The process in D state is apparently a kernel usb thread
root 18 0.0 0.0 0 0 ? D Jan16 0:00 [usb-hardware-sc]
it is present in that state on both boxes (no USB device connected, but
if I plug mouse or keyboard they work just fine).
Daniel
--
Daniel Veillard | Open Source and Standards, Red Hat
veillard(a)redhat.com | libxml Gnome XML XSLT toolkit
http://xmlsoft.org/
http://veillard.com/ | virtualization library
http://libvirt.org/