LKML Archive on
help / color / mirror / Atom feed
From: Keith Busch <>
To: Bjorn Helgaas <>
Cc: Jesse Vincent <>, Sagi Grimberg <>,, Andrew Lutomirski <>,,,
	Jens Axboe <>, Bjorn Helgaas <>,
	Christoph Hellwig <>
Subject: Re: Another NVMe failure, this time with AER info
Date: Fri, 11 May 2018 11:42:42 -0600	[thread overview]
Message-ID: <20180511174241.GC7344@localhost.localdomain> (raw)
In-Reply-To: <20180511172610.GB7344@localhost.localdomain>

On Fri, May 11, 2018 at 11:26:11AM -0600, Keith Busch wrote:
> I trust you know the offsets here, but it's hard to tell what this
> is doing with hard-coded addresses. Just to be safe and for clarity,
> I recommend the 'CAP_*+<offset>' with a mask.
> For example, disabling ASPM L1.2 can look like:
>  # setpci -s <B:D.f> CAP_PM+8.l=0:4

My mistake above: CAP_PM is a different capability, not the intended
one. It looks like setpci doesn't even have a convenient symbol for the
L1 PM extended capability, so the hard-coded offsets are the only way
for this setting. Sorry about the mistake.

  reply	other threads:[~2018-05-11 17:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2018-05-11 16:57 ` Bjorn Helgaas
2018-05-11 17:26   ` Keith Busch
2018-05-11 17:42     ` Keith Busch [this message]
2018-05-11 17:55       ` Bjorn Helgaas
2018-05-12  2:38   ` Ming Lei

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180511174241.GC7344@localhost.localdomain \ \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: Another NVMe failure, this time with AER info' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).