This isn't a real problem, but I guess it can point to something more serious - I recently upgraded to 2.6.36 linux kernel, and Load Average doesn't go under 1.0 - no matter how many tasks I have, no matter that CPU load is 0% and there are no processes waking up.
I wonder what could be causing this, and, well, if there's some nice way to debug this "problem".
I'm hoping that it won't lead to anything more serious (like some silent piece of kernel causing wakeups). The only problem that it makes now is probably that the 1.0 'bottom' doesn't look very healthy on graphs.
Can this be caused by tickless kernel?
I've seen this with weird things that are stalled on the scheduler, usually in a system call. If you have non-vanilla kernel modules, definitely start there, even if they are included in the kernel tree. Kernel elements with a user-space element are one way to describe this and you may find that the user-space daemon is hanging on an external event, which hangs the kernel step in-between, which hangs a program asking questions of the kernel.
Network-based filesystem, and not just those that communicate over Ethernet, are prime suspects.
Check for processes not in the runnable state with
ps -eo user,pid,stat,pcpu,args | grep -v " R"
And you can decode the status from this table taken from the
ps
man page.