Comment 3 for bug 1694596

My NVMe drive failed again yesterday. I no longer think the errors are due to the APST support. I'm starting to think it's either something in the Linux kernel 4.8.0-53 upgrade or simply a problem with the drive hardware or firmware.

The time-line of the errors is shown below. Note that I never defined the "default_ps_max_latency_us" parameter to 6000. I only set it to a value of zero.

Parameter "nvme_core.default_ps_max_latency_us" is not defined:

2017-04-04 Upgraded to 4.8.0-46.49
2017-04-24 Upgraded to 4.8.0-49.52 ← Adds NVMe APST support (LP: #1664602)
2017-05-01 Upgraded to 4.8.0-51.54
2017-05-16 Upgraded to 4.8.0-52.55
2017-05-25 Upgraded to 4.8.0-53.56 ← Errors on NVMe drive

Parameter "nvme_core.default_ps_max_latency_us" is set to zero:

2017-05-29 Linux 4.8.0-53.56 (APST disabled) ← Running OK
2017-05-30 Linux 4.8.0-53.56 (APST disabled) ← Running OK
2017-05-31 Linux 4.8.0-53.56 (APST disabled) ← Errors on NVMe drive

At this point, I switched from the Hardware Enablement (HWE) stack back to the original General Availability (GA) stack for the Linux kernel and X server on Ubuntu 16.04.

2017-05-31 Linux 4.4.0-78.90 (GA) ← Running OK so far
2017-06-01 Linux 4.4.0-78.90 (GA) ← Running OK so far

I hope this change will help determine whether the errors are due to the drive itself or something in the Linux 4.8 upgrade. I guess we should close this bug report, or at least rename it.

Thank you,
John