exactly, I've seen this on a 2.2.16 box that went deep into swap. Although
it didn't lock up, kswapd was using most of the CPU time during a swapoff.
-mh
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/