From: Keith Busch <keith.busch@linux.intel.com>
To: Aron Griffis <aron@arongriffis.com>
Cc: linux-pci@vger.kernel.org, linux-nvme@lists.infradead.org,
willy@infradead.org
Subject: Re: PCIe unsupported request with Intel 760p
Date: Mon, 2 Jul 2018 10:36:40 -0600 [thread overview]
Message-ID: <20180702163640.GB22877@localhost.localdomain> (raw)
In-Reply-To: <20180525232009.GV11037@localhost.localdomain>
Unfortunately the development team says they will not be able to provide
a fix for this errata. When using this device in a platform that reacts
this way to an LTR message (hopefully these are very few nowadays), the
recommendation is either disable ASPM or set the Unsupported Request bit
in the root port's AER Uncorrectable Error Mask register.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
WARNING: multiple messages have this Message-ID (diff)
From: keith.busch@linux.intel.com (Keith Busch)
Subject: PCIe unsupported request with Intel 760p
Date: Mon, 2 Jul 2018 10:36:40 -0600 [thread overview]
Message-ID: <20180702163640.GB22877@localhost.localdomain> (raw)
In-Reply-To: <20180525232009.GV11037@localhost.localdomain>
Unfortunately the development team says they will not be able to provide
a fix for this errata. When using this device in a platform that reacts
this way to an LTR message (hopefully these are very few nowadays), the
recommendation is either disable ASPM or set the Unsupported Request bit
in the root port's AER Uncorrectable Error Mask register.
next prev parent reply other threads:[~2018-07-02 16:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 18:25 PCIe unsupported request with Intel 760p Aron Griffis
2018-05-07 12:30 ` Aron Griffis
2018-05-07 12:30 ` Aron Griffis
2018-05-07 13:43 ` Matthew Wilcox
2018-05-07 13:43 ` Matthew Wilcox
2018-05-07 15:12 ` Keith Busch
2018-05-07 15:12 ` Keith Busch
2018-05-07 15:16 ` Matthew Wilcox
2018-05-07 15:16 ` Matthew Wilcox
2018-05-07 15:57 ` Aron Griffis
2018-05-07 15:57 ` Aron Griffis
2018-05-07 16:08 ` Keith Busch
2018-05-07 16:08 ` Keith Busch
2018-05-11 19:39 ` Bjorn Helgaas
2018-05-11 19:39 ` Bjorn Helgaas
2018-05-11 20:02 ` Keith Busch
2018-05-11 20:02 ` Keith Busch
2018-05-25 23:20 ` Keith Busch
2018-05-25 23:20 ` Keith Busch
2018-05-30 23:33 ` Bryan Gurney
2018-05-30 23:33 ` Bryan Gurney
2018-07-02 16:36 ` Keith Busch [this message]
2018-07-02 16:36 ` Keith Busch
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=20180702163640.GB22877@localhost.localdomain \
--to=keith.busch@linux.intel.com \
--cc=aron@arongriffis.com \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=willy@infradead.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 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.