** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change power
Apparently yes. File attached.
With:
$ cat /proc/cmdline
BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-3-generic
root=UUID=0885f579-b2ff-4c94-964c-d65c30bb7761 ro rootflags=subvol=@
nvme_core.force_apst=1
I have been at least 8 days without re-booting with suspend/resume a
couple of times a day at least.
Steve,
Does the issue completely go away with my kernel?
Can you attach `sudo lspci -vvnn` with the kernel?
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsun
$ cat /proc/cmdline
BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-3-generic
root=UUID=0885f579-b2ff-4c94-964c-d65c30bb7761 ro rootflags=subvol=@
nvme_core.force_apst=1
Been through several cycles of suspend and resume, without any apparent
issues.
But I note:
$ sudo nvme id-ctrl /dev/nvme0n1
ps0 :
Ok, testing now... will report back...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change power state
Status in linux package in U
Steve,
I've found that the PCIe common clock may be the culprit here.
Please try the kernel [1] with kernel parameter nvme_core.force_apst=1.
[1] https://people.canonical.com/~khfeng/quirk-no-commclk/
--
You received this bug notification because you are a member of Kernel
Packages, which is su
Hmmm so if I understand PCIe ASPM would be set in the BIOS. I
updated the BIOS to a later version (3803) since the original issue
(soon after the last testing at end of Feb). So I guess it may be that
it has been disabled in the bios ?
I guess I need to go back and try an older non-fixed kerne
There is another user faces the same issue. The PCIe ASPM is enabled for
SM/PM/EVO 961, and disabling ASPM solves the issue for the user.
But ASPM is not enabled on your machine, so unfortunately it's not going
to help your case.
--
You received this bug notification because you are a member of
I have deleted/removed many of the older testing kernel, but I think
this one does not have the fix, based on post #97
$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.13.0-34-generic
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro
Suspend
Resume
$ sudo lspci -vvnn > lspci.txt
output attached
**
Hi Steve,
Can you boot with an older kernel with the original issue, suspend the
system, then attach `sudo lspci -vvnn`?
I think the ASPM get setup after the system resume from S3.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Realise I probably should have run as sudo, so sudo version attached
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705748/+attachment/5152446/+files/lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is
Hi Kai-Heng, Guessing that request is directed at me, so here it is:
$ lspci -vvnn
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Device
[1022:1450]
Subsystem: ASUSTeK Computer Inc. Device [1043:8747]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParE
Robert,
Can you attach `lspci -vvnn` here? Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change power state
Status in linux
This bug was fixed in the package linux - 4.4.0-119.143
---
linux (4.4.0-119.143) xenial; urgency=medium
* linux: 4.4.0-119.143 -proposed tracker (LP: #1760327)
* Dell XPS 13 9360 bluetooth scan can not detect any device (LP: #1759821)
- Revert "Bluetooth: btusb: fix QCA Rome
This bug was fixed in the package linux - 4.13.0-38.43
---
linux (4.13.0-38.43) artful; urgency=medium
* linux: 4.13.0-38.43 -proposed tracker (LP: #1755762)
* Servers going OOM after updating kernel from 4.10 to 4.13 (LP: #1748408)
- i40e: Fix memory leak related filter prog
** Tags removed: verification-needed-artful verification-needed-xenial
** Tags added: verification-done-artful verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/170574
I am not sure if I have done the correct thing, but following the
instructions above I have managed to install xenial-proposed kernel
4.13.0-38 on my Mint 18.2 XFCE system:
$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.13.0-38-generic
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro
I can confirm t
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-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag 'verifica
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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
The code is "Fix Committed" in the Arftul kernel tree, but it's not yet
"Fix Released" as a binary package. So 4.13.0-34 package doesn't contain
the fix yet.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
In case it helps, further test with 4.13.0-34
Feb 24 11:48:40 phs08 kernel: [0.00] Command line:
BOOT_IMAGE=/vmlinuz-4.13.0-34-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-
d3963957ab57 ro nvme_core.force_apst=1
... boots fine, appears ok then suspend overnight...
Feb 25 11:54:43 phs08 kern
http://people.canonical.com/~khfeng/lp1705748-pcireset/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change power state
Status in l
Hmm, I'll build a new one based on Bionic's kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change power state
Status in linux
Sorry for being so slow, and not sure I have run the correct tests:
Command line: BOOT_IMAGE=/vmlinuz-4.13.0-34-generic root=UUID=f7ae652b-
cbf6-48b8-bc6a-d3963957ab57 ro
Suspend and resume:
Feb 24 11:11:14 phs08 kernel: [ 7608.732297] nvme nvme0: controller is down;
will reset: CSTS=0x,
Please try [1].
The previous one was built on Bionic, it had higher libssl requirement
as a result. I build the new one on Xenial, so it should have the
correct version number.
[1] people.canonical.com/~khfeng/lp1746340-pcireset/
--
You received this bug notification because you are a member of
Can you manually install libssl1.1? Or skip installing header files, if
you don't use any DKMS.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB re
Unable to install the file:
linux-headers-4.13.0-34-generic_4.13.0-34.37~lp1746340_amd64.deb
due to missing dependency libssl1.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Tit
Build a new one, based on artful,
http://people.canonical.com/~khfeng/lp1746340-artful/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused t
Yes, but I am bit confused by that other thread, can you direct me to
the download of the specific kernel you want me to try.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Steve,
I guess LP: #1746340 is the same as this one.
Can you try this kernel with "nvme_core.force_apst=1"? I want to know if a PCI
reset for NVMe after resume can solve the issue.
people.canonical.com/~khfeng/lp1746340-2/
--
You received this bug notification because you are a member of Kerne
** Changed in: linux (Ubuntu Artful)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Artful)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Artful)
Status: New => In Progress
** Changed in: linux (Ubuntu Artful)
Assignee: (unassigned) => Ka
SRU: https://lists.ubuntu.com/archives/kernel-
team/2018-January/089222.html
** Description changed:
+ === SRU Justification ===
+ [Impact]
+ A user reported his NVMe went out to lunch after S3.
+
+ [Fix]
+ Disable APST for this particular NVMe + Motherboard setup.
+
+ [Test]
+ User confirmed t
> On 5 Jan 2018, at 7:28 PM, Steve Roberts <1705...@bugs.launchpad.net> wrote:
>
> Will this make it into the mainstream kernel updates or how do I track when
> it is ?
> I just installed 4.13.0-19 and the issue is still there.
I’ll backport it to Artful kernel. Thanks for the notice.
>
> --
Will this make it into the mainstream kernel updates or how do I track when it
is ?
I just installed 4.13.0-19 and the issue is still there.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
Sorry for slow response.
Yes all seems to be fine, I have had 9 days of uptime with numerous suspend and
resumes without issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Titl
https://lkml.org/lkml/2017/11/9/34
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change power state
Status in linux package in Ubunt
Steve, I'll send the patch if you have no concern.
Thanks for all the testing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change
Yes. Use "nvme_core.force_apst=1"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change power state
Status in linux package in Ubuntu
Installed that latest version, can confirm that apst is disabled without
the max_latency setting kernel parameter
I have also found a new BIOS for the m/b: 0902
So will also try and installing that and revert back to one of the
kernels with apst turned on, to see if any difference...
or is
My apology, I typed wrong PCIID for the Samsung device.
Please try this one instead,
http://people.canonical.com/~khfeng/lp1705748-again/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/170
Output from get-feature:
get-feature:0x0c (Autonomous Power State Transition), Current value: 0x01
Autonomous Power State Transition Enable (APSTE): Enabled
Auto PST Entries.
Entry[ 0]
.
Idle Time Prior to Trans
Can you attach the output of `nvme get-feature -f 0x0c -H /dev/nvme0`?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change power sta
Oct 26 17:23:41 phs08 kernel: [0.00] Command line:
BOOT_IMAGE=/vmlinuz-4.13.0-17-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-
d3963957ab57 ro
Suspend...
Oct 26 19:00:46 phs08 systemd-sleep[5347]: Suspending system...
Resume
Oct 26 19:57:11 phs08 kernel: [ 5841.689280] PM: resume of dev
Sorry for slow response:
Command line: BOOT_IMAGE=/vmlinuz-4.13.0-17-generic root=UUID=f7ae652b-
cbf6-48b8-bc6a-d3963957ab57 ro
Resulted in spontaneous disappearance (no suspend/resume needed):
Oct 26 17:20:44 phs08 kernel: [ 3011.057465] nvme nvme0: controller is down;
will reset: CSTS=0xf
The fault is mine. Didn't take out-of-tree proprietary modules into
account. Please try artful kernel here:
http://people.canonical.com/~khfeng/lp1705748-artful/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
I installed the files,
removed the nvme_core.default_ps_max_latency_us=0,
did an update-grub and rebooted...
failed to boot into graphical interface and then hung... reset needed
Command line: BOOT_IMAGE=/vmlinuz-4.14.0-rc4-evo+ryzen root=UUID
=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro
Suspect this
No, these two files are sufficient.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change power state
Status in linux package in Ubun
This time I built the kernel on top of mainline kernel, so there are
just two files.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to ch
Ah ok, so I will need to install 4.14 first ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change power state
Status in linux packa
Kai-Heng,
In reply to #66: I guess this is a definite indication that it is a
firmware issue.
#67: there are only two files to download, on all previous occasions
there have been four, is that correct ?
Steve
--
You received this bug notification because you are a member of Kernel
Packages, wh
Kai-Heng,
In response to #66, I guess that definitely points to a firmware issue
with Samsung drive
#67 I will try and let you know...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/17057
Steve, please try [1] without any NVMe parameters.
[1] http://people.canonical.com/~khfeng/lp1705748-evo+ryzen/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD
Steve,
I'll write a patch to let the system not to enable APST.
FWIW, my desktop ues Asus Prime B350m-A + Ryzen 7 1700, but with Intel
P600. Currently I don't have any issue when APST is enabled.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
Re: turn off APST completely
Tricky...
So I have been running with:
BOOT_IMAGE=/vmlinuz-4.13.0-8-generic
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro
nvme_core.default_ps_max_latency_us=0
for the last month or so with no issues
I suppose APST is about reducing power consumption, but
bplaa.yai,
Can you file a new bug?
SM/PM951 is an OEM version, which means it's already inside the laptop when you
unbox it.
That means we can make specific workaround for the laptop/NVMe combination.
--
You received this bug notification because you are a member of Kernel
Packages, which is su
FWIW, I'm also affected by this issue, but on a completely different
system (Razer Blade Stealth, Samsung PM951, Fedora 26 - kernel 4.13.4),
so I don't think specifically targeting Asus Prime B350m-A + Samsung 960
EVO would do it.
As the OP, I was having frequent random SSD disconnects (the issue
Hmm, there's no response from Samsung.
Do you think we should completely turn off APST for Asus Prime B350m-A +
Samsung 960 EVO?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Tit
Ok thanks and for the explanation - makes sense.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change power state
Status in linux pa
Raised the issue to Samsung:
http://lists.infradead.org/pipermail/linux-nvme/2017-September/012892.html
** Changed in: linux (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
That's because disks need to be stopped before chipsets/CPU goes to
suspend. So the internal messages are flushed *after* disk wakeup - disk
is not available at the end the suspend process.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
No, this seems to have been happening all along, if you look at the
timings in earlier posts...see post #25
...but what throws me and makes it more obscure it that the suspend
operations are logged on resume, and until yesterday I hadn't ever
managed to check the drive was actually alive (I actual
So is "nvme disk apparently does not become inaccessible until 3 min
after the system has woken up" a new behavior?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung
Tried that latest one... still fails after suspend but should I be using
nvme_core.default_ps_max_latency_us=1500 ?
But as I have said before it does bother me that the suspend and resume
operations seem to overlap and all are logged on resume.
Booted am:
Sep 7 10:02:44 phs08 kernel: [0.000
This kernel [1] resets NVMe controller before shutdown.
[1] http://people.canonical.com/~khfeng/pm961-reset/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 96
Just let you know, I am still working on this issue.
Currently digging through the spec, hopefully I can find some angle to try new
workarounds.
Completely disable APST should be last resort.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Also same result with nvme_core.default_ps_max_latency_us=1500
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change power state
Stat
Tried that latest version, same result:
Sep 1 16:56:16 phs08 kernel: [0.00] Command line:
BOOT_IMAGE=/vmlinuz-4.13.0-8-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-
d3963957ab57 ro
(Note without nvme_core.default_ps_max_latency_us=1500. hope this was
correct)
...
Sep 1 17:01:29 phs08 kern
Try it here:
http://people.canonical.com/~khfeng/pm961-quirks/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change power state
Stat
Originally can't read PCI status:
Aug 15 14:14:02 phs08 kernel: [ 2477.191603] nvme :01:00.0: controller is
down; will reset: CSTS=0x, PCI_STATUS=0x
Now only controller is dead:
Aug 30 09:35:19 phs08 kernel: [71904.271956] nvme nvme0: controller is down;
will reset: CSTS=0xff
Yes, correct I just searched the kernel log and no more
"...Refused to change..."
since I booted with:
Command line: BOOT_IMAGE=/vmlinuz-4.13.0-6-generic root=UUID=f7ae652b-
cbf6-48b8-bc6a-d3963957ab57 ro nvme_core.default_ps_max_latency_us=1500
--
You received this bug notification because yo
But no more "nvme :01:00.0: Refused to change power state, currently
in D3"?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change
I haven't yet tried with that latest kernel... but this morning, after 5
days of successful suspend/resume:
Aug 30 09:35:19 phs08 kernel: [71904.271956] nvme nvme0: controller is down;
will reset: CSTS=0x, PCI_STATUS=0x10
Aug 30 09:35:19 phs08 kernel: [71904.320269] print_req_error: I/O e
I built a kernel with the quirk. Please try it without the nvme_core
kernel parameter.
http://people.canonical.com/~khfeng/pm961/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Ti
Using http://people.canonical.com/~khfeng/lp1705748-sleep/
with "nvme_core.default_ps_max_latency_us=1500", to disable deepest
power state
Been through several suspend/resume cycles so far and seems to be ok.
--
You received this bug notification because you are a member of Kernel
Packages, wh
Use the one I built should be recent enough.
You can still get one from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.13-rc6/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Ti
Appreciate all your efforts Kai-Heng
Where do I get the latest mainline kernel ?
Thanks, Steve
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB r
Unfortunately still no joy
Aug 21 18:02:54 phs08 kernel: [0.00] Linux version 4.13.0-6-generic
(root@linux) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4))
#7~lp1705748 SMP Fri Aug 18 17:09:21 CST 2017 (Ubuntu
4.13.0-6.7~lp1705748-generic 4.13.0-rc5)
Aug 21 18:02:54 phs08 k
If this kernel still doesn't work, try latest mainline kernel with
"nvme_core.default_ps_max_latency_us=1500", do disable deepest power
state.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs
I guess NVMe probably needs a to sleep exlat time (6000 here) to let it
transit back to power state 0.
Please try http://people.canonical.com/~khfeng/lp1705748-sleep/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
Sorry for slow feedback
Unfortunately the issue is still there:
Aug 15 12:52:58 phs08 kernel: [0.00] Linux version 4.11.0-14-generic
(root@ryzen) (gcc version 6.3.0 20170618 (Ubuntu 6.3.0-19ubuntu1) ) #20 SMP Wed
Aug 9 20:56:51 CST 2017 (Ubuntu 4.11.0-14.20-generic 4.11.12)
Aug 15 1
Here you go:
http://people.canonical.com/~khfeng/lp1705748-8-9/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change power state
Sta
Yea, I think it's normal, because the kernel version is the same. The
old one with the same version will be removed before installing the new
one.
I have no idea about the nouveau part though. I'll build a new on based
on 4.11 to focus on the NVMe bug.
--
You received this bug notification becau
Unfortunately there seems another issue with this kernel:
The screen/video is blank on resume, I think this is the offending part:
ug 8 14:08:50 phs08 kernel: [ 165.478069] nouveau :27:00.0: DRM: resuming
fence...
Aug 8 14:08:50 phs08 kernel: [ 165.478082] nouveau :27:00.0: DRM:
resu
Ok, will test and report and back
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change power state
Status in linux package in Ubuntu
Please try this one:
http://people.canonical.com/~khfeng/lp1705748-3/
This kernel disables ASPT before controller shutdown. But looks like
it's not enough (comment #31), this kernel also explicitly set power
state 0 before controller shutdown.
--
You received this bug notification because you ar
I don't have a dmesg log file (due to systemd ?) but I attach syslog
from start of boot with the kernel to when the reset button pressed...
Thanks for your attention to this Kai-Heng, really appreciated, Steve.
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug
Can you attach the full dmesg? I'd like to check some additional
information.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change po
So last night I installed the kernel and it seems the issue persists:
Aug 3 02:30:59 phs08 kernel: [0.00] Command line:
BOOT_IMAGE=/vmlinuz-4.12.0-9-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-
d3963957ab57 ro
suspend:
Aug 3 02:52:35 phs08 systemd[1]: Reached target Sleep.
Aug 3 02:52:3
Sorry, I have downloaded but haven't got to testing it yet have had
to prioritise the day job... will aim to try this evening and report
back tomorrow...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
Roberts, does the new kernel I built still have the issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change power state
Status i
Please try this one:
http://people.canonical.com/~khfeng/lp1705748-disable-apst/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change
Probably need to change the device to full functional state before S3,
like how basic power management works.
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng)
--
You received this bug n
I have also just noticed that the nvme drive seems to disappear 2 or 3
minutes after the system has re-awakened, so whilst it consistently
seems to happen *after* resume from S3, it is not *on* resume.
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
Unfortunately there seems no improvement, system boots fine, and
operates fine, but nvme disappears again after suspend. However I didn't
see any spontaneous disappearance of device (so could be some progress ?
but will need to test for longer to be certain)
log extracts:
Jul 28 09:36:18 phs08 ke
Ok, thanks, will try and report back...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1705748
Title:
Samsung SSD 960 EVO 500GB refused to change power state
Status in linux package in
Try the kernel here, it adds a delay before controller reset.
http://people.canonical.com/~khfeng/lp1705748-2/
---
diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
index f15f4017fb95..1dc42006a8fd 100644
--- a/drivers/nvme/host/pci.c
+++ b/drivers/nvme/host/pci.c
@@ -2308,6 +2308,8
One curious thing I note, probably irrelevant, is that after resume,
there is lots of stuff recorded in the logs that seem to be about
suspending.. e.g. Freezing remaing tasks after the computer has
resumed...
ul 25 01:42:58 phs08 systemd[1]: Reached target Sleep.
Jul 25 01:42:58 phs08 systemd
Unfortunately the problem is still there with this 4.11 kernel...
After initial install of the kernel and a suspend/resume it all seemed ok, but
then after leaving suspended overnight, the disk goes missing again, see
extracts below.
Jul 25 01:30:54 phs08 kernel: [0.00] Command line:
BO
1 - 100 of 108 matches
Mail list logo
