From: Tejun Heo <tj@kernel.org>
To: Carlos Bessa <carlos.bessa@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
Bruce Allen <ballen@gravity.phys.uwm.edu>
Subject: Re: Frequent head unload cycle - WD1600BEVE
Date: Sat, 04 Oct 2008 16:37:05 +0900 [thread overview]
Message-ID: <48E71D21.4@kernel.org> (raw)
In-Reply-To: <f56b605d0810020716p71fefacau709ce26dd678632c@mail.gmail.com>
Carlos Bessa wrote:
> Hi,
> sorry but it took me a while to get back to this.
> I've been monitoring the load_cycle_increase in the last hours and,
> depending on the use of the computer it can climb up really fast. Just
> readin/browsing the web and working on some word processor and it
> increases at about 60 per hour, even higher if i'ts just idling. The
> increase will be less of course if i'm doing some more intensive tasks,
> probably with more frequent hard drive usage.
> And just to clear the fact about the hard drive having been replaced.
> I's a completely diferent model/brand. The older one is a Fujitsu 80GB
> hard drive, which never suffered from this problem (at least i didn't
> noticed it). It was replaced by this WD unit, simply due to higher
> capacity.
Okay, what seems to be going on is that the BIOS is programming the
drive the same way as the original one and the new one is interpreting
the same value differently - much more aggressively. Aiee... This
really requires a dynamic solution. Can you please apply workaround
manually for now?
Bruce, please ping me when you come back.
Thanks.
--
tejun
prev parent reply other threads:[~2008-10-04 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 14:01 Frequent head unload cycle - WD1600BEVE Carlos Bessa
2008-09-29 7:29 ` Tejun Heo
2008-09-30 17:35 ` Tejun Heo
[not found] ` <f56b605d0810020716p71fefacau709ce26dd678632c@mail.gmail.com>
2008-10-04 7:37 ` Tejun Heo [this message]
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=48E71D21.4@kernel.org \
--to=tj@kernel.org \
--cc=ballen@gravity.phys.uwm.edu \
--cc=carlos.bessa@gmail.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).