From: Mark Lord <liml@rtr.ca>
To: David Greaves <david@dgreaves.com>
Cc: Tejun Heo <htejun@gmail.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
IDE Linux <linux-ide@vger.kernel.org>,
ballen@gravity.phys.uwm.edu
Subject: Re: 2.6.22-rc3 hibernate(?) disables SMART on ide
Date: Tue, 05 Jun 2007 11:33:29 -0400 [thread overview]
Message-ID: <46658249.8030606@rtr.ca> (raw)
In-Reply-To: <466526FA.3090506@dgreaves.com>
David Greaves wrote:
> Mark Lord wrote:
>> That's odd. Could you try that again,
>> with the latest (either v7.3 or v7.4) version of hdparm
>> (from sourceforge) ?
>
> Using Debian's 7.3 via apt-get experimental - is that OK or would you like me to
> compile the upstream?
No, what you have is good, thanks.
> cu:~# hdparm -K1 /dev/hda
>
> /dev/hda:
> setting drive keep features to 1 (on)
> HDIO_DRIVE_CMD(keepsettings) failed: Input/output error
>
> dmesg:
> skge eth0: Link is up at 1000 Mbps, full duplex, flow control both
> hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hda: drive_cmd: error=0x04 { DriveStatusError }
> ide: failed opcode was: 0xef
I just find it odd that the drive rejects the command,
but Seagate do seem to be the first to drop older features nowadays.
But I thought their PATA units might have kept that functionality.
I have some modern seagate SATA drives here -- I'll try it on those too,
just for my own education.
Thanks.
next prev parent reply other threads:[~2007-06-05 15:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 21:41 2.6.22-rc3 hibernate(?) disables SMART on ide David Greaves
2007-06-02 9:45 ` Tejun Heo
2007-06-02 21:53 ` David Greaves
2007-06-04 16:29 ` Mark Lord
2007-06-04 17:22 ` David Greaves
2007-06-05 4:17 ` Mark Lord
2007-06-05 9:03 ` David Greaves
2007-06-05 15:33 ` Mark Lord [this message]
[not found] <8rnax-6XX-11@gated-at.bofh.it>
[not found] ` <8rA7H-1B4-1@gated-at.bofh.it>
2007-06-02 21:27 ` Bodo Eggert
2007-06-02 22:18 ` Jeff Garzik
2007-06-02 22:22 ` Alan Cox
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=46658249.8030606@rtr.ca \
--to=liml@rtr.ca \
--cc=ballen@gravity.phys.uwm.edu \
--cc=david@dgreaves.com \
--cc=htejun@gmail.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 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.