From: Marc MERLIN <marc@merlins.org>
To: Mark Lord <mlord@pobox.com>
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: Sun, 26 Jun 2011 17:06:14 -0700 [thread overview]
Message-ID: <20110627000614.GA5362@merlins.org> (raw)
In-Reply-To: <4E076E9E.9080400@pobox.com>
Speaking of which, what sata chips are recommended nowadays for PMP outside
sil24 cards?
On Sun, Jun 26, 2011 at 01:38:38PM -0400, Mark Lord wrote:
> > This sounds a lot like another recent PMP problem we had with marvell.
> > It could be that FIS-based switching doesn't work quite as well for
> > some reason.
>
> This all *used* to work with sata_mv.
> But I also recently noticed my sata_mv cards no longer work with the
> 4-port Marvell PMP here, and that combo definitely did work when I
> finished with it all (back around 2.6.29 or so).
I also used it but it was back 2-3 years ago now. I think it even worked
back in 2.6.18.
> I'm rather distracted here right now with broken internet connectivity,
> and hunting for new providers etc., so not likely to dig around on it.
>
> Perhaps Marc MERLIN could retest with an older kernel,
> say 2.6.32 or 2.6.29 even, and see what happens with those.
> Hopefully it will work there for him, and we'll have a starting
> point to bisect the issue.
So it's a bit difficult for me to get too much data on this since it's a
production system and downtime does come at somewhat of a premium.
However, if whoever may be able to work on it and see what broke (because it
almost works, I see all the drives on my PMP and I can read data somewhat, I
just get a lot of somewhat scary errors now) lets me know, if he/she has no
way to test him/herself, I'll see what I can do to help out and get to
replicate this with older kernels on either that server, or maybe another
machine I would have to build for it (trying repeatedly on production data,
even with backups, not so good :) ).
Thanks for the answer,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
next prev parent reply other threads:[~2011-06-27 0:06 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 [this message]
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
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=20110627000614.GA5362@merlins.org \
--to=marc@merlins.org \
--cc=hbailey@marvell.com \
--cc=lil@marvell.com \
--cc=linux-ide@vger.kernel.org \
--cc=mlord@pobox.com \
--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).