04-13-2020, 10:17 AM
(03-16-2020, 08:23 AM)amiraeva Wrote:(03-16-2020, 06:32 AM)ssfrfr@ Wrote:(02-11-2020, 07:32 PM)tsys Wrote:(02-11-2020, 10:58 AM)tophneal Wrote: s3 also doesn't seem to work with the presence of an NVMe device.
Not in general. I have an NVMe drive installed and it works fine for me. Are there any errors in the kernel message log? Those might help to figure out what is going wrong.
from my system, 5.6.0-rc4 custom build from gitlab.manjaro.org:
[ 92.398922] PM: suspend entry (s2idle)
[ 92.410407] Filesystems sync: 0.011 seconds
[ 92.413114] dwmmc_rockchip fe310000.mmc: pre_suspend failed for non-removable host: -38
[ 92.413833] Freezing user space processes ... (elapsed 0.003 seconds) done.
[ 92.417714] OOM killer disabled.
[ 92.417999] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 92.420304] printk: Suspending console(s) (use no_console_suspend to debug)
[ 98.476403] rockchip-pcie f8000000.pcie: PCIe link enter L2 timeout!
[ 98.476426] PM: dpm_run_callback(): rockchip_pcie_suspend_noirq+0x0/0x130 returns -110
[ 98.476432] PM: Device f8000000.pcie failed to suspend noirq: error -110
[ 98.496671] PM: noirq suspend of devices failed
[ 98.726837] usb usb5: root hub lost power or was reset
[ 98.726844] usb usb6: root hub lost power or was reset
[ 98.906339] usb usb7: root hub lost power or was reset
[ 98.906347] usb usb8: root hub lost power or was reset
[ 98.906806] cdn-dp fec00000.dp: [drm:cdn_dp_pd_event_work [rockchipdrm]] Not connected. Disabling cdn
[ 99.012380] nvme nvme0: 6/0/0 default/read/poll queues
[ 99.070831] OOM killer enabled.
[ 99.071110] Restarting tasks ... done.
[ 99.074307] PM: suspend exit
my NVME is a Samsung PM951 I pulled out of a surface book.
It goes to sleep, then wakes right back up.
For what it's worth, I get a very similar error with an Intel 660p 1 TB in dmesg. Goes to sleep then wakes back up soon after.
I have a Intel 660p (512GB) and see the same behaviour and messages. I'm running Manjaro-ARM 20.04 with the standard kernel (5.6.0-1-MANJARO-ARM). Aside from this issue, the 660p is working well, although I haven't tried any intensive IO with it yet.