From: Greg Stark <gsstark@mit.edu>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Greg Stark <gsstark@mit.edu>,
linux-kernel@vger.kernel.org,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: SMART support for libata
Date: 08 Jun 2005 12:59:40 -0400 [thread overview]
Message-ID: <87br6g6ayr.fsf@stark.xeocode.com> (raw)
In-Reply-To: <41B7EFA3.8000007@pobox.com>
FWIW here's a report of a bit of a problem with libata-dev and SMART support.
I'm not actually clear whether this is the fault of libata or the traditional
IDE drivers though.
I built 2.6.12rc4 with 2.6.11-bk6-libata-dev1.patch applied.
(I had to fix up a couple things that didn't apply against 2.6.12)
I updated to 5.33 per someone's suggestion on the mailing list and SMART
support started working. Yay. At that point I noticed my old PATA drive was
getting really hot so I put it to sleep with "hdparm -Y".
Now whenever smartd probes that drive my system freezes for a few seconds and
I get this in my syslog:
Jun 8 12:49:36 stark kernel: hda: status timeout: status=0xd0 { Busy }
Jun 8 12:49:36 stark kernel:
Jun 8 12:49:36 stark kernel: ide: failed opcode was: 0xe5
I'm fine with failing to get SMART info from a sleeping drive. I'm not clear
whether it's actually possible to get data back or not though it would be nice
to know how much sleeping is lowering the drive temperature. But freezing the
machine is unkind.
--
greg
next prev parent reply other threads:[~2005-06-08 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y8g8r4y6.fsf@stark.xeocode.com>
2004-12-09 6:24 ` SMART support for libata Jeff Garzik
2005-06-08 16:59 ` Greg Stark [this message]
2005-06-08 18:52 ` Mark Lord
2005-06-09 3:08 ` Greg Stark
2005-06-09 15:25 ` Mark Lord
2005-06-09 18:13 ` Greg Stark
2005-06-10 6:38 ` Jens Axboe
2005-06-10 15:35 ` Greg Stark
2005-06-11 19:25 ` Adrian Bunk
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=87br6g6ayr.fsf@stark.xeocode.com \
--to=gsstark@mit.edu \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.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 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).