From: Genes Lists <lists@sapience.com>
To: linux-kernel@vger.kernel.org
Cc: kbusch@kernel.org, axboe@kernel.dk, sagi@grimberg.me,
linux-nvme@lists.infradead.org, hch@lst.de
Subject: Possible nvme regression in 6.4.11
Date: Wed, 16 Aug 2023 16:39:34 -0400 [thread overview]
Message-ID: <5f968b95-6b1c-4d6f-aac7-5d54f66834a8@sapience.com> (raw)
Also reported to bugzilla [1]
Failure happens on 1 laptop with samsung ssd.
Boot log manually transcribed:
kernel: nvme nvme0: controller is down; will reset: CSTS:0xffffffff,
PCI_STATUS=0xffff
kernel: nvme nvme0: Does your device have a faulty power saving mode
enabled?
kernel: nvme nvme0: try "nvme_core.default_ps_max_latency_us=0
pcie_aspm=off" and report a bug
kernel: nvme 0000:04:00.0: Unable to change power state from D3cold to
D0, device inaccessible
kernel: nvme nvme0: Disabling device after reset failure: -19
mount[353]: mount /sysroot: can't read suprtblock on /dev/nvme0n1p5.
mount[353]: dmesg(1) may have more information after failed moutn
system call.
kernel: nvme0m1: detected capacity change from 2000409264 to 0
kernel: EXT4-fs (nvme0n1p5): unable to read superblock
systemd([1]: sysroot.mount: Mount process exited, code=exited, status=32/n/a
...
All kernels are upstream, untainted and compiled on Arch using:
gcc version 13.2.1
Kernels Tested:
- 6.4.10 - works fine
- 6.4.11 - fails
- 6.5-rc6 - fails
- 6.4.11 + nvme_core.default_ps_max_latency_us=0 pcie_aspm=off - fails
- 6.4.11 with 1 revert below - fails
Revert "nvme-pci: add NVME_QUIRK_BOGUS_NID for Samsung PM9B1 256G
and 512G"
This reverts commit 061fbf64825fb47367bbb6e0a528611f08119473.
Hardware:
model name : Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
stepping : 9
microcode : 0xf4
nvme:
04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe
SSD Controller SM961/PM961/SM963
Subsystem: Samsung Electronics Co Ltd SM963 2.5" NVMe PCIe SSD
Flags: bus master, fast devsel, latency 0, IRQ 16, NUMA node 0
Memory at edb00000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/32 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [b0] MSI-X: Enable+ Count=33 Masked-
Kernel driver in use: nvme
Gene
[1] https://bugzilla.kernel.org/show_bug.cgi?id=217802
next reply other threads:[~2023-08-16 20:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 20:39 Genes Lists [this message]
2023-08-16 21:04 ` Keith Busch
2023-08-17 1:30 ` Genes Lists
2023-08-17 9:16 ` Genes Lists
2023-08-17 17:28 ` Keith Busch
2023-08-17 17:43 ` Genes Lists
2023-08-23 17:41 ` Keith Busch
2023-08-23 20:25 ` Genes Lists
2023-08-24 2:44 ` Ricky WU
2023-08-24 9:48 ` Genes Lists
2023-08-24 10:22 ` Genes Lists
2023-08-25 12:51 ` Ricky WU
2023-08-30 21:09 ` Genes Lists
2023-09-11 8:02 ` Linux regression tracking (Thorsten Leemhuis)
2023-09-11 11:38 ` Thorsten Leemhuis
2023-09-18 17:07 ` [Revert] " Jade Lovelace
2023-09-18 17:07 ` [PATCH] Revert "misc: rtsx: judge ASPM Mode to set PETXCFG Reg" Jade Lovelace
2023-09-11 15:41 ` Possible nvme regression in 6.4.11 Augusto Zanellato
2023-08-24 11:29 ` Genes Lists
2023-08-17 3:00 ` Bagas Sanjaya
2023-09-29 11:49 ` Linux regression tracking #update (Thorsten Leemhuis)
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=5f968b95-6b1c-4d6f-aac7-5d54f66834a8@sapience.com \
--to=lists@sapience.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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
all inboxes | Powered by JetHome®