From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-pci@vger.kernel.org, linux-nvme@lists.infradead.org,
Vidya Sagar <vidyas@nvidia.com>
Subject: Re: Are AER corrected errors worrying?
Date: Wed, 6 Jan 2021 23:40:00 +0100 [thread overview]
Message-ID: <20210106224000.skryo2aijhfiomfw@function> (raw)
In-Reply-To: <20210106214808.GA1280721@dhcp-10-100-145-180.wdc.com>
Keith Busch, le mer. 06 janv. 2021 13:48:08 -0800, a ecrit:
> On Wed, Jan 06, 2021 at 09:28:23PM +0100, Samuel Thibault wrote:
> > Is there more I can provide to investigate if that can somehow be fixed
> > in the driver? I guess I can safely use the system with pcie_aspm=off?
> > (the energy saving seems neglectible)
>
> I don't think there's more to do from the kernel or driver beyond
> disabling usage of the problematic feature. I think a proper fix would
> have to come from the hardware vendor.
Ok, thanks!
Samuel
_______________________________________________
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: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Keith Busch <kbusch@kernel.org>
Cc: Vidya Sagar <vidyas@nvidia.com>,
linux-nvme@lists.infradead.org, linux-pci@vger.kernel.org
Subject: Re: Are AER corrected errors worrying?
Date: Wed, 6 Jan 2021 23:40:00 +0100 [thread overview]
Message-ID: <20210106224000.skryo2aijhfiomfw@function> (raw)
In-Reply-To: <20210106214808.GA1280721@dhcp-10-100-145-180.wdc.com>
Keith Busch, le mer. 06 janv. 2021 13:48:08 -0800, a ecrit:
> On Wed, Jan 06, 2021 at 09:28:23PM +0100, Samuel Thibault wrote:
> > Is there more I can provide to investigate if that can somehow be fixed
> > in the driver? I guess I can safely use the system with pcie_aspm=off?
> > (the energy saving seems neglectible)
>
> I don't think there's more to do from the kernel or driver beyond
> disabling usage of the problematic feature. I think a proper fix would
> have to come from the hardware vendor.
Ok, thanks!
Samuel
next prev parent reply other threads:[~2021-01-06 22:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-01 22:40 Are AER corrected errors worrying? Samuel Thibault
2021-01-04 18:44 ` Keith Busch
2021-01-04 20:12 ` Samuel Thibault
2021-01-04 20:12 ` Samuel Thibault
2021-01-04 21:36 ` Samuel Thibault
2021-01-04 21:36 ` Samuel Thibault
2021-01-04 22:33 ` Samuel Thibault
2021-01-04 22:33 ` Samuel Thibault
2021-01-06 20:28 ` Samuel Thibault
2021-01-06 20:28 ` Samuel Thibault
2021-01-06 21:48 ` Keith Busch
2021-01-06 21:48 ` Keith Busch
2021-01-06 22:40 ` Samuel Thibault [this message]
2021-01-06 22:40 ` Samuel Thibault
-- strict thread matches above, loose matches on Subject: below --
2021-01-02 17:03 Samuel Thibault
2021-01-03 6:45 ` Vidya Sagar
2021-01-03 11:25 ` Samuel Thibault
2021-01-03 13:48 ` Samuel Thibault
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=20210106224000.skryo2aijhfiomfw@function \
--to=samuel.thibault@ens-lyon.org \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=vidyas@nvidia.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.