Comment 5 for bug 721896

Revision history for this message
User Unknown (user-unknown) wrote :

When kswapd0 starts going berserk on my machine, my swap is usually not or barely in use (0 or a few kiB of the 3GB). However, once kswapd0 is given some time to be wicked, it will fill up the swap considerately to a point (normally not full but a little over half full, I think; last night it was stuck at around 1.8GB after the fore-mentioned six hours), and then it seems to poke the data in the swap around for minutes and hours, having 'top' display slightly different, higher as well as lower values of memory usage every second without changing very much. During all that time it eats up one of my CPUs at a 100% -- by now, though, apparently with a lower process priority than in January and the first weeks of February, leaving my machine usable as opposed to before.

I guess I will try without suspend-to-RAM for a while to see if it occurs then, as well.