NVME drive is not brought up after suspend

[Belgarath]

I have replaced the NVME drive from Kingston 1TB NVME (which worked after suspending fine but failed) to Crucial CT2000P5PSSD8 (P7CR403), which stays dead after waking up from suspending.

The drive stays in power-off mode even after reset and is not visible in BIOS until full power cycle (the motherboard can stay powered on so the power-cycle can be done with the front button rather than switch at power supply)

There is nothing in dmesg that would suggest there is an issue other than at the wakeup there is information that the nvme0 drive cannot perform reset.

I can't attach logs as my system is dead at that point.

I tested it on both 22.04 and 23.04 (I upgraded hoping that 6.2 kernel my resolve the issue)
---
ProblemType: Bug
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CasperVersion: 1.480
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 23.04
LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
RelatedPackageVersions:
 linux-restricted-modules-6.2.0-20-generic N/A
 linux-backports-modules-6.2.0-20-generic N/A
 linux-firmware 20230323.gitbcdcfbcf-0ubuntu1
Tags: lunar
Uname: Linux 6.2.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 02/09/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F51h
dmi.board.asset.tag: Default string
dmi.board.name: AB350-Gaming-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF51h:bd02/09/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350-Gaming
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/2031835/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Belgarath (belgarath)]

For some reason linux-image-6.2.0-27-generic is not on package list

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 2031835

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Belgarath (belgarath)]

apport information

[Belgarath (belgarath)]

apport information

[Belgarath (belgarath)]

apport information

[Belgarath (belgarath)]

apport information

[Belgarath (belgarath)]

apport information

[Belgarath (belgarath)]

apport information

[Belgarath (belgarath)]

apport information

[Belgarath (belgarath)]

apport information

[Belgarath (belgarath)]

apport information

[Belgarath (belgarath)]

apport information

[Belgarath (belgarath)]

apport information

[Belgarath (belgarath)]

apport information

[Belgarath (belgarath)]

apport information

[Belgarath (belgarath)]

apport information

[Belgarath (belgarath)]

apport information

[Belgarath (belgarath)]

apport information

[Belgarath (belgarath)]

apport information

[Belgarath (belgarath)]

report form 23.04 (live USB version) added

[Paul White (paulw2u)]

Changing status to 'Confirmed' on behalf of the reporter (requested by Kernel Bot in comment #5)

[Belgarath (belgarath)]

I replaced the Crucial drive with KINGSTON SKC3000D2048G and the problem has disappeared, crucial CT2000P5PSSD8 still has the same issue.