From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Keith Busch <kbusch@kernel.org>, Vidya Sagar <vidyas@nvidia.com>
Cc: linux-pci@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: Are AER corrected errors worrying?
Date: Mon, 4 Jan 2021 21:12:47 +0100 [thread overview]
Message-ID: <20210104201247.5k47gueib3cw4sfr@function> (raw)
In-Reply-To: <20210104184435.GE1024941@dhcp-10-100-145-180.wdc.com>
Hello,
Vidya Sagar wrote:
> Since this is a laptop, I'm suspecting that ASPM states might have
> been enabled which could be causing these errors.
Keith Busch, le lun. 04 janv. 2021 10:44:35 -0800, a ecrit:
> Sometimes these types of errors occur from low power settings, so you
> can try disabling the automatic management of these (assuming the
> hardware supports it). To disable nvme specific power state transitions,
> the kernel parameter is "nvme_core.default_ps_max_latency_us=0".
I have tried to add it, and this one line changed in lspci -vv:
02:00.0 Non-Volatile memory controller: Sandisk Corp WD Black SN750 / PC SN730 NVMe SSD (prog-if 02 [NVM Express])
[...]
Capabilities: [c0] Express (v2) Endpoint, MSI 00
[...]
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend-
turned to
DevSta: CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr- TransPend-
that last value happens to be what I was seeing for that line with the
manufacturer-provided ubuntu linux kernel.
So far (30m uptime) no corrected error report, I'll watch in the coming
hours/days to see if that avoided the issue. I wasn't able to trigger
such corrected errors by loading the machine, so possibly that's indeed
the converse that I should have been trying: letting it go low power :)
> PCI also has automatic link power savings that you can disable with
> parameter "pcie_aspm=off".
I'll try that if I still see errors with the nvme_core parameter.
Samuel
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-01-04 20:15 UTC|newest]
Thread overview: 8+ 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 [this message]
2021-01-04 21:36 ` Samuel Thibault
2021-01-04 22:33 ` Samuel Thibault
2021-01-06 20:28 ` Samuel Thibault
2021-01-06 21:48 ` Keith Busch
2021-01-06 22:40 ` 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=20210104201247.5k47gueib3cw4sfr@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox