Comment 38 for bug 574910

Jonas thank you for that information.

I am aware of the resources to track down high load average. I have iftop/iotop/top/vmstat/iostat and sar installed. The article fails to mention vmstat and SAR at all. Iftop/top/iotop are useful only in that they all report that nothing is "hogging" the resources. At one point it was even suggested, in another thread, that there was some sort of 'scheduler' issue and that running iftop would reduce the load average. I have not found that to be true.

FYI: I have been tracking down rouge processes since AIX 3.2.3, Solaris 2.4 and Slackware running the 0.9x kernels. The issue is systemic and not point based. To reiterate: a VM running 10.04 (with all patches) had load averages of 0.70 or above for more than 80 percent of the day. The only things running on the host were two shells in two tabs of a gnome terminal and Firefox with no java/js running (noscript blocked) and pidgin. Sar did/does not show any processes being stuck. Since no disk I/O, or network I/O would have been operating there was no reason for the load average to be above 0.01. A systemic issue indicates a Kernel issue (particularly since SAR does not report any unusual disk or I/O issues. I am sorry if I gave the impression that I was new at this.