linux-kernel - RE: 6.1.0-17: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <009a01db23f0$053c4240$0fb4c6c0$@lucidpixels.com>
Date: Mon, 21 Oct 2024 15:32:52 -0400
From: "Justin Piszcz" <jpiszcz@...idpixels.com>
To: "'Bjorn Helgaas'" <helgaas@...nel.org>
Cc: "'LKML'" <linux-kernel@...r.kernel.org>,
	<linux-nvme@...ts.infradead.org>
Subject: RE: 6.1.0-17: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff

-----Original Message-----
From: Bjorn Helgaas <helgaas@...nel.org> 
Sent: Monday, October 21, 2024 3:14 PM
To: Justin Piszcz <jpiszcz@...idpixels.com>
Cc: LKML <linux-kernel@...r.kernel.org>; linux-nvme@...ts.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