From: "Justin Piszcz" <jpiszcz@lucidpixels.com>
To: "'Bjorn Helgaas'" <helgaas@kernel.org>
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 15:32:52 -0400 [thread overview]
Message-ID: <009a01db23f0$053c4240$0fb4c6c0$@lucidpixels.com> (raw)
In-Reply-To: <20241021191426.GA842491@bhelgaas>
-----Original Message-----
From: Bjorn Helgaas <helgaas@kernel.org>
Sent: Monday, October 21, 2024 3:14 PM
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
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?
[ ..]
>
> Regards,
> Justin
Yes-- this turned out to be the result of the Intel i9 13900k/14900k known
CPU failure/bug issue. After working with Intel to replace the failing
i9-14900k with a replacement unit, everything has been rock solid without
any issues yet, running the new 0x12b microcode as of 10/21/2024. This is
the first time I have seen stack smashing/NVME errors due to a CPU failing
but that is what it was, I have not seen a single instance of this error
after replacing the CPU.
Three is a more detailed account of the issue that I posted here:
https://forum.level1techs.com/t/debian-linux-stable-on-pro-ws-w680-ace-ipmi-
application-segfaults-kernel-panic/212854/8
Regards,
Justin
prev parent reply other threads:[~2024-10-21 19:33 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 ` 6.1.0-17: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff Bjorn Helgaas
2024-10-21 19:32 ` Justin Piszcz [this message]
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='009a01db23f0$053c4240$0fb4c6c0$@lucidpixels.com' \
--to=jpiszcz@lucidpixels.com \
--cc=helgaas@kernel.org \
--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