From: Sinan Kaya <okaya@codeaurora.org>
To: Ethan Zhao <ethan.kernel@gmail.com>
Cc: Wim ten Have <wim.ten.have@oracle.com>,
Bjorn Helgaas <bhelgaas@google.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: Red Hat (Fedora) bug report 1467674 concerning your kernel functional performance enhancements causing PCI Express crashes,
Date: Wed, 5 Jul 2017 08:28:55 -0400 [thread overview]
Message-ID: <47e18e59-5417-33d6-e150-25b2c714e391@codeaurora.org> (raw)
In-Reply-To: <CABawtvOOWV1aKk=1LBk+S0UfG02UTNMvtdJM58HQYW4JXFAyrQ@mail.gmail.com>
Hi,
On 7/5/2017 3:42 AM, Ethan Zhao wrote:
> Sinan,
>
> About the patch attached, why clear the word of
> PCI_EXP_DEVCTL_EXT_TAG ? does the device will be set by default after
> POST it is not supported ?
>
> dev_info(&dev->dev, "clearing extended tags capability\n");
>
> + pcie_capability_clear_word(dev, PCI_EXP_DEVCTL,
> + PCI_EXP_DEVCTL_EXT_TAG);
We don't usually trust the FW in Linux. Some outdated firmware might have
done the same mistake and end users usually don't upgrade their BIOS in
general. We end up working around issues in Linux with quirks etc.
The other issue is this. Default value of the register is not zero.
"Extended Tag Field Enable:
Default value of this bit is implementation specific"
https://pcisig.com/sites/default/files/specification_documents/ECN_Extended_Tag_Enable_Default_05Sept2008_final.pdf
Hope this helps,
Sinan
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-07-05 12:29 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
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 [this message]
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=47e18e59-5417-33d6-e150-25b2c714e391@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=bhelgaas@google.com \
--cc=ethan.kernel@gmail.com \
--cc=linux-pci@vger.kernel.org \
--cc=wim.ten.have@oracle.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.