From: Mark Lord <kernel@start.ca>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
Aaron Lu <aaron.lu@intel.com>,
bladud@gmail.com, Joe Sapp <nixphoeni+kernel@gmail.com>,
Alberto Mattea <support.intranet@libero.it>,
Peter Dons Tychsen <donpedro@tdcadsl.dk>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Tejun Heo <tj@kernel.org>, Jeff Garzik <jgarzik@pobox.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: STANDBY IMMEDIATE failed on NVIDIA MCP5x controllers when system suspend
Date: Tue, 12 Mar 2013 12:34:08 -0400 [thread overview]
Message-ID: <513F5900.9030503@start.ca> (raw)
In-Reply-To: <CADLC3L0nM+3ttR8V8cCOZWGY+eJqGZdmKiTRieYr_d+Xqh36UA@mail.gmail.com>
On 13-03-11 03:30 PM, Robert Hancock wrote:
..
> I'm sure there are some SSDs that do violate their data integrity
> commitments - a while ago some tests were done (don't have a link
> handy and I don't think they identified the actual vendor/model of the
> drives in any case) but there were definitely some SSDs that did do
> nasty things like trash unrelated data if power was lost while
> writing, etc. So we definitely don't want to risk this sort of thing
> occurring on a normal power-off or suspend.
Just about all current SATA SSDs advertise having some form(s)
of "background garbage collection". That "feature" has always concerned me,
because of the real possibility of power being removed (system shutdown)
while the drive firmware is in the midst of re-shuffling my data around.
One would hope that "STANDBY IMMEDIATE" is taken by the drive
as a signal to stop that fussing about and prepare for full/sudden power-off.
next prev parent reply other threads:[~2013-03-12 16:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 3:42 STANDBY IMMEDIATE failed on NVIDIA MCP5x controllers when system suspend Aaron Lu
2013-03-11 8:49 ` James Bottomley
2013-03-11 13:51 ` Aaron Lu
2013-03-11 14:34 ` James Bottomley
2013-03-11 15:00 ` Alan Stern
2013-03-12 2:53 ` Aaron Lu
2013-03-12 12:10 ` James Bottomley
2013-03-12 13:46 ` Aaron Lu
2013-03-12 15:08 ` Alan Stern
2013-03-11 14:35 ` Robert Hancock
2013-03-11 14:51 ` James Bottomley
2013-03-11 19:30 ` Robert Hancock
2013-03-12 16:34 ` Mark Lord [this message]
2013-03-11 20:01 ` Peter Dons Tychsen
2013-03-12 2:34 ` Aaron Lu
2013-03-12 23:21 ` Peter Dons Tychsen
2013-03-13 2:10 ` Robert Hancock
2013-03-13 2:36 ` Aaron Lu
2013-03-13 4:50 ` Simeon Bird
2013-03-13 5:07 ` Aaron Lu
2013-03-13 5:16 ` Simeon Bird
2013-03-13 5:41 ` Aaron Lu
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=513F5900.9030503@start.ca \
--to=kernel@start.ca \
--cc=James.Bottomley@hansenpartnership.com \
--cc=aaron.lu@intel.com \
--cc=bladud@gmail.com \
--cc=donpedro@tdcadsl.dk \
--cc=hancockrwd@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nixphoeni+kernel@gmail.com \
--cc=stern@rowland.harvard.edu \
--cc=support.intranet@libero.it \
--cc=tj@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).