From: keith.busch@intel.com (Keith Busch)
Subject: Linux AER reporting
Date: Wed, 24 Aug 2016 10:40:30 -0400 [thread overview]
Message-ID: <20160824144029.GA13258@localhost.localdomain> (raw)
In-Reply-To: <57BDA906.4050207@linux.vnet.ibm.com>
On Wed, Aug 24, 2016@11:02:46AM -0300, Guilherme G. Piccoli wrote:
> On 08/23/2016 08:56 PM, Nisha Miller wrote:
> >Hi Keith and Guilherme,
> >
> >thank you for your replies.
> >
> >Kernel 4.4.19 does not seem to have nvme driver with support for AER.
> >It is present in Kernel 4.7 but getting it to work on Centos 7.2 is
> >turning out to be quite a task. Arch Linux has kernel 4.7 so I will
> >give that a shot.
> >
> >I should have mentioned that we get the CSTS = 0xFFFFFFFF only after
> >millions of writes. When using fio, it runs for over 30 minutes before
> >the problem crops up.
>
> Hi Nisha, unfortunately the idea of the quirk I mentioned seems useless
> here, since you're getting the error after multiple writes. Hope Keith can
> provide more ideas for you!
An all 1's completion indicates the link is down. There should never be
a case where a functioning drive actually returns that from a read to
the CSTS register.
I'm not sure if PCIe AER has anything do with this, though. Are you
injecting these sorts of errors? If you're just doing normal IO testing,
AER may not apply here.
next prev parent reply other threads:[~2016-08-24 14:40 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
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 [this message]
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=20160824144029.GA13258@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 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.