From: keith.busch@intel.com (Keith Busch)
Subject: Linux AER reporting
Date: Mon, 22 Aug 2016 12:15:40 -0400 [thread overview]
Message-ID: <20160822161540.GD28276@localhost.localdomain> (raw)
In-Reply-To: <CAG3=cOncMTcyALa=-i1jeA-z4pe22D9CrJ=Rxr2E8HWBsEMOPg@mail.gmail.com>
Hi Nisha,
The Linux NVMe driver didn't add AER support until commit:
| commit a0a3408ee614848c27b0d36c2fe490da3b387b8d
| Author: Keith Busch <keith.busch at intel.com>
| Date: Mon Dec 7 15:30:31 2015 -0700
|
| NVMe: Add pci error handlers
If you don't have the commit, AER's may cause problems for NVMe.
I think 4.4 was the first kernel release to include it.
On Mon, Aug 22, 2016@08:52:10AM -0700, Nisha Miller wrote:
> Hi all,
>
> We have a PCIE SSD controller using NVME. This controller works on
> Windows and Linux. However, we are seeing a problem under Linux.
>
> In the nvme Linux driver in function nvme_kthread() the CSTS register
> is read once a second to check for controller status failure. In our
> case we see that occasionally this register is read as 0xFFFFFFFF.
> Whenever this happens, the kernel just hangs. This seems to be PCIe
> read error and we are trying to gather further information. How does
> one use Linux AER with the nvme driver?
>
> We are using Centos 7.2 with Kernel 3.19.8. PCIe AER has been enabled
> in the kernel and aerdriver.forceload=y is set in the command line.
>
> TIA
> Nisha Miller
next prev parent reply other threads:[~2016-08-22 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 15:52 Linux AER reporting Nisha Miller
2016-08-22 16:15 ` Keith Busch [this message]
2016-08-22 18:10 ` Guilherme G. Piccoli
2016-08-23 23:56 ` Nisha Miller
2016-08-24 14:02 ` Guilherme G. Piccoli
2016-08-24 14:40 ` Keith Busch
2016-08-24 17:13 ` Nisha Miller
2016-08-25 15:06 ` Keith Busch
2016-08-25 17:37 ` Nisha Miller
2016-08-25 17:49 ` Keith Busch
2016-08-25 18:08 ` Nisha Miller
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=20160822161540.GD28276@localhost.localdomain \
--to=keith.busch@intel.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