From: Bjorn Helgaas <helgaas@kernel.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-nvme@lists.infradead.org
Subject: Re: 6.1.0-17: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff
Date: Mon, 21 Oct 2024 14:14:26 -0500 [thread overview]
Message-ID: <20241021191426.GA842491@bhelgaas> (raw)
In-Reply-To: <CAO9zADza=73GsuzAcuyH-YfhS34qjkDtuJjGBReVGpfE6KN_ow@mail.gmail.com>
On Fri, Jan 05, 2024 at 09:49:58AM -0500, Justin Piszcz wrote:
> Hello,
>
> Distribution: Debian Stable x86-64
> Kernel: 6.1.0-17
>
> Reporting this as requested from the kernel message, I have now
> appended the recommended kernel boot parameters
> nvme_core.default_ps_max_latency_us=0 pcie_aspm=off and will see if
> this recurs.
Hi Justin, did anything ever come of this report? Is it reproducible?
Did it seem to be related to suspend/resume?
> Jan 5 06:18:52 atom kernel: [295306.524933] pcieport 0000:00:06.0:
> AER: Corrected error received: 0000:00:06.0
> Jan 5 06:18:52 atom kernel: [295306.524979] pcieport 0000:00:06.0:
> PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
> Jan 5 06:18:52 atom kernel: [295306.525004] pcieport 0000:00:06.0:
> device [8086:a74d] error status/mask=00000001/00002000
> Jan 5 06:18:52 atom kernel: [295306.525027] pcieport 0000:00:06.0:
> [ 0] RxErr (First)
> Jan 5 06:19:22 atom kernel: [295336.554420] nvme nvme0: controller is
> down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff
> Jan 5 06:19:22 atom kernel: [295336.554469] nvme nvme0: Does your
> device have a faulty power saving mode enabled?
> Jan 5 06:19:22 atom kernel: [295336.554489] nvme nvme0: Try
> "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug
> Jan 5 06:19:22 atom kernel: [295336.614521] nvme 0000:03:00.0: Unable
> to change power state from D3cold to D0, device inaccessible
> Jan 5 06:19:22 atom kernel: [295336.614898] nvme nvme0: Removing
> after probe failure status: -19
> Jan 5 06:19:22 atom kernel: [295336.630497] nvme0n1: detected
> capacity change from 7814037168 to 0
> Jan 5 06:19:22 atom kernel: [295336.630502] BTRFS error (device
> nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 1, rd 0, flush 0, corrupt 0,
> gen 0
> Jan 5 06:19:22 atom kernel: [295336.630513] BTRFS error (device
> nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 2, rd 0, flush 0, corrupt 0,
> gen 0
> Jan 5 06:19:22 atom kernel: [295336.630542] BTRFS error (device
> nvme0n1p2): bdev /dev/nvme0n1p2 errs: wr 3, rd 0, flush 0, corrupt 0,
> gen 0
>
> Regards,
> Justin
next parent reply other threads:[~2024-10-21 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAO9zADza=73GsuzAcuyH-YfhS34qjkDtuJjGBReVGpfE6KN_ow@mail.gmail.com>
2024-10-21 19:14 ` Bjorn Helgaas [this message]
2024-10-21 19:32 ` 6.1.0-17: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff Justin Piszcz
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=20241021191426.GA842491@bhelgaas \
--to=helgaas@kernel.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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