System freeze after resume from suspend to RAM

Question

Hi,
since quite a while (probably ever) I am unable to suspend my computer to RAM because everytime it freezes a few seconds after resuming, never to become alive again until a reboot. After some investigation, I managed to get kernel logs by taking a picture of my screen. The logs were not written to disk, hence I didn't see anything before. I had to write these by hand, I hope I didn't insert any mistakes:
kernel: sas: Enter sas_scsi_recover_host busy: 2 failed: 2
kernel: sas: trying to find task 0xfff880008b5b680
kernel: sas: sas_scsi_find_task: aborting task 0xfff880008b5b680
kernel: sas: sas_scsi_find_task: task 0xfff880008b5b680 is aborted
kernel: sas: sas_eh_handle_sas_errors: task 0xfff880008b5b680 is aborted
kernel: sas: trying to find task 0xffff8804606ccb40
kernel: sas: sas_scsi_find_task: aborting task 0xffff8804606ccb40
kernel: sas: sas_scsi_find_task: task 0xffff8804606ccb40 is aborted
kernel: sas: sas_eh_handle_sas_errors: task 0xffff8804606ccb40 is aborted
kernel: sas: ata7: end_device-0:0: cmd error handler
kernel: sas: ata8: end_device-0:1: cmd error handler
kernel: sas: ata7: end_device-0:0: dev error handler
kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
kernel: ata7.00: failed command: READ VERIFY SECTOR(S)
kernel: ata7.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 11
res 40/00:48:a0:79:88/00:00:07:00:00/40 Emask 0x4 (timeout)
kernel: ata7.00: status { DRDY }
kernel: ata7: hard resetting link
kernel: sas: ata8: end_device-0:1: dev error handler
kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
kernel: ata8.00: failed command: READ VERIFY SECTOR(S)
kernel: ata8.00: cmd 40/00:01:00:00:00/00:00:00:00:00/e0 tag 11
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
kernel: ata8.00: status { DRDY }
kernel: ata8: hard resetting link
This issue seems to be related to disk failures like bad sectors but I am quite sure, that my SSDs are in a good shape. I ran some SMART tests, they all turned out to be okay. Suspending from my dual-booted Windows works fine as well (although if the bad sector would be on the linux partition, it would probably not affect Windows).
Here's my setup:
$ lsblk -St
NAME HCTL TYPE VENDOR MODEL REV TRAN NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED RQ-SIZE RA WSAME
sda 1:0:0:0 disk ATA Corsair Force 3 2 sata sda 0 512 0 512 512 0 cfq 128 128 0B
sdb 7:0:0:0 disk ST1000DM 003-9YN162 NDP3 usb sdb 0 512 0 512 512 1 cfq 128 128 0B
sdc 0:0:0:0 disk ATA OCZ-REVODRIVE3 2.25 sas sdc 0 512 0 512 512 0 cfq 128 128 0B
sdd 0:0:1:0 disk ATA OCZ-REVODRIVE3 2.25 sas sdd 0 512 0 512 512 0 cfq 128 128 0B
sr0 2:0:0:0 rom TSSTcorp CDDVDW SH-222AL SB00 sata sr0 0 512 0 512 512 1 cfq 128 128 0B
$ lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 ntfs Recovery 567437B974379B27
├─sda2 vfat DC2D-099E /boot
├─sda3
├─sda4 ntfs FEBED982BED933BD
├─sda5 ext4 arch 41bad924-84a2-4e0a-9cd4-4ea723a2a5a3 /
└─sda6 swap 793fb3c1-8bec-4023-a7c3-ee94eee2e67a [SWAP]
sdb
└─sdb1 ntfs HDDRIVE2GO 2212E50812E4E231
sdc
└─sdc1 linux_raid_member home:0 208937dc-2904-e71c-435a-9928671e07a3
└─md0 ext4 revodrive ffe9d38f-87f2-44e1-ae26-f36c910af3c5 /home
sdd
└─sdd1 linux_raid_member home:0 208937dc-2904-e71c-435a-9928671e07a3
└─md0 ext4 revodrive ffe9d38f-87f2-44e1-ae26-f36c910af3c5 /home
I am not sure which one of the disks causes the freeze but I assume it's the revodrive because the logs talk about two drives. The Revodrive internally holds two drives, which are set up to operate in a RAID 0. Windows is installed on the Corsair drive, and has no access to the Revodrive. However, I used to run Windows on the Revodrive a few years ago, and it worked just fine.
Another interesting thing is that when I try to test suspend to RAM, the system does not freeze, nor produce errors. This only happens if none is written to /sys/power/pm_test (which means no automated wake-up, no testing).
Any ideas on how I could narrow down this issue? Thanks a lot!
EDIT
I just checked and confirmed that this issue is originating from the OCZ Revodrive:
$ dmesg | grep ata7.00 | head
[ 7.136432] ata7.00: ATA-8: OCZ-REVODRIVE3, 2.25, max UDMA/133
[ 7.136436] ata7.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 7.146442] ata7.00: configured for UDMA/133
$ dmesg | grep ata8.00 | head
[ 7.310018] ata8.00: ATA-8: OCZ-REVODRIVE3, 2.25, max UDMA/133
[ 7.310023] ata8.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 7.320022] ata8.00: configured for UDMA/133
Last edited by tuttiarch (2015-01-31 15:54:29)

Answer 1

Thank you for the link, unfortunally I don't have a NVIDIA card but use the Intel IGP (HD4600, Haswell) - maybe I should have mentioned that...
And other than in this bug report I cannot kill X or anything because neither other TTYs work - I cannot input anything (although the hotkeys work weird enough) nor is SSHD running because the system is completely frozen...
Very funny thing is that for the last 2 days my system didnt freeze once (suspended about 6-7 times during one boot), even though for the 2 weeks prior to that, it froze EVERY SINGLE TIME I resumed from suspend, it didnt work once...