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

[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 experiencing
the same symptoms with the same model laptop except with a 512GB
Samsung. 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.

$ sudo nvme list
Node SN Model Namespace Usage Format FW Rev
---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1 ************** PM951 NVMe SAMSUNG 512GB 1 500.20 GB / 512.11 GB 512 B + 0 B BXV76D0Q

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-14-generic 4.10.0-14.16
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: ajclayton 3305 F.... pulseaudio
CurrentDesktop: Unity:Unity7
Date: Fri Mar 31 09:42:38 2017
InstallationDate: Installed on 2012-09-08 (1665 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: Dell Inc. XPS 15 9550
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt nouveau.modeset=0 log_buf_len=20M
RelatedPackageVersions:
linux-restricted-modules-4.10.0-14-generic N/A
linux-backports-modules-4.10.0-14-generic N/A
linux-firmware 1.164
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed


** Tags: amd64 apport-bug zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Brad Figg]

This change was made by a bot.

** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Seth Forshee]

** Changed in: linux (Ubuntu)
Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress

** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Seth Forshee (sforshee)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

@Andy,

Can you install `nvme-cli` and attach the output of `nvme id-ctrl
/dev/nvme0`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Seth Forshee]

Please test this kernel and let me know whether it fixes your problem.
Thanks!

http://people.canonical.com/~sforshee/lp1678184/linux-4.10.0-16.18+lp1678184v201704030935/

** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[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 : 0x144d
sn : **************
mn : PM951 NVMe SAMSUNG 512GB
fr : BXV76D0Q
rab : 2
ieee : 002538
cmic : 0
mdts : 5
cntlid : 1
ver : 0
rtd3r : 0
rtd3e : 0
oaes : 0
oacs : 0x17
acl : 7
aerl : 3
frmw : 0x6
lpa : 0
elpe : 63
npss : 4
avscc : 0x1
apsta : 0x1
wctemp : 0
cctemp : 0
mtfa : 0
hmpre : 0
hmmin : 0
tnvmcap : 0
unvmcap : 0
rpmbs : 0
sqes : 0x66
cqes : 0x44
nn : 1
oncs : 0x1f
fuses : 0
fna : 0
vwc : 0x1
awun : 255
awupf : 0
nvscc : 1
acwu : 0
sgls : 0
subnqn :
ps 0 : mp:6.00W operational enlat:5 exlat:5 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
ps 1 : mp:4.20W operational enlat:30 exlat:30 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
ps 2 : mp:3.10W operational enlat:100 exlat:100 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
ps 3 : mp:0.0700W non-operational enlat:500 exlat:5000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
ps 4 : mp:0.0050W non-operational enlat:2000 exlat:22000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

BTW you should use the kernel from repo instead of kernel from comment
#4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

@Andy,

Are you willing to help me testing if ps2/ps3 works?
My guess is that ps2 (most powersaving operational state) works but not ps3/ps4.

So I need your help to try kernel parameter
"nvme_core.default_ps_max_latency_us=250", and
"nvme_core.default_ps_max_latency_us=3000".

Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[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 /dev/nvme0
get-feature:0xc (Autonomous Power State Transition), Current value:0x000001
Autonomous Power State Transition Enable (APSTE): Enabled

$ uname -a
Linux TEC-AJC2-U 4.10.0-19-generic #21-Ubuntu SMP Thu Apr 6 17:04:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[André Düwel]

Hi, I have set "nvme_core.default_ps_max_latency_us=3000" now for over a
day now and its working, too. No issues until now.

@Kai-Heng Feng: do you need any other testing?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

Yes, can you try 6000 again? 3000 doesn't make it enters to PS3. My bad.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Nils]

I'm having the exact same problem (drive dying with filesystem read
errors and system becoming unusable after using it for a while)

However, my nvme SSD is not from Samsung, but from Toshiba:

nvme list
Node SN Model Namespace Usage Format FW Rev
---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1 177S10WYTAMT THNSF5256GPUK TOSHIBA 1 256.06 GB / 256.06 GB 512 B + 0 B 51025KLA


nvme id-ctrl /dev/nvme0
NVME Identify Controller:
vid : 0x1179
ssvid : 0x1179
sn : 177S10WYTAMT
mn : THNSF5256GPUK TOSHIBA
fr : 51025KLA
rab : 1
ieee : 00080d
cmic : 0
mdts : 0
cntlid : 0
ver : 0
rtd3r : 0
rtd3e : 0
oaes : 0
oacs : 0x17
acl : 3
aerl : 3
frmw : 0x2
lpa : 0x2
elpe : 127
npss : 5
avscc : 0
apsta : 0x1
wctemp : 351
cctemp : 355
mtfa : 0
hmpre : 0
hmmin : 0
tnvmcap : 0
unvmcap : 0
rpmbs : 0
sqes : 0x66
cqes : 0x44
nn : 1
oncs : 0x1e
fuses : 0
fna : 0x4
vwc : 0x1
awun : 255
awupf : 0
nvscc : 0
acwu : 0
sgls : 0
subnqn :
ps 0 : mp:8.00W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
ps 1 : mp:3.90W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
ps 2 : mp:2.00W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
ps 3 : mp:0.1200W non-operational enlat:1000 exlat:1000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
ps 4 : mp:0.0120W non-operational enlat:5000 exlat:10000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
ps 5 : mp:0.0060W non-operational enlat:100000 exlat:50000 rrt:5 rrl:5
rwt:5 rwl:5 idle_power:- active_power:-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

@Nils,

Is your laptop XPS 9550/Precision 5510, too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Nils]

No, it's a Lenovo ThinkPad X270. Do you need any other information?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Ben]

I'm also experiencing issues since ugprading to 17.04. When I switch to
another TTY (via ctrl-alt-f1) the following errors get printed to the
screen:

