Between v4.3.0 and v4.4.0-rc1 mainline kernels began creating new devices for a PCIe disk (http://poweredbymushkin.com/index.php/catalog/item/36-scorpion-deluxe/839-scorpion-deluxe-960gb).  An error is detected on the file system supported by the disk, on the old device, and it's switched to read-only.  In the case in question, this includes the root file system, so there's not much to go on in terms of logs.  There are crypto and lvm layers involved, but it seems the issue is with the block devices.

For example, the result of suspending and resuming is the addition of a new device (while retaining the old one).....
root@host1:~# uname -a
Linux host1 4.5.0-2-amd64 #1 SMP Debian 4.5.4-1 (2016-05-16) x86_64 GNU/Linux
root@host1:~# root@host1:~# ls -l /dev/sd*
brw-rw---- 1 root disk 8,  0 Jun 11 12:29 /dev/sda
brw-rw---- 1 root disk 8,  1 Jun 11 12:29 /dev/sda1
brw-rw---- 1 root disk 8,  2 Jun 11 12:29 /dev/sda2
brw-rw---- 1 root disk 8,  3 Jun 11 12:29 /dev/sda3
brw-rw---- 1 root disk 8,  4 Jun 11 12:29 /dev/sda4
brw-rw---- 1 root disk 8,  5 Jun 11 12:29 /dev/sda5
brw-rw---- 1 root disk 8, 16 Jun 11 12:29 /dev/sdb
brw-rw---- 1 root disk 8, 17 Jun 11 12:29 /dev/sdb1
brw-rw---- 1 root disk 8, 18 Jun 11 12:29 /dev/sdb2
brw-rw---- 1 root disk 8, 19 Jun 11 12:29 /dev/sdb3
brw-rw---- 1 root disk 8, 20 Jun 11 12:29 /dev/sdb4
brw-rw---- 1 root disk 8, 32 Jun 11 12:29 /dev/sdc
brw-rw---- 1 root disk 8, 48 Jun 11 12:29 /dev/sdd
root@host1:~# echo mem >> /sys/power/state 
root@host1:~# 
root@host1:~# ls -l /dev/sd*
brw-rw---- 1 root disk 8,  0 Jun 11 12:29 /dev/sda
brw-rw---- 1 root disk 8,  1 Jun 11 12:29 /dev/sda1
brw-rw---- 1 root disk 8,  2 Jun 11 12:29 /dev/sda2
brw-rw---- 1 root disk 8,  3 Jun 11 12:29 /dev/sda3
brw-rw---- 1 root disk 8,  4 Jun 11 12:29 /dev/sda4
brw-rw---- 1 root disk 8,  5 Jun 11 12:29 /dev/sda5
brw-rw---- 1 root disk 8, 16 Jun 11 12:29 /dev/sdb
brw-rw---- 1 root disk 8, 17 Jun 11 12:29 /dev/sdb1
brw-rw---- 1 root disk 8, 18 Jun 11 12:29 /dev/sdb2
brw-rw---- 1 root disk 8, 19 Jun 11 12:29 /dev/sdb3
brw-rw---- 1 root disk 8, 20 Jun 11 12:29 /dev/sdb4
brw-rw---- 1 root disk 8, 32 Jun 11 12:29 /dev/sdc
brw-rw---- 1 root disk 8, 48 Jun 11 12:29 /dev/sdd
brw-rw---- 1 root disk 8, 64 Jun 11 12:30 /dev/sde
brw-rw---- 1 root disk 8, 65 Jun 11 12:30 /dev/sde1
brw-rw---- 1 root disk 8, 66 Jun 11 12:30 /dev/sde2
brw-rw---- 1 root disk 8, 67 Jun 11 12:30 /dev/sde3
brw-rw---- 1 root disk 8, 68 Jun 11 12:30 /dev/sde4
root@host1:~# 

The device which was on /dev/sdb is now /dev/sde.  On the console, there are errors like...
[57.966939] blk_update_request: I/O error, dev sdb, sector 9157040
[57.966947] Aborting journal on device dm-1-8.
etc

The same thing happens on every custom-compiled kernel tried from v4.4.0-rc1 to v4.6.0, but is not present in a custom-compiled v4.3.0 kernel. Bisecting is not giving much joy - I keep ending up with kernels that won't boot.
  
Note that /dev/sda is a SATA disk that is quite happy, so apologies if this report is misdirected to "power management" when it's actually a problem elsewhere.