Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1599042 - Hang during boot: nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff
Hang during boot: nvme0: controller is down; will reset: CSTS=0xffffffff, PCI...
Status: NEW
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
28
x86_64 Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Matthias Clasen
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-07-08 04:02 EDT by Jan Vlug
Modified: 2018-10-15 12:52 EDT (History)
18 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Vlug 2018-07-08 04:02:31 EDT
I have a brand new laptop on which I want to install Fedora from the live image (Windows 10 was pre-installed, but can be removed completely).

The boot process from the USB live image continues until these start jobs are running:

A start job is running for Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling
A start job is running for udev Wait for complete device initialization

Then this message appears:
nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff
And then the system hangs.


Information from the BIOS of my system:
The BIOS states that the model of the sytem is: N140WU.
BIOS version: 1.05.02
KBC/EL firmware version: 1.05.02
ME FW version: 11.8.50.3434
Version 2.18.1263 American Megatrends
Comment 1 Jan Vlug 2018-07-08 05:23:19 EDT
I made a change in the BIOS in the Advanced screen to the SATA mode setting:

Originally SATA mode was set to: AHCI Mode
I selected for SATA mode: Intel RST Premium With Intel Optane System Acceleration

Now the Live Fedora image boots fully.

However, I do not see the SSD disk when Fedora is booted. Nor in the installer, the gparted, blivet-gui or disks. Only the USB pen with the live image is being reported. So I still cannot install Fedora to my system.
Comment 2 Jan Vlug 2018-07-09 17:57:00 EDT
Details about the SSD:
The disks is a Western Digital: WDS500G2X0C:
https://products.wdc.com/library/Spe...178-800181.pdf
https://products.wdc.com/library/Spe...879-810008.pdf
The bios states: PCIe 1.0, WDS500G2X0C-00L350
This link suggests that the SSD is supported under Linux:
https://www.anandtech.com/show/12543...and-ssd-review

I also found another report describing the issue that I have with exactly the same Western Digital SSD model:
https://community.wd.com/t/linux-sup...me-2018/225446
Comment 3 Jan Vlug 2018-07-09 17:59:43 EDT
Oops,now with working links:

Details about the SSD:
The disks is a Western Digital: WDS500G2X0C:
[url]https://products.wdc.com/library/SpecSheet/ENG/2178-800181.pdf[/url]
[url]https://products.wdc.com/library/SpecSheet/ENG/2879-810008.pdf[/url]
The bios states: PCIe 1.0, WDS500G2X0C-00L350
This link suggests that the SSD is supported under Linux:
[url]https://www.anandtech.com/show/12543/the-western-digital-wd-black-3d-nand-ssd-review[/url]

I also found another report describing the issue that I have with exactly the same Western Digital SSD model:
https://community.wd.com/t/linux-support-for-wd-black-nvme-2018/225446
Comment 4 Jan Vlug 2018-07-09 18:05:14 EDT
Discard comment 2 and 3, now hopefully without errors:

Details about the SSD:
The disks is a Western Digital: WDS500G2X0C:
https://products.wdc.com/library/SpecSheet/ENG/2178-800181.pdf
https://products.wdc.com/library/SpecSheet/ENG/2879-810008.pdf
The bios states: PCIe 1.0, WDS500G2X0C-00L350
This link suggests that the SSD is supported under Linux:
https://www.anandtech.com/show/12543/the-western-digital-wd-black-3d-nand-ssd-review

I also found another report describing the issue that I have with exactly the same Western Digital SSD model:
https://community.wd.com/t/linux-support-for-wd-black-nvme-2018/225446
Comment 6 Jan Vlug 2018-07-11 16:06:16 EDT
I replaced the WD Black SSD with a:
500GB Samsung 970 EVO NVME PCI-e 3.0 x4, M.2
This SSD is recognized correctly and Fedora 28 is running fine on it now.

I leave this bug open, because I'm not sure whether the issue was related to Fedora Linux or the SSD.
Comment 7 Jan Vlug 2018-08-16 07:30:41 EDT
See this link for a solution (I did not test it, because I do not have the disk any more):
https://community.wd.com/t/linux-support-for-wd-black-nvme-2018/225446/9?u=chrisyuan
Comment 8 Laura Abbott 2018-10-01 17:16:49 EDT
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs.
 
Fedora 28 has now been rebased to 4.18.10-300.fc28.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29.
 
If you experience different issues, please open a new bug report for those.
Comment 9 Richard Shaw 2018-10-09 12:30:18 EDT
Per this link[1] the fix is to:

In the GRUB boot menu, press e to edit startup parameter
Add nvme_core.default_ps_max_latency_us=5500 by the end of quiet splash
Ctrl-x to boot up, the installer should detect this disk in partition step.

After finishing finish installation, press shift while power on to enter GRUB again, add same kernel parameter nvme_core.default_ps_max_latency_us=5500, Ctrl-x to boot up.

You will see Ubuntu boot up successfully, edit /etc/default/grub, add parameter nvme_core.default_ps_max_latency_us=5500 again, execute sudo update-grub. so that every time boot up will contain this parameter in the grub automatically, no more manually edit.

[1] https://community.wd.com/t/linux-support-for-wd-black-nvme-2018/225446/9?u=chrisyuan
Comment 10 Jan Vlug 2018-10-15 12:52:44 EDT
The information at the link of the previous comment suggests that this issue has not been solved.

Note You need to log in before you can comment on or make changes to this bug.