Graham, after testing this by leaving my machine running for several days, I could confirm that it seems not to be directly related to suspend-to-ram. However, I got the feeling that after suspend-to-ram it seems more likely to occur sooner. As an example: with my machine running continuously for days, it took more than three days for this issue to become really bad; with suspend-to-ram, however (computer normally runs far more than 12 hours a day, being suspended over night), it usually already occurred on the second day. Though, I believe, never on the first day.
I don't know if I understood you correctly: does this happen for you directly after resume from suspend-to-ram? At least for me the issue did never occur immediately after resume. Whenever it occurred, it was sporadically and several hours afterwards, but I never really saw any pattern to it, neither did I notice any correlation with dpkg or update- manager. Oh, and Arkadiy's server runs 24/7 without any hibernation or such (see post #4). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/721896 Title: kswapd0 100% cpu usage -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