[ 746.341551] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #525023: comm NetworkManager: reading directory iblock 0
[ 746.343318] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #524289: comm pool: reading directory iblock 0
[ 746.356125] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #11272213: comm systemd-udevd: reading directory iblock 0
[ 746.356139] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #11272210: comm systemd-udevd: reading directory iblock 0
[ 746.356332] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #11272193: comm systemd-udevd: reading directory iblock 0
[ 746.356338] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #11272825: comm systemd-udevd: reading directory iblock 0
[ 746.356400] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #11272210: comm systemd-udevd: reading directory iblock 0
[ 746.474632] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #524539: comm unity-settings-: reading directory iblock 0
[ 746.992814] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #5506108: comm BrowserBlocking: reading directory iblock 0
[ 746.304451] EXT4-fs error (device nvme0n1p7): ext4_find_entry:1463: inode #5506117: comm BrowserBlocking: reading directory iblock 0

I also tried to run `smartctl -t long /dev/nvme0n1p7` however the
results seem to indicate that the tool doesn't work with my particular
SSD:

smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.10.0-19-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number: PM951 NVMe SAMSUNG 512GB
Serial Number: S29PNX0H611013
Firmware Version: BXV77D0Q
PCI Vendor/Subsystem ID: 0x144d
IEEE OUI Identifier: 0x002538
Controller ID: 1
Number of Namespaces: 1
Namespace 1 Size/Capacity: 512,110,190,592 [512 GB]
Namespace 1 Utilization: 254,982,533,120 [254 GB]
Namespace 1 Formatted LBA Size: 512
Local Time is: Mon Apr 17 17:45:48 2017 AEST
Firmware Updates (0x06): 3 Slots
Optional Admin Commands (0x0017): Security Format Frmw_DL *Other*
Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Maximum Data Transfer Size: 32 Pages

Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 6.00W - - 0 0 0 0 5 5
1 + 4.20W - - 1 1 1 1 30 30
2 + 3.10W - - 2 2 2 2 100 100
3 - 0.0700W - - 3 3 3 3 500 5000
4 - 0.0050W - - 4 4 4 4 2000 22000

Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 0

=== START OF SMART DATA SECTION ===
Read NVMe SMART/Health Information failed: NVMe Status 0x2002

-------------------------

I'm using a Dell XPS 15 9550. Is there anything I can do to help you
guys debug the issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

@Nils,
With the current default value, your NVMe will transit to PS4. So let's add kernel parameter 'nvme-core.nvme_core.default_ps_max_latency_us=2000' to test if PS3 also shares the same issue.
If this issue persists, use 'nvme-core.nvme_core.default_ps_max_latency_us=0' to turn APST off.

@Ben,
Is your laptop XPS 9550/Precision 5510, too?

Please try 'nvme-core.nvme_core.default_ps_max_latency_us=5500', if the
issue persists, please try 'nvme-
core.nvme_core.default_ps_max_latency_us=200'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

@Ben, I saw that you uses XPS 9550, the comment was clipped at the
bottom.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[André Düwel]

@Kai-Heng Feng: I will test now with 6000, so far it looks good, but
hadn't much time to test during the holidays. I report back later this
day.

Additional Info for my XPS15 9550:
NVME Identify Controller:
vid : 0x144d
ssvid : 0x144d
sn : S29PNXAGB08057
mn : PM951 NVMe SAMSUNG 512GB
fr : BXV77D0Q
rab : 2
ieee : 002538
cmic : 0
mdts : 5
cntlid : 1
ver : 0
rtd3r : 0
rtd3e : 0
oaes : 0
oacs : 0x17
acl : 7
aerl : 3
frmw : 0x6
lpa : 0
elpe : 63
npss : 4
avscc : 0x1
apsta : 0x1
wctemp : 0
cctemp : 0
mtfa : 0
hmpre : 0
hmmin : 0
tnvmcap : 0
unvmcap : 0
rpmbs : 0
sqes : 0x66
cqes : 0x44
nn : 1
oncs : 0x1f
fuses : 0
fna : 0
vwc : 0x1
awun : 255
awupf : 0
nvscc : 1
acwu : 0
sgls : 0
subnqn :
ps 0 : mp:6.00W operational enlat:5 exlat:5 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
ps 1 : mp:4.20W operational enlat:30 exlat:30 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
ps 2 : mp:3.10W operational enlat:100 exlat:100 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
ps 3 : mp:0.0700W non-operational enlat:500 exlat:5000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
ps 4 : mp:0.0050W non-operational enlat:2000 exlat:22000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Shantanu Goel]

@Kai-heng Feng: I have a precision 5510 and faced same issue. I'm
running with "nvme_core.default_ps_max_latency_us=6000" since last 3
days without any problem now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Chris Sanders]

I have an xps15 9550 same as above, same controller, same issue. I set
nvme_core.default_ps_max_latency_us=6000 this morning and have ~1 hour
right now with no crash. I'll continue to run it today and report back.

The only issue I have seen with the 6k setting which I didn't not see
with a setting of 250 was a black screen on boot with an external
display connected. I can't imagine how that's affected by this setting.
I was able to boot by turning off the display until the laptop was
booted and then turning it on which seems to be working. This reliably
repeats with the 6k kernel setting with no problem on the 250 setting,
at least on the 3-4 reboots I've done in the last two days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[André Düwel]

@Kai-Heng Feng: Almost same here, the whole working day without any
issues. should I do a negative test with 23000 to confirm that ps/4 is
the issue for Samsung PM951?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

I don't think that's necessary, the default value (25000) is larger than
23000, so PS4 is enabled in this case.

Thank you for all the testing - this information will be useful for
patch author, Dell and Samsung.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Antoine Hedgecock]

Do we have an ETA on the patch coming out?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[André Düwel]

** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Francesco]

I want to report that I got the same bug under Ubuntu 16.04 with hardware enablement stack. The bug came with a recent update of the linux-generic-hwe, I now have 4.8.0.48.20 and I am affected.
I also have an XPS 9550 with the 512GB Samsung NVMe. Was the APST support backported to 4.8?

For the moment my workaround is using the old 4.4 kernel, but I will try
the kernel parameters as well...

Info about my drive:
$ sudo nvme list
Node SN Model Version Namespace Usage Format FW Rev
---------------- -------------------- ---------------------------------------- -------- --------- -------------------------- ---------------- --------
/dev/nvme0n1 S29PNXAGC05771 PM951 NVMe SAMSUNG 512GB 1.1 1 450,10 GB / 512,11 GB 512 B + 0 B BXV77D0Q
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Nils]

