From: Jeff Garzik <jgarzik@pobox.com>
To: "Barry K. Nathan" <barryn@pobox.com>
Cc: Jens Axboe <axboe@suse.de>, Pavel Machek <pavel@suse.cz>,
Dave Jones <davej@redhat.com>,
marcelo.tosatti@cyclades.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] laptop mode
Date: Tue, 14 Oct 2003 13:50:28 -0400 [thread overview]
Message-ID: <3F8C3764.1070305@pobox.com> (raw)
In-Reply-To: <20031012224519.GA9043@ip68-4-255-84.oc.oc.cox.net>
Barry K. Nathan wrote:
> On Sat, Oct 11, 2003 at 03:59:43PM +0200, Jens Axboe wrote:
>
>>Not very likely, imho. People have been using spin down with hdparm for
>>years (in Linux and elsewhere), while acoustic management is a bit more
>>esoteric.
>
>
> I'm having trouble finding this on Google now, but I've heard rumors
> over the years of old Fireball drives corrupting data if they receive
> write commands too soon after spinning up (i.e., the drive doesn't
> bother waiting to spin up fully first). Maybe I'm not remembering the
> details correctly, but it was something about the drive trying to act on
> commands before it was fully spun up and malfunctioning as a result.
Well, there exists devices which comply with the delayed spin-up part of
ATA/ATAPI specification... maybe our code doesn't cover that. I don't
put much stock in rumors, but they are occasionally clues... :)
Jeff
next prev parent reply other threads:[~2003-10-14 17:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200310091103.h99B31ug014566@hera.kernel.org>
2003-10-09 14:02 ` [PATCH] laptop mode Jeff Garzik
2003-10-09 14:05 ` Jens Axboe
2003-10-09 14:17 ` Dave Jones
2003-10-09 14:26 ` Jens Axboe
2003-10-11 11:49 ` Pavel Machek
2003-10-11 13:59 ` Jens Axboe
2003-10-12 22:45 ` Barry K. Nathan
2003-10-14 17:50 ` Jeff Garzik [this message]
2003-10-09 14:09 ` Marcelo Tosatti
2003-10-09 14:11 ` Jens Axboe
2003-10-09 14:18 ` Jeff Garzik
2003-10-09 14:21 ` Jens Axboe
2003-10-09 14:28 ` Dave Jones
2003-10-17 19:42 ` Jan Rychter
2003-10-18 12:52 ` Jens Axboe
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=3F8C3764.1070305@pobox.com \
--to=jgarzik@pobox.com \
--cc=axboe@suse.de \
--cc=barryn@pobox.com \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=pavel@suse.cz \
/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