Hi. I've noticed that with recent kernels (starting somewhere between 2.6.20 and 2.6.22) I sometimes get *lots* of disk activity on resume from suspend to ram. About 2/3 of the time, the system resumes normally but in the remaining 1/3 of the time, the hard drive light stays on almost solid and the machine is very, very slow to respond. The only way I've found to reliably recover from this is if I can get to a command prompt fast enough and do "shutdown -r now". There's not much cpu activity at all, it just seems to be disk io that's killing interactivity. This also happens if I resume just from an empty gnome desktop with no applications running, so I don't think it's due to swapping.
Some kernels affected: 2.6.22, 2.6.23+hrt patches, Ubuntu Gutsy kernel (2.6.22-14). These are all 64-bit kernels running on an HP nx6125 laptop - single-core Turion 64 processor, 1 gig of ram. To the best of my recollection, this problem did *not* appear with 2.6.20. I put some dmesg output from the vm block dumping and some vmstat output at http://nullinfinity.org/tmp/s2ram/ . The dmesg logs are from the same resume, just a little while apart. The vmstat is from a different resume. Any workarounds, patches, tips for further debugging etc would be appreciated. - Johan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