I have to admit that I'm not sure how or where to set 'nvme-
core.nvme_core.default_ps_max_latency_us=2000'.

I assumed that it's a kernel boot parameter that I can add in grub? But
when I do nothing changes and "sysctl -a", which I assumed should list
the changed parameter does not show anything related to nvme at all.

If you could advise me how or where to set that parameter, I will do so.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Chris Sanders]

I can now confirm that I've had a stable machine for more than 7 hours
using 6k for latency. I think the longest I had with out the option was
~3 hours and generally it was ~45 minutes to crash.

Nils, I'm setting the parameter in /etc/default/grub by appending it to
the "GRUB_CMDLINE_LINUX_DEFAULT" options then running `update-grub`.
That has worked for me, although I'm not sure how to confirm it took.
That is a permanent method, I started by just adding the 250 during boot
so it was for a single boot while testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Nils]

Thanks Chris.
I have tried 'nvme-core.nvme_core.default_ps_max_latency_us=2000' (though I have been unable to verify that the parameter actually changed) and the problem persisted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Chris Sanders]

Nils, from above use 'nvme-core.nvme_core.default_ps_max_latency_us=0'
to turn APST off.

That as my first step to confirm this is indeed related to APST and the
same bug. If that doesn't do it, I'm afraid you might have another
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[André Düwel]

@Nils: as Chris mentioned try to set it to 0 and then check with 'sudo
nvme get-feature -f 0x0c -H /dev/nvme0' if its really disabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Ben]

@Kai-Heng Feng

I tried 'nvme-core.nvme_core.default_ps_max_latency_us=5500' and got a
crash.

To confirm I have added the boot parameter:

$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=7cf9f325-5277-4249-b399-4df583e6286b ro quiet splash nvme-core.nvme_core.default_ps_max_latency_us=5500 vt.handoff=7

Will now try with 'nvme-core.nvme_core.default_ps_max_latency_us=200'.
Will let you know within 24 hours if it happens again

Thanks a lot for you hard work on this mate, we all really appreciate it
:)

If there's any other info you need, just let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Nils]

Hm, ok I seem to be unable to disable APST. :(

In '/etc/default/grub', I have

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme-
core.nvme_core.default_ps_max_latency_us=0"

and I get

cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=365f1a9c-9598-4ad5-a387-d02f771767a1 ro quiet splash nvme-core.nvme_core.default_ps_max_latency_us=0 vt.handoff=7

but when I try to confirm that it's disabled, I get

sudo nvme get-feature -f 0x0c -H /dev/nvme0
get-feature:0xc (Autonomous Power State Transition), Current value:0x000001
Autonomous Power State Transition Enable (APSTE): Enabled
Auto PST Entries .................

Not sure if I'm doing something wrong.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

@Ben, @Nils,

You have two 'nvme-core' in the parameter...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Nils]

Hm, thanks. That's copied verbatim from your comment above. ;)
I did not notice the inconsistency with the rest of the comments.

In the meantime I DID manage to disable APST with

sudo nvme set-feature -f 0x0c -v=0 /dev/nvme0

and that seems to have helped (no crash for 9 hours). I'll retry with
2000 now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Nils]

With nvme_core.default_ps_max_latency_us=2000 the problem persists.
However, everything seems fine with nvme_core.default_ps_max_latency_us=0.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

So on your machine (X270 + Toshiba), the NVMe has this issue on non-
operational power states, ps 3. The maximum working states is ps2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Aras Zagros]

I have a Dell XPS 15 9550 (i7-6700HQ 16GB-RAM 4K 512GB SSD Samsung).

I'm experiencing the same problem that @Ben has described.

My story: I went from 16.04 to 16.10 (no serious issues with the
previous versions) and then 17.04 almost a week ago, everything with the
previous versions was great but seems like 17.04 has two really
bothering issues with my device, this one and "slow mouse pointer
issue".

Guys seems like there isn't any solid fixes so far. Should I disable
"APST" too?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[André Düwel]

@Aras: I have exactly the same Laptop as you have. You do not need to
disable it completely, just change in the '/etc/default/grub' the
following line

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=6000"

This way, at least the most power saving states are still enabled (6W if
disabled vs. 0,07W with PS/3) :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Seth Forshee]

@kaihengfeng - based on the number of incidents here I'm thinking that
enabling APST was premature. Maybe we just need to revert "nvme: Enable
autonomous power state transitions" for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[André Düwel]

I forgot to mention that you need to run 'update-grub' and reboot your
system :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[André Düwel]

@sforshee: You would suggest an other solution, e.g. setting the default
value for nvme_core.default_ps_max_latency_us to 0, this way it is still
possible to enable the power saving features for experienced users
without having an impact to everyone else :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Ben]

@kaihengfeng

I haven't gotten any issues so far with
'nvme_core.default_ps_max_latency_us=5500'. That was with around 12
hours of use yesterday (previously, the issue was occurring within 2
hours).

$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=7cf9f325-5277-4249-b399-4df583e6286b ro quiet splash nvme_core.default_ps_max_latency_us=5500 vt.handoff=7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

The upstream author sent a patch set [1] according to this bug report
(thanks guys!). Looks like 4.11 will disable APST and make it opt-in,
and 4.12 will introduce a new quirk to avoid deepest power state.

I'll backport the patch set once it lands at linux-nvme tree.

[1]: http://lists.infradead.org/pipermail/linux-
nvme/2017-April/009519.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

Patch v3:
http://lists.infradead.org/pipermail/linux-nvme/2017-April/009683.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Andy Lutomirski]

The quirk updates have landed here in the linux-block tree here:

https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-
block.git/commit/?h=for-
linus&id=be56945c4edd5a3da15f8254b68d1ddb1588d0c4

Reporters, could you test that kernel? (Or Kai-Heng, is there a way you
could build a test kernel that people could use?)

The current 4.11 queue does not disable APST entirely on Samsung
devices. Instead it turns off the deepest sleep state on the affected
drives on the affected laptops. Hopefully this covers all the
problematic cases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

