![]() ![]() Ps 0 : mp:8.00W operational enlat:0 exlat:0 rrt:0 rrl:0 However, my nvme SSD is not from Samsung, but from Toshiba: I'm having the exact same problem (drive dying with filesystem read errors and system becoming unusable after using it for a while) 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 Here's the id-ctrl output in case it is still helpful: That quirk looks good! Running stable and also verified that `nvme get-feature -f 0x0c -H /dev/nvme0` reports Disabled. UpgradeStatus: Upgraded to zesty on (23 days ago)ĭmi.modalias: dmi:bvnDellInc. Linux- backports- modules- 4.10.0- 14-generic N/A ![]() Linux- restricted- modules- 4.10.0- 14-generic N/A InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) InstallationDate: Installed on (1665 days ago) Node SN Model Namespace Usage Format FW Rev Prior to manually disabling APST the drive would die and system would go down in flames with I/O errors within 20 to 40 minutes of boot. I am experiencing the same symptoms with the same model laptop except with a 512GB Samsung. That patch has a quirk for certain 256GB Samsung drives found in Dell laptops that do not behave well when APST is enabled. APST support just landed in the latest Zesty kernel (4.10.0-14.16) as part of https:/ /bugs.launchpad. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |