[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

2017-04-11 Thread Andy Clayton
Sure thing. I have been running with "nvme_core.default_ps_max_latency_us=250" and repo kernel for about 24 hours now without issue. Confirmed with nvme that APST is enabled. I will switch to "nvme_core.default_ps_max_latency_us=3000" later today or tomorrow. $ sudo nvme get-feature -f 0x0c -H /de

[Kernel-packages] [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

2017-04-05 Thread Andy Clayton
That quirk looks good! Running stable and also verified that `nvme get- feature -f 0x0c -H /dev/nvme0` reports Disabled. Thanks for the quick responses! Here's the id-ctrl output in case it is still helpful: $ sudo nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x144d ssvid : 0x14

[Kernel-packages] [Bug 1678184] [NEW] APST quirk needed for Samsung 512GB NVMe drive

2017-03-31 Thread Andy Clayton
Public bug reported: APST support just landed in the latest Zesty kernel (4.10.0-14.16) as part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602. That patch has a quirk for certain 256GB Samsung drives found in Dell laptops that do not behave well when APST is enabled. I am experien