From: Diego Rondini <panda84@inwind.it>
To: linux-ide@vger.kernel.org
Subject: [Affected devices] Frequent head unload under Linux
Date: Tue, 30 Sep 2008 10:53:42 +0200 [thread overview]
Message-ID: <48E1E916.9080202@inwind.it> (raw)
As asked in this page:
http://ata.wiki.kernel.org/index.php/Known_issues
I report you of two notebook with this issue.
Unfortunately I haven't access to these notebooks anymore (I installed
Linux in an install party) so I cannot attach the output of the several
commands.
Both of them did very frequent unloads, for sure more than 5 per minute,
but maybe even more. So that's more than 180 per hour!
The notebook were very different, the first was a 5 years old HP Compaq
NX 9005 with a 30GB drive:
http://h18000.www1.hp.com/products/quickspecs/11602_na/11602_na.HTML#Storage
Probably the drive was a Hitachi model:
http://www.itreviews.co.uk/hardware/h504.htm
The other one was a brand new HP Compaq F760EL with a 120GB drive, but I
didn't managed to know which kind of drive it's using...
Sorry for the incomplete informations provided, hope it's better than
nothing.
Bye,
Diego
next reply other threads:[~2008-09-30 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 8:53 Diego Rondini [this message]
2008-10-01 3:02 ` [Affected devices] Frequent head unload under Linux Tejun Heo
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=48E1E916.9080202@inwind.it \
--to=panda84@inwind.it \
--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 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.