From: Johannes Thumshirn <jthumshirn@suse.de>
To: Don Dutile <ddutile@redhat.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Alexander Graf <agraf@suse.de>, Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH 2/2] pci: Don't set RCB bit in LNKCTL if the upstream bridge hasn't
Date: Tue, 15 Nov 2016 13:58:22 +0100 [thread overview]
Message-ID: <20161115125822.sna3oz56prmrelgc@linux-x5ow.site> (raw)
In-Reply-To: <5829E373.1070901@redhat.com>
On Mon, Nov 14, 2016 at 11:16:51AM -0500, Don Dutile wrote:
> On 11/14/2016 06:56 AM, Johannes Thumshirn wrote:
> > On Wed, Nov 09, 2016 at 11:11:40AM -0600, Bjorn Helgaas wrote:
> > > Hi Johannes,
> > >
> > > On Wed, Nov 02, 2016 at 04:35:52PM -0600, Johannes Thumshirn wrote:
> > > > The Read Completion Boundary (RCB) bit must only be set on a device or
> > > > endpoint if it is set on the root complex.
> > > >
> > > > Certain BIOSes erroneously set the RCB Bit in their ACPI _HPX Tables
> > > > even if it is not set on the root port. This is a violation to the PCIe
> > > > Specification and is known to bring some Mellanox Connect-X 3 HCAs into
> > > > a state where they can't map their firmware and go into error recovery.
> > > >
> > > > BIOS Information
> > > > Vendor: IBM
> > > > Version: -[A8E120CUS-1.30]-
> > > > Release Date: 08/22/2016
> > >
> > > This seems like a pretty serious problem (sounds like maybe the HCA is
> > > completely useless?)
> >
> > Correct.
> >
> > >
> > > Can you point us at a bugzilla or other problem report? It's nice to
> > > have details of what this looks like to a user, so people who trip
> > > over this problem have a little more chance of finding the solution.
> >
> > As we already said, our bugzilla entry for this is not accessible from the
> > outside, but I know Red Hat does have a bugzilla entry for the same issue as
> > well. Maybe this is reachable from the outside (adding Don for this, as I know
> > he has worked on this problem as well).
> >
> RHEL bz's are not accessible from the outside.
> I suggest capturing the content of the RH bz issue and creating a k.o. bz
> with the information.
I've created https://bugzilla.kernel.org/show_bug.cgi?id=187781 to track this
on b.k.o. Feel free to add any information you have.
@Bjorn anything else I can provide in order to get the fix applied?
Byte,
Johannes
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2016-11-15 12:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 22:35 [PATCH 1/2] pci: export pcie_find_root_port Johannes Thumshirn
2016-11-02 22:35 ` [PATCH 2/2] pci: Don't set RCB bit in LNKCTL if the upstream bridge hasn't Johannes Thumshirn
2016-11-09 17:11 ` Bjorn Helgaas
2016-11-14 11:56 ` Johannes Thumshirn
2016-11-14 16:16 ` Don Dutile
2016-11-15 12:58 ` Johannes Thumshirn [this message]
2016-11-16 18:11 ` Bjorn Helgaas
2016-11-17 9:57 ` Johannes Thumshirn
2016-11-21 16:53 ` Bjorn Helgaas
2016-11-22 7:59 ` Johannes Thumshirn
2016-11-22 10:56 ` Johannes Thumshirn
2016-11-22 16:01 ` Myron Stowe
2016-11-23 17:31 ` Bjorn Helgaas
2016-11-23 19:49 ` Bjorn Helgaas
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=20161115125822.sna3oz56prmrelgc@linux-x5ow.site \
--to=jthumshirn@suse.de \
--cc=agraf@suse.de \
--cc=bhelgaas@google.com \
--cc=ddutile@redhat.com \
--cc=hare@suse.de \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®