From: "ANEZAKI, Akira" <fireblade1230@yahoo.co.jp>
To: Gwendal Grignou <gwendal@google.com>
Cc: "ANEZAKI, Akira" <fireblade1230@yahoo.co.jp>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Mark Lord <kernel@teksavvy.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: Fwd: libata-pmp patch for 3.2.x and later for eSATA Port Multiplier Sil3726
Date: Fri, 23 Mar 2012 02:55:40 +0900 [thread overview]
Message-ID: <4F6B679C.60004@yahoo.co.jp> (raw)
In-Reply-To: <CAMHSBOVD4wAtwAravVkDjyWV+Nwtuybt=yae=26PcGxxirw=Lg@mail.gmail.com>
Hello Gwendal,
Thank you for your information.
I think ata8 might different from other 3 PMPs. I'll try to update all
firmware but it is running resync on broken RAID now. So I can't do it soon.
By the way, both of ata8 and ata9 loses some HDDs also. Are those
affected by PMPs on ata7 and ata10? Why 3.1.x driver can work?
Best Regards,
Akira
> Now I see your problem. Indeed on ata7, ata10, we have a problem.
> I notice however some messages I did not see before:
>>> [ 4.856382] ata7.15: Port Multiplier 1.1, 0x1095:0x3726 r23, 6 ports, feat 0x1/0x9
>>> [ 4.858742] ata7.00: hard resetting link
>>> [ 14.843039] ata7.00: softreset failed (timeout)
>>> [ 17.836402] ata7.15: qc timeout (cmd 0xe4)
> The later indicates that the PMP is stuck and the host can not read
> its internal register.
> Is it possible that the PMP in these 4 enclosures you are using have a
> different firmware than the other ones?
> Firmware 1.0114 is available at:
> http://www.siliconimage.com/support/searchresults.aspx?pid=26&cat=23
>
> From the release notes:
> """- Fix SRST and initial two RegFIS Problem."""
>
> Gwendal.
next prev parent reply other threads:[~2012-03-22 17:55 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201203122030.q2CKUjb2022067@bzweb02.app.bz.hst.phx2.redhat.com>
2012-03-13 4:28 ` libata-pmp patch for 3.2.x and later for eSATA Port Multiplier Sil3726 ANEZAKI, Akira
2012-03-13 16:56 ` Fwd: " Mark Lord
2012-03-18 18:35 ` ANEZAKI, Akira
2012-03-21 9:09 ` Gwendal Grignou
2012-03-22 4:36 ` ANEZAKI, Akira
2012-03-22 8:14 ` black
2012-03-22 8:16 ` ANEZAKI, Akira
2012-03-22 12:51 ` Gwendal Grignou
2012-03-22 14:02 ` ANEZAKI, Akira
2012-03-22 16:16 ` Gwendal Grignou
2012-03-22 16:16 ` Gwendal Grignou
2012-03-22 17:55 ` ANEZAKI, Akira [this message]
2012-03-23 5:14 ` Gwendal Grignou
2012-03-23 6:40 ` ANEZAKI, Akira
2012-03-23 8:31 ` Gwendal Grignou
2012-03-23 9:59 ` ANEZAKI, Akira
2012-03-25 1:19 ` ANEZAKI, Akira
2012-03-25 15:28 ` Gwendal Grignou
2012-03-26 0:41 ` ANEZAKI, Akira
2012-03-26 1:42 ` black
2012-03-26 1:46 ` ANEZAKI, Akira
2012-03-26 2:30 ` ANEZAKI, Akira
2012-03-26 9:50 ` ANEZAKI, Akira
2012-03-26 11:26 ` ANEZAKI, Akira
2012-03-27 11:17 ` Gwendal Grignou
2012-03-27 12:26 ` ANEZAKI, Akira
2012-03-27 12:26 ` ANEZAKI, Akira
2012-03-27 13:18 ` ANEZAKI, Akira
2012-03-27 13:18 ` ANEZAKI, Akira
2012-03-27 13:46 ` black
2012-03-27 13:46 ` black
2012-03-27 14:10 ` ANEZAKI, Akira
2012-03-27 14:10 ` ANEZAKI, Akira
2012-03-29 6:32 ` Gwendal Grignou
2012-03-29 7:19 ` ANEZAKI, Akira
2012-03-29 7:19 ` ANEZAKI, Akira
2012-03-28 5:22 ` ANEZAKI, Akira
2012-03-28 5:22 ` ANEZAKI, Akira
2012-03-28 5:29 ` ANEZAKI, Akira
2012-03-28 5:29 ` ANEZAKI, Akira
2012-03-29 6:08 ` Gwendal Grignou
2012-03-29 6:08 ` Gwendal Grignou
2012-03-29 6:27 ` ANEZAKI, Akira
2012-03-29 6:27 ` ANEZAKI, Akira
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=4F6B679C.60004@yahoo.co.jp \
--to=fireblade1230@yahoo.co.jp \
--cc=gwendal@google.com \
--cc=jgarzik@pobox.com \
--cc=kernel@teksavvy.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.