Bug 1599042
| Summary: | Hang during boot: nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jan Vlug <jan.public> |
| Component: | kernel | Assignee: | Matthias Clasen <mclasen> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 28 | CC: | airlied, bskeggs, ewk, hdegoede, hobbes1069, hx, ichavero, itamar, jan.public, jarodwilson, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, steved, velosol |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-02-21 21:11:38 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jan Vlug
2018-07-08 08:02:31 UTC
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. 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 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 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 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. 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 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. 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 The information at the link of the previous comment suggests that this issue has not been solved. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are 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.20.5-100.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. *********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. Same here. I already killed 3 Fedora installs and still it dies like this after 3rd reboot... |