- #STANDARD NVM EXPRESS CONTROLLER LATITUDE 7470 UPDATE#
- #STANDARD NVM EXPRESS CONTROLLER LATITUDE 7470 FULL#
- #STANDARD NVM EXPRESS CONTROLLER LATITUDE 7470 FREE#
Parm: admin_timeout:timeout in seconds for admin commands (byte) Vermagic: 4.10.0-19-generic SMP mod_unload lib/modules/4.10.0-19-generic/kernel/drivers/nvme/host/nvme-core.ko Here is the output with having run the nvme_core kernel parameter above: I don't know if this hasĪnything to do with the issue, but my system seems stable and it has not Using the nvme_core kernel parameter above. I reinstalled 17.04 and I've been running for 3 hours without incident
Ps 1 : mp:4.20W operational enlat:30 exlat:30 rrt:1 rrl:1 Ps 0 : mp:6.00W operational enlat:5 exlat:5 rrt:0 rrl:0 I downgraded to 16.10 and now have no more problems of this kind. The operating system would state that the disk is now read only and/or give IO errors. When I upgraded to ubuntu 17.04 beta 2 (which I believe is kernel 4.10), I started having crashes after anywhere from 10min to an hour. I'm running into what I think is the same or a related problem.
#STANDARD NVM EXPRESS CONTROLLER LATITUDE 7470 FREE#
If it does, feel free to delete one of the posts.
#STANDARD NVM EXPRESS CONTROLLER LATITUDE 7470 UPDATE#
I'll obviously need to update the blacklist to fix your laptop (in lieu of a better workaround that still lets you get some power savings), but I need the info above to figure out what the blacklist entry should look like.Īlso posted in bug 194921. There's some reason to believe that the problem is triggered by specific combinations of laptop and SSD. Samsung currently has a machine that appears to be affected and is trying to figure out what's going on. Can you try booting with nvme_fault_ps_max_latency_us=0? That with disable the power-saving feature that is likely at fault. What kind of computer is this? Is it a laptop? Is the affected disk something that came with the laptop?ģ.
#STANDARD NVM EXPRESS CONTROLLER LATITUDE 7470 FULL#
Even better would be the full output of 'nvme id-ctrl /dev/nvme0' - you can find the 'nvme' tool in the nvme-cli package.Ģ.
A new enough smartctl will show it in 'smartctl -i /dev/nvme0'. PCI: 04:00.0 Non-Volatile memory controller : Samsung Electronics Co Ltd NVMe SSD Controller SM951/PM951 (rev 01)Īs 4.11 enables APST for NVMe and there already is an exception for the Samsung SM951 NVMe SSD whose description seems to be related, I guess my SSD has the same bug.įor the moment I'm back to 4.9 kernel, but ready for testing if required.Ĭould you give me some more details of your hardware?ġ. blk_update_request: I/O error, dev nvme0n1, sector 916172848 blk_update_request: I/O error, dev nvme0n1, sector 916172864 blk_update_request: I/O error, dev nvme0n1, sector 916173120
blk_update_request: I/O error, dev nvme0n1, sector 916173360 nvme0n1: detected capacity change from 512110190592 to 0 nvme nvme0: Removing after probe failure status: -19 nvme 0000:04:00.0: controller is down will reset: CSTS=0xffffffff, PCI_STATUS=0xffff After updating to Kernel 4.11-rc3 (current Fedora 26 kernel), I noticed sudden disk outage after some time.
0 kommentar(er)
