From: Zachary Amsden <zach@vmware.com>
To: benh@kernel.crashing.org, linux-kernel@vger.kernel.org
Subject: Re: Strange IO behaviour on wakeup from sleep
Date: Wed, 27 Oct 2004 07:18:39 -0700 [thread overview]
Message-ID: <417FAE3F.20908@vmware.com> (raw)
>
>
>Hi !
>
>Not much datas at this point yet, but paulus and I noticed that current
>bk (happened already last saturday or so) has a very strange problem
>when waking up from sleep (suspend to ram) on our laptops.
>
>This doesn't seem to be directly related to the PM code, at least not
>the arch one, as far as I know. The IDE throughput goes down to less
>than 100k/sec on hdparm. We haven't yet figured out where the time is
>lost, the disk seem to properly be restored to UDMA4 as usual, that code
>didn't change for ages, I don't think it's a problem at that level in
>IDE.
>
>
I would tend to be very suspicious of DMA not being restored correctly
because on some systems, prior to or during suspend, DMA may be shutdown
to conserve power. There are changes afloat that touch suspend/resume,
and there have been historical problems with DMA not being restored
properly after wakeup on some laptops.
Although this may be another shot in the dark, it might rule out the DMA
problem: try cat /proc/ide/yourchipset before and after suspend and
note any changes. Failing that, use hdparm to turn off DMA before
suspend and see if the performance suffers to the same degree as after
wakeup.
Zachary Amsden
zach@vmware.com
next reply other threads:[~2004-10-27 14:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 14:18 Zachary Amsden [this message]
2004-10-27 22:40 ` Strange IO behaviour on wakeup from sleep Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2004-10-27 2:56 Benjamin Herrenschmidt
2004-10-27 6:24 ` Jens Axboe
2004-10-27 11:20 ` Tim Schmielau
2004-10-27 12:06 ` Benjamin Herrenschmidt
2004-10-27 12:13 ` Tim Schmielau
2004-10-27 13:01 ` Nigel Cunningham
2004-10-27 13:08 ` Benjamin Herrenschmidt
2004-10-27 13:20 ` Nigel Cunningham
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=417FAE3F.20908@vmware.com \
--to=zach@vmware.com \
--cc=benh@kernel.crashing.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.