From: Tino Keitel <tino.keitel@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Keeping track of spin-down/spin-up and causes of spin-up?
Date: Tue, 8 Jul 2008 09:48:18 +0200 [thread overview]
Message-ID: <20080708074818.GA341@dose.home.local> (raw)
In-Reply-To: <jwvskuku9jr.fsf-monnier+gmane.linux.kernel@gnu.org>
On Tue, Jul 08, 2008 at 03:25:18 -0400, Stefan Monnier wrote:
> I clearly remember seeing a reference to some system that allowed to
> keep track of causes of disk spin-up, but Google seems to say
> I'm deluded. [ Or maybe my memory confused it for the facility used by
> powertop to keep track of causes of CPU wake-ups? ]
>
> In any case, I have a machine here whose disk keeps spinning back up
> on a regular basis, and I can't seem to find any correlated event.
> Is there a tool that can help me track down the reason why the disk
> is accessed?
See Documentation/laptops/laptop-mode.txt, the notes regarding
block_dump.
Regards,
Tino
next prev parent reply other threads:[~2008-07-08 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 7:25 Keeping track of spin-down/spin-up and causes of spin-up? Stefan Monnier
2008-07-08 7:48 ` Tino Keitel [this message]
2008-07-08 8:07 ` Elias Oltmanns
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=20080708074818.GA341@dose.home.local \
--to=tino.keitel@gmx.de \
--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