Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Wim ten Have <wim.ten.have@oracle.com>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Wim ten Have <wim.ten.have@oracle.com>
Subject: Re: Red Hat (Fedora) bug report 1467674 concerning your kernel functional performance enhancements causing PCI Express crashes,
Date: Tue, 4 Jul 2017 19:59:16 +0200	[thread overview]
Message-ID: <20170704195916.43fbe6e4.wim.ten.have@oracle.com> (raw)
In-Reply-To: <2acc9a73-0c2c-31f3-fcdf-42289213860e@codeaurora.org>

On Tue, 4 Jul 2017 11:57:37 -0400
Sinan Kaya <okaya@codeaurora.org> wrote:

> Hi,
> 
> On 7/4/2017 11:32 AM, Bjorn Helgaas wrote:
> > [+cc linux-pci]
> > 
> > Thanks very much for the detailed problem report, Wim!  I'm taking the
> > liberty to forward to the linux-pci list in case others trip over the
> > same thing.
> >   
> 
> So, the spec is lying :) and reality doesn't match theory.
> 
> "Per the ECN mentioned below, all PCIe Receivers are expected to support
>  Extended Tags"
> 
> > The problem is not specific to this piece of h/w.  I did pin-point the
> > issue to specific kernel code commit  
> <snip>
> 
> > 60db3a4d8cc9073cf56264785197ba75ee1caca4
> >   * <wtenhave@hagen:55> git bisect good
> >     60db3a4d8cc9073cf56264785197ba75ee1caca4 is the first bad commit
> >     commit 60db3a4d8cc9073cf56264785197ba75ee1caca4
> >     Author: Sinan Kaya <okaya@codeaurora.org>
> >     Date:   Fri Jan 20 09:16:51 2017 -0500
> > 
> >       PCI: Enable PCIe Extended Tags if supported
> >   
> <snip>
> 
> > 3. Boot and see it crash as soon it starts to operate on specific PCI
> > Express Ethernet controller.
> >   
> 
> I guess we have an endpoint/system with errata that needs to be blacklisted.
> Can you please try another endpoint with the same system?
> 
> You have conflicting information above. I want to understand whether it
> is the endpoint or the system that needs to be blacklisted.

  Specific PCI Express ethernet are embedded on the systems mainboard.
  There's only one PCI Express that requires a riser card.  It is empty.

> Please also provide sudo lspci -vvv output from the system with the patch.
> Sinan

  Detail (lspci -vvv) is added to RedHat filed bugzilla entry; BugID 1467674
  since the info is rather large.

	https://bugzilla.redhat.com/show_bug.cgi?id=1467674

Enjoy,
- Wim.

  reply	other threads:[~2017-07-04 17:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170704161352.1cdb2670.wim.ten.have@oracle.com>
2017-07-04 15:32 ` Fwd: Red Hat (Fedora) bug report 1467674 concerning your kernel functional performance enhancements causing PCI Express crashes, Bjorn Helgaas
2017-07-04 15:57   ` Sinan Kaya
2017-07-04 17:59     ` Wim ten Have [this message]
2017-07-04 22:25       ` Sinan Kaya
2017-07-05  1:00         ` Sinan Kaya
2017-07-05  7:42           ` Ethan Zhao
2017-07-05 12:28             ` Sinan Kaya
2017-07-05 11:13           ` Wim ten Have
2017-07-05 12:37             ` Sinan Kaya
2017-07-05 13:00               ` Wim ten Have
2017-07-05 13:20                 ` Sinan Kaya

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=20170704195916.43fbe6e4.wim.ten.have@oracle.com \
    --to=wim.ten.have@oracle.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=okaya@codeaurora.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