public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Brannlund <johan_brn@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Lots of disk activity on resume from s2ram
Date: Mon, 15 Oct 2007 21:53:21 +0000 (UTC)	[thread overview]
Message-ID: <pan.2007.10.15.21.53.21@yahoo.com> (raw)

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


             reply	other threads:[~2007-10-15 23:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-15 21:53 Johan Brannlund [this message]
2007-10-16 12:12 ` Lots of disk activity on resume from s2ram Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pan.2007.10.15.21.53.21@yahoo.com \
    --to=johan_brn@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox