I can confirm that the problem does not happen when cache is on SATA vs.
NVME. I assume this needs to get pushed to the kernel then? Please
advise.
cache
nvme0n1p5 OFFLINE 0 0 0
sda3ONLINE 0 0 0
Linux mp
I am also seeing this issue with zfs and l2arc cache on an NVMe and
4.10.14 on zesty. I've seen it in the past with btrfs, and a bcache
cache on NVMe as well, but not with the bcache cache on a SATA SSD. I
will move my zfs l2arc cache to a SATA SSD to see if that fixes suspend.
This is probably an
I think this is more of an symptom of the cache being located on an NVMe
drive which are notorious for causing power problems. I'm closing this
until I can validate on a non-NVMe drive.
** Changed in: zfs-linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification
Same results with 4.8 kernel & pm_trace as above:
Linux mp 4.8.0-39-generic #42~16.04.1-Ubuntu SMP Mon Feb 20 15:06:07 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
2017-03-05 10:032017-03-05 15:03 UTCKernelOops linux-
image-4.8.0-39-generic
Occurs while suspend to ram, attempted pm_trace (sudo sh -c "sync && echo 1 >
/sys/power/pm_trace && pm-suspend"):
...
[1.196689] Key type encrypted registered
[1.196712] AppArmor: AppArmor sha1 policy hashing enabled
[1.442937] evm: HMAC attrs: 0x1
[1.444273] Magic number:
Precision 5510 BIOS version: 1.2.19 (latest)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670137
Title:
zfs l2arc cache inhibits proper suspend
To manage notifications about this bug go to:
