mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sinan Kaya <okaya@kernel.org>
To: Bjorn Helgaas <helgaas@kernel.org>, linux-pci@vger.kernel.org
Cc: Robert Smith <robert.smith51@protonmail.com>,
	Bart Van Assche <bvanassche@acm.org>,
	linux-kernel@vger.kernel.org
Subject: Re: PCI extended tags regression: 3ware 9650SE-2LP RAID controller not working on AMD Ryzen system
Date: Fri, 1 Feb 2019 17:26:08 -0500	[thread overview]
Message-ID: <403fdf3f-9777-1f14-f02a-30c3897e948d@kernel.org> (raw)
In-Reply-To: <20190201215249.GT229773@google.com>



On 2/1/2019 4:52 PM, Bjorn Helgaas wrote:
> See https://bugzilla.kernel.org/show_bug.cgi?id=202425.
> 
> Robert bisected a problem with a 3ware 9650SE-2LP controller to
> 60db3a4d8cc9 ("PCI: Enable PCIe Extended Tags if supported") and
> verified that reverting it solves the problem.
> 
> We have found issues in the past where Root Ports don't handle
> extended tags correctly and have added quirks to avoid use of them:
> 
>    1b30dfd376e2 ("PCI: Mark Broadcom HT1100 and HT2000 Root Port Extended Tags as broken")
>    62ce94a7a5a5 ("PCI: Mark Broadcom HT2100 Root Port Extended Tags as broken")
> 
> I don't know yet what Root Ports Robert has, but maybe we need a
> similar quirk?
> 
> I'm pretty sure Root Ports that don't handle extended tags are out of
> spec, so it would be ideal if we could get the manufacturer to provide
> an erratum as documentation.
> 

I agree. The issue needs to be directed to AMD. PCI spec says it is
safe to enable this option. I also have not heart of a single complaint
from Intel systems.


> Bjorn
> 

      reply	other threads:[~2019-02-01 22:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-01 21:52 Bjorn Helgaas
2019-02-01 22:26 ` Sinan Kaya [this message]

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=403fdf3f-9777-1f14-f02a-30c3897e948d@kernel.org \
    --to=okaya@kernel.org \
    --cc=bvanassche@acm.org \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=robert.smith51@protonmail.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 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®