Please try kernel at [1] without 'nvme_core.default_ps_max_latency_us='
parameter, it includes '[PATCH v3 0/2] nvme APST quirk updates, take
two'.

It does two things:
1. Enable APST to ps3 on Dell XPS/Precision with Samsung NVMe,
2. Disable APST on Toshiba NVMe.

[1] http://people.canonical.com/~khfeng/lp1678184/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

I didn't see your comment while I was commenting...

Thank you for your work, Andy!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[André Düwel]

I will test it :) Thanks for all your work!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[André Düwel]

It works, no crashes so far :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[André Düwel]

@Kai-Heng Feng, @Seth Forshee: should we move the ticket status to fix
committed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

No, not yet. I am working on that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Charlotte Manning]

We're seeing this after upgrading to hwe-edge kernel (4.10.0.X) from Ubuntu 16.04,
so far three machines:
Intel Skull Canyon NUC6i7KYK with Intel SSDPEKKF512G nvme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[sridhar basam]

I am seeing this after upgrading to the 4.8.0-49 kernel on Ubuntu 16.04
with Intel 600P
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

@Charlotte Manning, @sridhar basam,

I opened another report to focus on Intel NVMe, LP: #1686592.

Can you attach output of `nvme id-ctrl /dev/nvme0` to that bug report?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Javi]

Booting with 4.8.0-49 or 4.10.0-20 crash system: Dell 9550 with PM951 NVMe Samsung 512GB
Now I'm working with 4.8.0-46 without any crashes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Chris Sanders]

Javi, see comment 25 above I'm booting with a work around on the 9550 with PM951.
However, also note that this bug shouldn't crash "on boot". I had a seperate issue with the 9550 with tlp and external usb devices causing an on boot crash which is not related to this. I recommend you run w/o any external devices to see if your boot problem is this, and add the above work around to keep you from crashing randomly when this bug triggers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Javi]

Sorry, to be more precise, not while booting. Really system crashed in
less than an hour using 4.8.0-49 or 4.10.0-20 kernels.

Thanks Chris, I will try with nvme_core.default_ps_max_latency_us param
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Chris Sanders]

Great, this should fix it for you then. I ran between 40 min and 3 hours
between crashes. I've been running daily (this is my daily use laptop
for work) and after the above fix it's completely stable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Javi]

Param nvme_core.default_ps_max_latency_us=6000 works with Dell 9550 -
Samsung PM951
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Stefan Bader]

** Also affects: linux (Ubuntu Zesty)
Importance: Undecided
Status: New

** Also affects: linux (Ubuntu Yakkety)
Importance: Undecided
Status: New

** Changed in: linux (Ubuntu Zesty)
Importance: Undecided => Medium

** Changed in: linux (Ubuntu Zesty)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Stefan Bader]

Patch 1/2 needed relaxed context checking to apply:
checking file drivers/nvme/host/core.c
Hunk #1 succeeded at 1262 (offset 2 lines).
Hunk #2 succeeded at 1341 (offset 2 lines).
checking file drivers/nvme/host/nvme.h
Hunk #1 succeeded at 81 (offset -1 lines).
checking file drivers/nvme/host/pci.c
Hunk #1 succeeded at 18 with fuzz 1 (offset -1 lines).
Hunk #2 succeeded at 2060 with fuzz 1 (offset 5 lines).
Hunk #3 succeeded at 2120 (offset 9 lines).

** Changed in: linux (Ubuntu Yakkety)
Importance: Undecided => Medium

** Changed in: linux (Ubuntu Yakkety)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Dimitri John Ledkov]

I believe I am affected, trying this out using the kernel from comment
44.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Andy Lutomirski]

Hi @keihengfeng,

Could you build a test kernel with the two test patches here applied:

https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/log/?h=nvme/power&id=1115e17962c597d8e6dd140d903a51a58d0ec2c0

I'd like to get some testing to see whether that works on the
problematic Samsung and Intel machines. (Those delete the quirk and
replace the APST table computation with something closer to what Intel
RSTe does.)

Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

Hi guys, can you try the kernel in [1] and remove the nvme kernel
parameter? I slightly tested it on the Precision 5510 at my hand,
haven't notice any errors so far.

[1] http://people.canonical.com/~khfeng/apst-rste-z/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Ian De Silva]

I experienced the same issue with 16.10 on a Dell 9550 (#1689357).

I installed the kernel from @kaihengfeng and have been using the new
kernel for the better part of the day (about 14 hours, 8 of which was
active-use time). No issues thus far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Jan Drewes]

I too have experienced this issue (Dell Precision 5510, Samsung PM951
512GB). I am now running the Kernel from Kai-Heng Feng (Posting #61)
since about 4.5h with no troubles. I'll let the machine run downloads
through the night, if it crashes I will report back. For now the fix
seems to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Jan Drewes]

Update: With the above kernel, my system is now running for 16h without
problems, including long periods of both high and very little load.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Jan Drewes]

Another update:

after running well for a few days, I have now encountered this bug (first time for me).
After the bug hit, the NVMe drive disappeared, and only a hard reset solved the problem (I lost some work...).

May 13 10:42:59 Trouble kernel: [23310.930585] nvme 0000:04:00.0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff
May 13 10:42:59 Trouble kernel: [23310.944569] nvme 0000:04:00.0: enabling device (0000 -> 0002)
May 13 10:42:59 Trouble kernel: [23310.944626] nvme nvme0: Removing after probe failure status: -19
May 13 10:42:59 Trouble kernel: [23310.944634] nvme0n1: detected capacity change from 512110190592 to 0
May 13 10:42:59 Trouble kernel: [23310.944918] blk_update_request: I/O error, dev nvme0n1, sector 0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Andy Lutomirski]

@jdrewes: just for completeness, can you post the nvme-related log
messages from the beginning of that boot? I want to verify that I
programmed the controller the way I meant to.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Jan Drewes]

