From: Mark Lord <mlord@pobox.com>
To: Marc MERLIN <marc@merlins.org>
Cc: Tejun Heo <tj@kernel.org>,
linux-ide@vger.kernel.org, Larry Li <lil@marvell.com>,
hbailey@marvell.com
Subject: Re: decoding PMP errors with Marvel SATA controller
Date: Tue, 28 Jun 2011 23:53:37 -0400 [thread overview]
Message-ID: <4E0AA1C1.6020406@pobox.com> (raw)
In-Reply-To: <20110629034125.GC32153@merlins.org>
On 11-06-28 11:41 PM, Marc MERLIN wrote:
..
> So it seems it was a false alarm after all, I'll report back if I have
> problems again, but it looks like it's working solidly and for what it's
> worth with 5 drives and software raid 5, I can both read and write files
> at about 115MB/s, which isn't too shabby :)
Mmm.. power everything OFF, wait a few seconds,
then power on and verify that it all still works.
Thanks
--
Mark Lord
Real-Time Remedies Inc.
mlord@pobox.com
next prev parent reply other threads:[~2011-06-29 3:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-26 7:08 decoding PMP errors with Marvel SATA controller Marc MERLIN
2011-06-26 9:03 ` Tejun Heo
2011-06-26 17:38 ` Mark Lord
2011-06-27 0:06 ` Marc MERLIN
2011-06-27 1:29 ` Mark Lord
2011-06-27 1:58 ` Hubert Bailey
2011-07-06 20:55 ` Tim Small
2011-06-29 3:41 ` Marc MERLIN
2011-06-29 3:53 ` Mark Lord [this message]
2011-06-29 5:03 ` Marc MERLIN
2011-06-29 15:07 ` sata_mv WARNING: at drivers/ata/libata-sff.c:1322 Marc MERLIN
2011-06-29 16:03 ` Mark Lord
2011-07-12 14:29 ` Tejun Heo
2011-07-13 20:54 ` Gwendal Grignou
2011-07-13 22:41 ` Mark Lord
2011-07-14 7:19 ` Gwendal Grignou
2011-07-14 12:03 ` Mark Lord
2011-07-15 15:55 ` Marc MERLIN
2011-07-16 0:32 ` [PATCH] Prevent warning during PMP error recovery Gwendal Grignou
2011-07-16 0:34 ` Gwendal Grignou
2011-07-21 7:24 ` Tejun Heo
2011-07-21 7:25 ` Tejun Heo
2011-07-22 20:48 ` Gwendal Grignou
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=4E0AA1C1.6020406@pobox.com \
--to=mlord@pobox.com \
--cc=hbailey@marvell.com \
--cc=lil@marvell.com \
--cc=linux-ide@vger.kernel.org \
--cc=marc@merlins.org \
--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).