From: Jens Axboe <axboe@suse.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>, Andrew Morton <akpm@osdl.org>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Subject: Re: Strange IO behaviour on wakeup from sleep
Date: Wed, 27 Oct 2004 08:24:27 +0200 [thread overview]
Message-ID: <20041027062427.GE15910@suse.de> (raw)
In-Reply-To: <1098845804.606.4.camel@gaston>
On Wed, Oct 27 2004, Benjamin Herrenschmidt wrote:
> 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'm not sure yet how to track that down, it could be the IO scheduler
> getting messed up on wakeup for some reason. Any clue appreciated.
Just saw the same thing here yesterday. It's not io scheduler related
(happened with even noop, if you switch to it), but apart from that I
have no clues so far either.
--
Jens Axboe
next prev parent reply other threads:[~2004-10-27 6:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 2:56 Strange IO behaviour on wakeup from sleep Benjamin Herrenschmidt
2004-10-27 6:24 ` Jens Axboe [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2004-10-27 14:18 Zachary Amsden
2004-10-27 22:40 ` Benjamin Herrenschmidt
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=20041027062427.GE15910@suse.de \
--to=axboe@suse.de \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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.