May 13 04:14:41 Trouble systemd[1]: Starting Cryptography Setup for nvme0n1p3_crypt...
May 13 04:14:41 Trouble systemd-cryptsetup[618]: Volume nvme0n1p3_crypt already active.
May 13 04:14:41 Trouble systemd[1]: Started Cryptography Setup for nvme0n1p3_crypt.
May 13 04:14:41 Trouble systemd-fsck[682]: /dev/nvme0n1p2: clean, 321/124928 files, 169069/499712 blocks
May 13 04:14:41 Trouble systemd-fsck[686]: /dev/nvme0n1p1: 16 files, 5393/130812 clusters
May 13 04:14:41 Trouble systemd[1]: Found device /dev/mapper/nvme0n1p3_crypt.
May 13 04:14:41 Trouble kernel: [ 1.320827] nvme 0000:04:00.0: Samsung/Dell NVMe quirk is being ignored -- please report your results
May 13 04:14:41 Trouble kernel: [ 1.320866] nvme nvme0: pci function 0000:04:00.0
May 13 04:14:41 Trouble kernel: [ 1.430158] nvme nvme0: APST enabled: max PS = 4, max round-trip latency = 24000us, table = 18130100000000001813010000000000181301000000000020f05500000000000000000000000000000000000000000000000000000000000000000000000000
May 13 04:14:41 Trouble kernel: [ 1.448104] nvme0n1: p1 p2 p3
May 13 04:14:41 Trouble kernel: [ 12.893967] EXT4-fs (nvme0n1p2): mounting ext2 file system using the ext4 subsystem
May 13 04:14:41 Trouble kernel: [ 12.900921] EXT4-fs (nvme0n1p2): mounted filesystem without journal. Opts: (null)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Ian De Silva]

After running @kaihengfeng's kernel since May 10th, I've had 2 freeze-
ups. I couldn't stop and debug the first time (I was on a deadline),
but this time I'm seeing the same sort of messages in my syslog
("EXT4-fs (dm-2): re-mounted. Opts: errors=remount-ro"). It seems to
take days to get to this point.

I've attached my syslog in case that helps.

Just like @jdewes, I'm running with an encrypted file system (LUKS on
LLVM).

** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+attachment/4877047/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

I can confirm above two new incident. I still encountered this issue
after 3 days on a Precision 5510.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Stephen Hamer]

Hi,

Running 64-bit Ubuntu 16.04 on a new quietpc "sentinel" fanless pc with
a 256GB Samsung PM961 Polaris NVMe M.2 SSD.

Came back to my set-up this lunchtime and found that the screen had
frozen - first ever crash in 7 years of using ubuntu!

Did Ctrl+Alt+F4 to get to a terminal and got this message:

EXT4-fs error (dev nvme0n1p4:ext4_find_entry:1461:inode #1460718: com
(agetty): reading directory block lblock 0

Is it the same issue?

Solution ideas?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

Stephen, what linux kernel version do you use?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[François]

Hi,

I'm running Zesty on the following:

Linux francois-XPS-15-9560 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28
16:14:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

and seem to be affected by the same bug.

I tried the kernel listed in #61 and was stable for at least 2 hours.
When I got back from lunch and my computer logged off (blank screen), it
had crashed with the following error:

EXT4-fs error (device nvme0n1p1à: ext4_find_entry:1463: inode #1835009: comm (plymouth): reading directory lblock 0
ecryptfs_encrypt_page: Error attempting to write lower page; rc = [-5]


Let me know if there is any other info you'd like from me. Thanks!

$ sudo nvme id-ctrl /dev/nvme0

NVME Identify Controller:
vid : 0x144d
ssvid : 0x144d
sn : S33XNX0HC01366
mn : PM961 NVMe SAMSUNG 1024GB
fr : CXY74D1Q
rab : 2
ieee : 002538
cmic : 0
mdts : 0
cntlid : 2
ver : 10200
rtd3r : 186a0
rtd3e : 4c4b40
oaes : 0
oacs : 0x17
acl : 7
aerl : 3
frmw : 0x16
lpa : 0x2
elpe : 63
npss : 4
avscc : 0x1
apsta : 0x1
wctemp : 341
cctemp : 344
mtfa : 0
hmpre : 0
hmmin : 0
tnvmcap : 1024209543168
unvmcap : 0
rpmbs : 0
sqes : 0x66
cqes : 0x44
nn : 1
oncs : 0x1f
fuses : 0
fna : 0x1
vwc : 0x1
awun : 255
awupf : 0
nvscc : 1
acwu : 0
sgls : 0
subnqn :
ps 0 : mp:7.60W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
ps 1 : mp:5.00W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
ps 2 : mp:3.60W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

Sounds like even with new RSTe policy, we still need to disable PS4 for
XPS 9550/Precision 5510 as a temporary solution.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Stephen Hamer]

Hi Kai-Heng,

You ask:

"Stephen, what linux kernel version do you use?"

***@azed-H270N:~$ uname -a
Linux azed-H270N 4.8.0-51-generic #54~16.04.1-Ubuntu SMP Wed Apr 26 16:00:28 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

My bad, didn't notice it's XPS 9560...
To disable the deepest power state, you can add this to your kernel parameter:
"nvme_core.default_ps_max_latency_us=6000".

Please report back if this works, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[François]

@kaihengfeng: could you please expand on your comment in #73? is it
something that can be done with kernel options? does the kernel in
proposed mentioned in #74 also fixing the issue you are mentioning? also
note that I have an XPS 9560 (not 9550).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Thadeu Lima de Souza Cascardo]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
zesty' to 'verification-done-zesty'. If the problem still exists, change
the tag 'verification-needed-zesty' to 'verification-failed-zesty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kleber Sacilotto de Souza]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-
yakkety'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[John Neffenger]

I think I hit this problem, but with the 256 GB Lite-On (or LiteOn) NVMe
M.2 PCIe CX2 Series Enterprise Solid-State Drive Model CA1-8B256 that
came standard in my 2017 Dell Precision Tower 3420.

I'm on the HWE Kernel with the "linux-generic-hwe-16.04" package, having
installed from the Ubuntu 16.04.2 LTS amd64 ISO file. I didn't notice
any file system errors until I upgraded to the "linux-
image-4.8.0-53-generic" package on May 25, 2017. Below is my upgrade
schedule showing when the errors occurred:

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 ← Started noticing errors on NVMe drive

