Didn't have this problem until I upgraded with Samsung 970 EVO Plus
NVME. Nope, GRUB_CMDLINE_LINUX_DEFAULT="quiet splash
nvme_core.default_ps_max_latency_us=5500" does not work for me, nor 200
or 0. The crash happens so random, it can go for days without crashing
but still, does not provide
Got a new laptop from Amazon, wiped the nasty windows that came with it
and put linux on there and started experiencing this issue almost right
away. Finally found my way here after weeks of banging my head against
the wall, googling log messages and trying every crappy troubleshooting
Exactly the same bug with Samsung SSD 970 EVO Plus 1TB. Ubuntu 20.04, laptop
System76 Lemur Pro. The problem is with software, as I tried to replace the SSD
with another one, but the problem is still here. After lid is closed or after
suspend mode the system crashes with multiple `ext4 FS error
Hi
I'm now experiencing this bug with
Samsung SSD 970 EVO Plus 2TB on a Lenovo T480 with 2 nvme drives.
nvme_core.default_ps_max_latency_us=0 does not help it.
Because the problem only arose after two months, I can't rule a hardware
failure, although smart looks all fine.
Some relevant info
Hi
I'm now experiencing this bug with
Samsung SSD 970 EVO Plus 2TB on a Lenovo T480 with 2 nvme drives.
nvme_core.default_ps_max_latency_us=0 does not help it.
Because the problem only arose after two months, I can't rule a hardware
failure, although smart looks all fine.
Some relevant info
Ber,
Please file a separate 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:
Oh, this is also helpful:
sudo nvme list:
Node SN Model
Namespace Usage Format FW Rev
-
Im also experiencing this bug.
uname -a gives:
Linux ThinkPad-T480s 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19
08:06:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
I set nvme_core.default_ps_max_latency_us=0, to turn APST off. Uptil now, I
haven't experienced any crashes. I haven't tried any
@ian-x88 Hi Ian, nothing changed, so no solution for now. I am
considering to buy a new laptop. The problem makes me feel so confused
and upset. The SSD is Samsung 250 GB 860 EVO Sata III 64L V NAND Solid
State Drive. The infinite loop for ext4 fs error occur irregularly,
might be twice an hour or
Hello Yingfag - can I check please - was it a 1TB Samsung SSD? Which
model of SSD (950? 960? 970? something else?). When you changed the SSD
- did you keep the same model? What was your final solution? Regards,
Ian.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I was experiencing this issue for around 1 year, always repeated
irregularly. Allienware 13 with Samsung SDD. Over 7 times
reinstallation, changed SSD twice.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have posted my 1TB (PM951) issue as a new bug here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805816
--
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
Hi Kai-Heng, thanks!
Overnight I've used `nvme_core.default_ps_max_latency_us=0` in GRUB with
no read-only crashes (everything has been smooth). I left the machine
awake all night, I've since suspended & awoken it twice, all seems to be
ok.
As expected all APSTE is disabled:
`
$ sudo nvme
Ian, I am working on this issue and trying to find the root cause of it.
Let's see what I can find.
--
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
To follow-up. Earlier today I fresh-booted and didn't use the APST
disable command - my machine crashed out with read-only errors after
minutes.
I then updated grub to use `nvme_core.default_ps_max_latency_us=250` as
suggested - it was stable for 6 hours, through 2 suspends. A little
while ago it
20, 2018 3:39 AM
To: Judy Brock
Subject: [Bug 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive
I'd like to follow-up on this bug - it affects me using kernel 4.19.0 on
a Dell XPS 9550 with a 1TB Samsung drive. Details below. Do I need to
open a new bug as I've got a 1TB drive
I'd like to follow-up on this bug - it affects me using kernel 4.19.0 on
a Dell XPS 9550 with a 1TB Samsung drive. Details below. Do I need to
open a new bug as I've got a 1TB drive and this bug report was opened
for a 512GB drive?
$ uname -a
Linux ian-XPS-15-9550 4.19.0-041900-generic
> On 22 Jan 2018, at 9:34 AM, Lucas Zanella <1678...@bugs.launchpad.net> wrote:
>
> I'm having this on my Razer Blade Stealth, 512gb samsung SSD, ubuntu
> 17.10.1, but also had the issue on 17.04 and today at 16.04 after
> updating (possibly related; or not). I installed 17.10.1 today and
>
I'm having this on my Razer Blade Stealth, 512gb samsung SSD, ubuntu
17.10.1, but also had the issue on 17.04 and today at 16.04 after
updating (possibly related; or not). I installed 17.10.1 today and
immediately updated and the error ocurred. I then reinstalled without
updating and I've seen no
> On 28 Oct 2017, at 9:10 PM, Bashar wrote:
>
> Same problem here on a Lenovo ideapad Y700 and Ubuntu 16.04
> /dev/nvme0n1SAMSUNG MZVLW512HMJP-000L2
>
> I disabled APST by adding nvme_core.default_ps_max_latency_us=0 to the
> kernel parameters in /etc/default/grub and
Same problem here on a Lenovo ideapad Y700 and Ubuntu 16.04
/dev/nvme0n1SAMSUNG MZVLW512HMJP-000L2
I disabled APST by adding nvme_core.default_ps_max_latency_us=0 to the
kernel parameters in /etc/default/grub and works ok, no blocking since
then.
--
You received this bug notification
What you faced (D3 issue) is not the same as this one (APST issue).
Please 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
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.
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
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
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
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
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
** 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
This bug was fixed in the package linux - 4.10.0-22.24
---
linux (4.10.0-22.24) zesty; urgency=low
* linux: 4.10.0-22.24 -proposed tracker (LP: #1691146)
* Fix NVLINK2 TCE route (LP: #1690155)
- powerpc/powernv: Fix TCE kill on NVLink2
* CVE-2017-0605
- tracing: Use
@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
Hi Same issue with a Lenovo X1 yoga with 512ssd
sudo nvme list
Node SN Model
Namespace Usage Format FW Rev
-
This bug was fixed in the package linux - 4.10.0-22.24
---
linux (4.10.0-22.24) zesty; urgency=low
* linux: 4.10.0-22.24 -proposed tracker (LP: #1691146)
* Fix NVLINK2 TCE route (LP: #1690155)
- powerpc/powernv: Fix TCE kill on NVLink2
* CVE-2017-0605
- tracing: Use
This is not a Samsung drive
-Original Message-
From: boun...@canonical.com [mailto:boun...@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
@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
@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 :
@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
@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
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
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
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
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
@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
** 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
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
Hi Kai-Heng,
You ask:
"Stephen, what linux kernel version do you use?"
azed@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
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
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
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
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
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
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
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
@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.
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 :04:00.0: controller is
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
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.
--
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
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
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=1115e17962c597d8e6dd140d903a51a58d0ec2c0
I'd like to get some testing to see whether that works on the
problematic Samsung and
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
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
** 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 =>
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
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
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
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
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
@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.
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
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.
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:
@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
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:
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
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
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]
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=be56945c4edd5a3da15f8254b68d1ddb1588d0c4
Reporters, could you test that kernel? (Or Kai-Heng, is there a way you
could build a test kernel
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
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]:
@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
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
@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
@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
@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
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
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:
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
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
@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
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
@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
@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:
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
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.
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
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
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
** 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
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:
1 - 100 of 120 matches
Mail list logo