On 2016-10-03 18:38, John Andersen wrote:
On October 3, 2016 4:22:55 AM PDT, "Carlos E. R." <> wrote:
Still, why is George getting conflicting readings from Ksystemguard?
Dunno. I prefer output from top or atop.
Could it be that it is being blocked by whatever is using all the resources, such that it never actually sees the culprit in the list?
I don't think so...
Stuff happening in the kernel never shows up in top or Ksystemguard.
That maybe.
I would ask if the disk drive light was on solid during the slow down.
A failing drive sometimes acts like a super busy system, but doesn't show up in top.
No, because in that case it is the processes waiting for operations on the disk to complete, and they take eons. CPU usage is about nil, maybe the disk firmware is busy. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)