First my Thunderbird Lightning calendar database got corrupted so I
couldn't add events. One time the system just froze, with the mouse
cursor and keyboard not working. Yesterday, the root file system
remounted read-only after waking from suspend.

This morning I added "nvme_core.default_ps_max_latency_us=0" to the Grub
configuration, and after repairing the file system errors with "e2fsck",
everything seems to be working fine so far:

/etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash swapaccount=1 nvme_core.default_ps_max_latency_us=0"

I'm considering moving back to the GA 16.04 kernel, just to be more
conservative in my system updates. Is the general advice to use the HWE
kernel only if we need support for some new hardware, but otherwise,
stay on the GA kernel?

Is there anything in Kernel version 4.8.0-53 that may have caused the
problem or made it more likely to appear?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[John Neffenger]

Oops, wrong model number on the Lite-On drive in my Dell Precision Tower
3420. It should be Lite-On Model CX2-8B256-Q11.

The "nvme list" command reports:

Node: /dev/nvme0n1
Model: CX2-8B256-Q11 NVMe LITEON 256GB
Version: 1.2
Namespace: 1
Usage: 0.00 B / 256.06 GB
Format: 512 B + 0 B
FW Rev: 48811QD
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

@John

Can you paste the output of `nvme id-ctrl /dev/nvme0`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[François]

@kaihengfeng, to follow up with #77, using 4.12.0rc3 and the following
boot options

$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.12.0-041200rc3-generic root=UUID=0768ab04-826b-49ba-81c1-9e51657ecd48 ro quiet splash acpi_enforce_resources=lax nouveau.modeset=0 nvme_core.default_ps_max_latency_us=6000 vt.handoff=7

I still experience this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[John Neffenger]

@kaihengfeng Here you go:

$ sudo nvme id-ctrl /dev/nvme0
NVME Identify Controller:
vid : 0x14a4
ssvid : 0x1b4b
sn : TW0XVRV7LOH006AJ09F1
mn : CX2-8B256-Q11 NVMe LITEON 256GB
fr : 48811QD
rab : 0
ieee : 002303
cmic : 0
mdts : 5
cntlid : 1
ver : 10200
rtd3r : f4240
rtd3e : f4240
oaes : 0
oacs : 0x1f
acl : 3
aerl : 3
frmw : 0x14
lpa : 0x2
elpe : 63
npss : 4
avscc : 0x1
apsta : 0x1
wctemp : 358
cctemp : 368
mtfa : 50
hmpre : 0
hmmin : 0
tnvmcap : 256060514304
unvmcap : 0
rpmbs : 0
sqes : 0x66
cqes : 0x44
nn : 1
oncs : 0x1f
fuses : 0
fna : 0
vwc : 0x1
awun : 255
awupf : 7
nvscc : 1
acwu : 0
sgls : 0
ps 0 : mp:8.00W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
ps 1 : mp:4.00W operational enlat:5 exlat:5 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
ps 2 : mp:2.10W operational enlat:5 exlat:5 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
ps 3 : mp:0.1000W non-operational enlat:5000 exlat:5000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
ps 4 : mp:0.0100W non-operational enlat:50000 exlat:100000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Judy Brock]

This is not a Samsung drive

-----Original Message-----
From: ***@canonical.com [mailto:***@canonical.com] On Behalf Of John Neffenger
Sent: Tuesday, May 30, 2017 8:50 AM
To: Judy Brock
Subject: [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

@kaihengfeng Here you go:

$ sudo nvme id-ctrl /dev/nvme0
NVME Identify Controller:
vid : 0x14a4
ssvid : 0x1b4b
sn : TW0XVRV7LOH006AJ09F1
mn : CX2-8B256-Q11 NVMe LITEON 256GB
fr : 48811QD
rab : 0
ieee : 002303
cmic : 0
mdts : 5
cntlid : 1
ver : 10200
rtd3r : f4240
rtd3e : f4240
oaes : 0
oacs : 0x1f
acl : 3
aerl : 3
frmw : 0x14
lpa : 0x2
elpe : 63
npss : 4
avscc : 0x1
apsta : 0x1
wctemp : 358
cctemp : 368
mtfa : 50
hmpre : 0
hmmin : 0
tnvmcap : 256060514304
unvmcap : 0
rpmbs : 0
sqes : 0x66
cqes : 0x44
nn : 1
oncs : 0x1f
fuses : 0
fna : 0
vwc : 0x1
awun : 255
awupf : 7
nvscc : 1
acwu : 0
sgls : 0
ps 0 : mp:8.00W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
ps 1 : mp:4.00W operational enlat:5 exlat:5 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
ps 2 : mp:2.10W operational enlat:5 exlat:5 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
ps 3 : mp:0.1000W non-operational enlat:5000 exlat:5000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
ps 4 : mp:0.0100W non-operational enlat:50000 exlat:100000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Yakkety:
Fix Committed
Status in linux source package in Zesty:
Fix Committed

Bug description:
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
experiencing the same symptoms with the same model laptop except with
a 512GB Samsung. 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.

$ sudo nvme list
Node SN Model Namespace Usage Format FW Rev
---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1 ************** PM951 NVMe SAMSUNG 512GB 1 500.20 GB / 512.11 GB 512 B + 0 B BXV76D0Q

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-14-generic 4.10.0-14.16
ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
Uname: Linux 4.10.0-14-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: ajclayton 3305 F.... pulseaudio
CurrentDesktop: Unity:Unity7
Date: Fri Mar 31 09:42:38 2017
InstallationDate: Installed on 2012-09-08 (1665 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: Dell Inc. XPS 15 9550
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt nouveau.modeset=0 log_buf_len=20M
RelatedPackageVersions:
linux-restricted-modules-4.10.0-14-generic N/A
linux-backports-modules-4.10.0-14-generic N/A
linux-firmware 1.164
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
dmi.bios.date: 04/07/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 01.02.00
dmi.board.name: 0N7TVV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 15 9550
dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

@John, I opened a new bug for LiteOn, LP: #1694596.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Launchpad Bug Tracker]

This post might be inappropriate. Click to display it.

[Marco Bernasocchi]

Hi Same issue with a Lenovo X1 yoga with 512ssd

sudo nvme list
Node SN Model Namespace Usage Format FW Rev
---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1 S2CYNAAH200772 SAMSUNG MZVKV512HAJH-000L1 1 170.68 GB / 512.11 GB 512 B + 0 B 6L0QBXX7


***@placebo:~$ sudo nvme id-ctrl /dev/nvme0
NVME Identify Controller:
vid : 0x144d
ssvid : 0x144d
sn : S2CYNAAH200772
mn : SAMSUNG MZVKV512HAJH-000L1
fr : 6L0QBXX7
rab : 2
ieee : 002538
cmic : 0
mdts : 5
cntlid : 1
ver : 0
rtd3r : 0
rtd3e : 0
oaes : 0
oacs : 0x7
acl : 7
aerl : 3
frmw : 0x6
lpa : 0x1
elpe : 63
npss : 4
avscc : 0x1
apsta : 0x1
wctemp : 0
cctemp : 0
mtfa : 0
hmpre : 0
hmmin : 0
tnvmcap : 0
unvmcap : 0
rpmbs : 0
sqes : 0x66
cqes : 0x44
nn : 1
oncs : 0x1f
fuses : 0
fna : 0
vwc : 0x1
awun : 255
awupf : 0
nvscc : 1
acwu : 0
sgls : 0
subnqn :
ps 0 : mp:6.50W operational enlat:5 exlat:5 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
ps 1 : mp:6.40W operational enlat:30 exlat:30 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
ps 2 : mp:3.60W operational enlat:100 exlat:100 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
ps 3 : mp:0.0700W non-operational enlat:500 exlat:5000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
ps 4 : mp:0.0050W non-operational enlat:2000 exlat:22000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
***@placebo:~$




sudo nvme get-feature -f 0x0c -H /dev/nvme0n1
get-feature:0xc (Autonomous Power State Transition), Current value:0x000001
Autonomous Power State Transition Enable (APSTE): Enabled
Auto PST Entries .................
Entry[ 0]
.................
Idle Time Prior to Transition (ITPT): 275 ms
Idle Transition Power State (ITPS): 3
.................
Entry[ 1]
.................
Idle Time Prior to Transition (ITPT): 275 ms
Idle Transition Power State (ITPS): 3
.................
Entry[ 2]
.................
Idle Time Prior to Transition (ITPT): 275 ms
Idle Transition Power State (ITPS): 3
.................
Entry[ 3]
.................
Idle Time Prior to Transition (ITPT): 1200 ms
Idle Transition Power State (ITPS): 4
.................
Entry[ 4]
.................
Idle Time Prior to Transition (ITPT): 0 ms
Idle Transition Power State (ITPS): 0
.................
# there are 16 Entries all like Entry[4]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

@François
Add "nvme_core.default_ps_max_latency_us=0" to kernel parameter to see if disable APST completely helps.

@Marco
Add "nvme_core.default_ps_max_latency_us=5500" to kernel parameter to see if disable deepest power state helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Launchpad Bug Tracker]

This post might be inappropriate. Click to display it.

[Kleber Sacilotto de Souza]

** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Launchpad Bug Tracker]

