Can confirm yes also -25 Kernel on Asus PN-50
--
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/1956821
Title:
System hangs on reboot and shutdown
Status in linux package in Ubuntu:
Same issue here on Asus PN50 Ryzen 5 4500U Bios 0623
Also with 5.13.0-23-generic
--
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/1957018
Title:
System hangs on reboot and shutdown
Same as #31 for me, Mint 20.2 (=Ubuntu 20.04) Nvidia 470.86
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1911055
Title:
[modeset][nvidia] suspend/resume broken
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.
$ 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
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
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
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-
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
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
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:
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
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:
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.
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
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
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
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
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:
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
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
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,
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.
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
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
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
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: [
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
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
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
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
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,
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
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
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
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:
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
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"
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
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.
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
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
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
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
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:
Many thanks, suggested kernel now under test...
--
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
Many thanks, suggested kernel now under test...
--
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
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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
Confirm that removing:
nvme_core.default_ps_max_latency_us=0
from boot params results in reproducible problem on resume from suspend.
Downloaded and installed 4.13 headers and generic kernel:
Linux version 4.13.0-041300rc1-generic
Unable to test issue with above kernel. System boots ok, but now
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1705748/+attachment/4918946/+files/Lspci.txt
--
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
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1705748/+attachment/4918945/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This is a brand new build, with Mint 18.2 installed intitally with
kernel 4.8.53, but upgraded straight away to latest kernel due to using
Ryzen cpu.
Will try to test with the 4.13 in the next 24 h
--
You received this bug notification because you are a member of Kernel
Packages, which is
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1705748/+attachment/4918953/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1705748/+attachment/4918949/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1705748/+attachment/4918950/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1705748/+attachment/4918951/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1705748/+attachment/4918948/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1705748/+attachment/4918943/+files/CRDA.txt
--
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
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1705748/+attachment/4918944/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1705748/+attachment/4918947/+files/Lsusb.txt
--
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
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1705748/+attachment/4918952/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected sonya
** Description changed:
Originally thought my issue was same as this:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
but requested to report as separate bug
System becomes unusable at seemingly random times but
Public bug reported:
Originally thought my issue was same as this:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
but requested to report as separate bug
System becomes unusable at seemingly random times but especially after
resume from suspend due to disk 'disappearing' becoming
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.
66 matches
Mail list logo
