From: Myron Stowe <myron.stowe@gmail.com>
To: Xiangliang Yu <yuxiangl@marvell.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>, yxlraid <yxlraid@gmail.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] PCI: fix system hang issue of Marvell SATA host controller
Date: Sat, 16 Mar 2013 18:13:48 -0600 [thread overview]
Message-ID: <CAL-B5D15UP0-z+4whBVxsbHm6_43DEK5+BOr=PZYsc-DNB7VrQ@mail.gmail.com> (raw)
In-Reply-To: <CAL-B5D0JOTBTRhh-i=DkiUjSsid1v408DE5nj_R2qvaHDtEQ=g@mail.gmail.com>
On Thu, Mar 14, 2013 at 9:03 AM, Myron Stowe <myron.stowe@gmail.com> wrote:
> On Wed, Mar 13, 2013 at 3:40 AM, Xiangliang Yu <yuxiangl@marvell.com> wrote:
>> Hi, Bjorn
>>
>>> >> > Now, the situation is like this:
>>> >> > I captured the PCIE trace with analyzer and found that 1st BE is 0x1111
>>> >> > when
>>> >> > accessing IO port space. But 9125 spec has some limitation, and the BE
>>> >> > must
>>> >> > be
>>> >> > 0x0100, to access the 2nd byte only. So, the chip will go to bad.
>>> >>
>>> >> Great, this is new, interesting, data. Is the 9125 spec publicly
>>> >> accessible and/or could you elaborate on the "some limitation"
>>> >> comment?
>>> > 9125 spec is publicly accessible.
>> If you can't see the pic, please open the attachment. Thanks!
>
> Neither Bjorn nor myself could see the pic (from the previous thread
> or this thread's attachment).
>
>>
>>
Just an FYI that I proposed a different tact at
https://lkml.org/lkml/2013/3/16/168. For those following this thread
you may want to start following that thread also.
next prev parent reply other threads:[~2013-03-17 0:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 14:29 [PATCH 2/2] PCI: fix system hang issue of Marvell SATA host controller yxlraid
2013-03-07 16:28 ` Bjorn Helgaas
2013-03-08 3:07 ` Xiangliang Yu
2013-03-08 4:19 ` Bjorn Helgaas
2013-03-08 6:51 ` Xiangliang Yu
2013-03-08 17:01 ` Bjorn Helgaas
2013-03-09 14:49 ` Xiangliang Yu
2013-03-09 23:24 ` Myron Stowe
[not found] ` <F766E4F80769BD478052FB6533FA745D25F440A64D@SC-VEXCH4.marvell.com>
2013-03-11 21:19 ` Myron Stowe
[not found] ` <F766E4F80769BD478052FB6533FA745D25F440A9C6@SC-VEXCH4.marvell.com>
2013-03-12 16:21 ` Bjorn Helgaas
2013-03-13 9:40 ` Xiangliang Yu
2013-03-14 15:03 ` Myron Stowe
2013-03-17 0:13 ` Myron Stowe [this message]
2013-03-21 16:00 ` Myron Stowe
2013-03-09 3:18 ` Myron Stowe
2013-03-14 4:16 ` Robert Hancock
2013-03-14 15:02 ` Myron Stowe
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='CAL-B5D15UP0-z+4whBVxsbHm6_43DEK5+BOr=PZYsc-DNB7VrQ@mail.gmail.com' \
--to=myron.stowe@gmail.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=yuxiangl@marvell.com \
--cc=yxlraid@gmail.com \
/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.