This bug was fixed in the package linux - 4.8.0-54.57

---------------
linux (4.8.0-54.57) yakkety; urgency=low

* linux: 4.8.0-54.57 -proposed tracker (LP: #1692589)

* CVE-2017-0605
- tracing: Use strlcpy() instead of strcpy() in __trace_find_cmdline()

* Populating Hyper-V MSR for Ubuntu 13.10 (LP: #1193172)
- SAUCE: (no-up) hv: Supply vendor ID and package ABI

* [Hyper-V] Implement Hyper-V PTP Source (LP: #1676635)
- hv: allocate synic pages for all present CPUs
- hv: init percpu_list in hv_synic_alloc()
- Drivers: hv: vmbus: Prevent sending data on a rescinded channel
- hv: switch to cpuhp state machine for synic init/cleanup
- hv: make CPU offlining prevention fine-grained
- Drivers: hv: vmbus: Fix a rescind handling bug
- Drivers: hv: util: kvp: Fix a rescind processing issue
- Drivers: hv: util: Fcopy: Fix a rescind processing issue
- Drivers: hv: util: Backup: Fix a rescind processing issue
- Drivers: hv: vmbus: Move the definition of hv_x64_msr_hypercall_contents
- Drivers: hv: vmbus: Move the definition of generate_guest_id()
- Revert "UBUNTU: SAUCE: (no-up) hv: Supply vendor ID and package ABI"
- Drivers: hv vmbus: Move Hypercall page setup out of common code
- Drivers: hv: vmbus: Move Hypercall invocation code out of common code
- Drivers: hv: vmbus: Consolidate all Hyper-V specific clocksource code
- Drivers: hv: vmbus: Move the extracting of Hypervisor version information
- Drivers: hv: vmbus: Move the crash notification function
- Drivers: hv: vmbus: Move the check for hypercall page setup
- Drivers: hv: vmbus: Move the code to signal end of message
- Drivers: hv: vmbus: Restructure the clockevents code
- Drivers: hv: util: Use hv_get_current_tick() to get current tick
- Drivers: hv: vmbus: Get rid of an unsused variable
- Drivers: hv: vmbus: Define APIs to manipulate the message page
- Drivers: hv: vmbus: Define APIs to manipulate the event page
- Drivers: hv: vmbus: Define APIs to manipulate the synthetic interrupt
controller
- Drivers: hv: vmbus: Define an API to retrieve virtual processor index
- Drivers: hv: vmbus: Define an APIs to manage interrupt state
- Drivers: hv: vmbus: Cleanup hyperv_vmbus.h
- hv_util: switch to using timespec64
- Drivers: hv: restore hypervcall page cleanup before kexec
- Drivers: hv: restore TSC page cleanup before kexec
- Drivers: hv: balloon: add a fall through comment to hv_memory_notifier()
- Drivers: hv: vmbus: Use all supported IC versions to negotiate
- Drivers: hv: Log the negotiated IC versions.
- Drivers: hv: Fix the bug in generating the guest ID
- hv: export current Hyper-V clocksource
- hv_utils: implement Hyper-V PTP source
- SAUCE: (no-up) hv: Supply vendor ID and package ABI

* CIFS: Enable encryption for SMB3 (LP: #1670508)
- SMB3: Add mount parameter to allow user to override max credits
- SMB2: Separate Kerberos authentication from SMB2_sess_setup
- SMB2: Separate RawNTLMSSP authentication from SMB2_sess_setup
- SMB3: parsing for new snapshot timestamp mount parm
- cifs: Simplify SMB2 and SMB311 dependencies
- cifs: Only select the required crypto modules
- cifs: Add soft dependencies
- CIFS: Separate SMB2 header structure
- CIFS: Make SendReceive2() takes resp iov
- CIFS: Make send_cancel take rqst as argument
- CIFS: Send RFC1001 length in a separate iov
- CIFS: Separate SMB2 sync header processing
- CIFS: Separate RFC1001 length processing for SMB2 read
- CIFS: Add capability to transform requests before sending
- CIFS: Enable encryption during session setup phase
- CIFS: Encrypt SMB3 requests before sending
- CIFS: Add transform header handling callbacks
- CIFS: Add mid handle callback
- CIFS: Add copy into pages callback for a read operation
- CIFS: Decrypt and process small encrypted packets
- CIFS: Add capability to decrypt big read responses
- CIFS: Allow to switch on encryption with seal mount option
- CIFS: Fix possible use after free in demultiplex thread

* APST quirk needed for Samsung 512GB NVMe drive (LP: #1678184)
- nvme: Adjust the Samsung APST quirk
- nvme: Quirk APST off on "THNSF5256GPUK TOSHIBA"

-- Kleber Sacilotto de Souza <***@canonical.com> Mon, 22 May
2017 18:56:12 +0200

** Changed in: linux (Ubuntu Yakkety)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Josh Lilly]

I would like to add that this bug also affects 256GB versions of the Samsung NVMe drives.
The quirk has been added for the 512GB, can we also have one added for the 256GB?

Here is my output of nvme-cli

**
nvme list

Node SN Model Version Namespace Usage Format FW Rev
---------------- -------------------- ---------------------------------------- -------- --------- -------------------------- ---------------- --------
/dev/nvme0n1 S29NNXAGC38399 PM951 NVMe SAMSUNG 256GB 1.1 1 201.30 GB / 256.06 GB 512 B + 0 B BXV77D0Q



nvme id-ctrl /dev/nvme0n1

NVME Identify Controller:
vid : 0x144d
ssvid : 0x144d
sn : S29NNXAGC38399
mn : PM951 NVMe SAMSUNG 256GB
fr : BXV77D0Q
rab : 2
ieee : 002538
cmic : 0
mdts : 5
cntlid : 1
ver : 0
rtd3r : 0
rtd3e : 0
oaes : 0
oacs : 0x17
acl : 7
aerl : 3
frmw : 0x6
lpa : 0
elpe : 63
npss : 4
avscc : 0x1
apsta : 0x1
wctemp : 0
cctemp : 0
mtfa : 0
hmpre : 0
hmmin : 0
tnvmcap : 0
unvmcap : 0
rpmbs : 0
sqes : 0x66
cqes : 0x44
nn : 1
oncs : 0x1f
fuses : 0
fna : 0
vwc : 0x1
awun : 255
awupf : 0
nvscc : 1
acwu : 0
sgls : 0
ps 0 : mp:6.00W operational enlat:5 exlat:5 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
ps 1 : mp:4.20W operational enlat:30 exlat:30 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
ps 2 : mp:3.10W operational enlat:100 exlat:100 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
ps 3 : mp:0.0700W non-operational enlat:500 exlat:5000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
ps 4 : mp:0.0050W non-operational enlat:2000 exlat:22000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

Josh,

Can you file a new bug?

Also attach `lspci -nn` and `sudo nvme get-feature -f 0x0c -H
/dev/nvme0` in the new bug. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Thim Thom]

Followed the instructions from here, but
nvme_core.default_ps_max_latency_us=6000
did not work for me.

I'm now on nvme_core.default_ps_max_latency_us= 0 and will try if this
helps.

17.04 4.12 from mainline, Bios from May, Dell Precision 5510 (from
12/2015), Samsung 512 GB
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Kai-Heng Feng]

Thim, what happened to your NVMe? Can you file a new bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions

[Steve Roberts]

Just landed here with similar issue on Samsung 960 EVO 500GB, system
crashes/hangs with disk inaccessible (?) but mostly after resume from
suspend, or latest 3 mins after cold boot...


Kernel 4.10.0-26-generic
M/B Asus Prime B350m-A

Seems it is either not fixed or I have another bug....

e.g.
Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST device=00:00.0 address=0xfffffffdf8000000 flags=0x0a00]
Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme 0000:01:00.0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0xffff
Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 callbacks suppressed
Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme 0000:01:00.0: Refused to change power state, currently in D3
Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe failure status: -19
Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change from 500107862016 to 0
Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, dev nvme0n1, sector 0


nvme list

/dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB
1.2 1 125.20 GB / 500.11 GB 512 B + 0 B 2B7QCXE7

sudo nvme id-ctrl /dev/nvme0

NVME Identify Controller:
vid : 0x144d
ssvid : 0x144d
sn : S3EUNX0J305518L
mn : Samsung SSD 960 EVO 500GB
fr : 2B7QCXE7
rab : 2
ieee : 002538
cmic : 0
mdts : 9
cntlid : 2
ver : 10200
rtd3r : 7a120
rtd3e : 4c4b40
oaes : 0
oacs : 0x7
acl : 7
aerl : 3
frmw : 0x16
lpa : 0x3
elpe : 63
npss : 4
avscc : 0x1
apsta : 0x1
wctemp : 350
cctemp : 352
mtfa : 0
hmpre : 0
hmmin : 0
tnvmcap : 500107862016
unvmcap : 0
rpmbs : 0
sqes : 0x66
cqes : 0x44
nn : 1
oncs : 0x1f
fuses : 0
fna : 0x5
vwc : 0x1
awun : 255
awupf : 0
nvscc : 1
acwu : 0
sgls : 0
ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678184

Title:
APST quirk needed for Samsung 512GB NVMe drive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+subscriptions