From: Greg Freemyer <greg.freemyer@gmail.com>
To: linux-ide@vger.kernel.org
Subject: Re: 'hdparm -C' problems with libata-dev
Date: Tue, 12 Apr 2005 16:55:48 -0400 [thread overview]
Message-ID: <87f94c370504121355e9231e2@mail.gmail.com> (raw)
In-Reply-To: <20050412140002.GC27920@tuxdriver.com>
On Apr 12, 2005 10:00 AM, John W. Linville <linville@tuxdriver.com> wrote:
> On Fri, Apr 08, 2005 at 04:03:21PM +0200, Gerald Hopf wrote:
>
> > Is there anything i can do to make this ('hdparm -C') work? Is this a
> > libata bug or missing feature? A Seagate Firmware bug? A hdparm problem?
> > Or just not possible with SATA Drives?
>
> Sounds like a bug w/ my implementation of HDIO_DRIVE_CMD for libata.
> However, I have yet to take the opportunity to track it down. Plus,
> I'll be taking a little vacation over the coming weekend, so I likely
> won't get to this until sometime next week... :-(
>
> Until then, please feel free to experiment more w/ hdparm to see if
> there are any other problems w/ hdparm on SATA. Please copy me on
> reports of any such problems (or send them to me directly). Thanks!
>
> John
> --
> John W. Linville
> linville@tuxdriver.com
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
I reported that "hdparm -r" was not working with PATA drives a couple
months ago. I got no feedback, but if someone can test it with SATA I
would be curious if it works.
Greg
--
Greg Freemyer
The Norcross Group
Forensics for the 21st Century
prev parent reply other threads:[~2005-04-12 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 14:03 'hdparm -C' problems with libata-dev Gerald Hopf
2005-04-12 14:00 ` John W. Linville
2005-04-12 20:55 ` Greg Freemyer [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=87f94c370504121355e9231e2@mail.gmail.com \
--to=greg.freemyer@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).