Bug 49371 - OCZ-VERTEX4 SSD stop working after suspend to ram/disk
Summary: OCZ-VERTEX4 SSD stop working after suspend to ram/disk
Status: NEW
Alias: None
Product: IO/Storage
Classification: Unclassified
Component: Serial ATA (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Jeff Garzik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-23 06:24 UTC by xorik
Modified: 2012-10-23 19:47 UTC (History)
2 users (show)

See Also:
Kernel Version: 3.4-3.6.3 (may be earlier)
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description xorik 2012-10-23 06:24:09 UTC 
Hi.
I have SSD:

$ sudo hdparm -i /dev/sd
/dev/sdb:
 Model=OCZ-VERTEX4, FwRev=1.4, SerialNo=OCZ-2F94OT7I13287951
 Config={ }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=12288
 BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=16
 (maybe): CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=250069680
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio3 pio4 
 DMA modes:  mdma0 mdma1 mdma2 
 UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6 
 AdvancedPM=no WriteCache=enabled
 Drive conforms to: Unspecified:  ATA/ATAPI-6,7
 * signifies the current active mode

When I to put my system to suspend2ram or suspend2disk, SSD stops working. If OS runs from this ssd, it hungs, (but nothing interesting in the syslog: http://ompldr.org/vZnRwag).

If I put system, running on hdd, I got this:

==================== sudo pm-suspend ===========================
[  146.696181] atl1c 0000:02:00.0: irq 44 for MSI/MSI-X
[  146.696317] atl1c 0000:02:00.0: atl1c: eth1 NIC Link is Up<100 Mbps Full Duplex>
[  146.740205] atl1c 0000:02:00.0: irq 44 for MSI/MSI-X
[  146.740345] atl1c 0000:02:00.0: atl1c: eth1 NIC Link is Up<100 Mbps Full Duplex>
[  147.244699] PM: Syncing filesystems ... done.
[  147.463764] PM: Preparing system for mem sleep
[  147.506098] Freezing user space processes ... (elapsed 0.01 seconds) done.
[  147.517116] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[  147.528104] PM: Entering mem sleep
[  147.528125] Suspending console(s) (use no_console_suspend to debug)
[  147.528513] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[  147.528595] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  147.528599] sd 1:0:0:0: [sdb] Stopping disk
[  147.530872] serial 00:08: disabled
[  147.530891] serial 00:08: wake-up capability disabled by ACPI
[  147.537919] sd 0:0:0:0: [sda] Stopping disk
[  149.144117] PM: suspend of devices complete after 1615.727 msecs
[  149.144295] PM: late suspend of devices complete after 0.176 msecs
[  149.144437] pcieport 0000:00:1c.2: wake-up capability enabled by ACPI
[  149.155139] ehci_hcd 0000:00:1d.7: wake-up capability enabled by ACPI
[  149.166044] uhci_hcd 0000:00:1d.3: wake-up capability enabled by ACPI
[  149.166074] uhci_hcd 0000:00:1d.2: wake-up capability enabled by ACPI
[  149.166103] uhci_hcd 0000:00:1d.1: wake-up capability enabled by ACPI
[  149.166132] uhci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI
[  149.166178] PM: noirq suspend of devices complete after 21.880 msecs
[  149.166416] ACPI: Preparing to enter system sleep state S3
[  149.166836] PM: Saving platform NVS memory
[  149.166864] Disabling non-boot CPUs ...
[  149.168116] smpboot: CPU 1 is now offline
[  149.168441] CPU 1 offline: Remove Rx thread
[  149.168555] ACPI: Low-level resume complete
[  149.168555] PM: Restoring platform NVS memory
[  149.168555] Enabling non-boot CPUs ...
[  149.168555] smpboot: Booting Node 0 Processor 1 APIC 0x1
[  149.182012] bnx2i: CPU 1 online: Create Rx thread
[  149.183034] CPU1 is up
[  149.183700] ACPI: Waking up from system sleep state S3
[  149.206211] uhci_hcd 0000:00:1d.0: wake-up capability disabled by ACPI
[  149.206232] uhci_hcd 0000:00:1d.1: wake-up capability disabled by ACPI
[  149.206252] uhci_hcd 0000:00:1d.2: wake-up capability disabled by ACPI
[  149.206273] uhci_hcd 0000:00:1d.3: wake-up capability disabled by ACPI
[  149.217063] ehci_hcd 0000:00:1d.7: wake-up capability disabled by ACPI
[  149.239247] PM: noirq resume of devices complete after 55.101 msecs
[  149.239338] PM: early resume of devices complete after 0.065 msecs
[  149.239365] i915 0000:00:02.0: setting latency timer to 64
[  149.239478] snd_hda_intel 0000:00:1b.0: irq 43 for MSI/MSI-X
[  149.239529] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[  149.239550] usb usb2: root hub lost power or was reset
[  149.239563] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[  149.239582] usb usb3: root hub lost power or was reset
[  149.239593] uhci_hcd 0000:00:1d.2: setting latency timer to 64
[  149.239612] usb usb4: root hub lost power or was reset
[  149.239623] uhci_hcd 0000:00:1d.3: setting latency timer to 64
[  149.239642] usb usb5: root hub lost power or was reset
[  149.239655] ehci_hcd 0000:00:1d.7: setting latency timer to 64
[  149.239673] pci 0000:00:1e.0: setting latency timer to 64
[  149.239683] ata_piix 0000:00:1f.2: setting latency timer to 64
[  149.239692] pcieport 0000:00:1c.2: wake-up capability disabled by ACPI
[  149.240062] serial 00:08: activated
[  149.257391] atl1c 0000:02:00.0: irq 44 for MSI/MSI-X
[  149.456168] ata2.00: NODEV after polling detection
[  149.456170] ata2.00: revalidation failed (errno=-2)
[  149.706031] usb 4-1: reset low-speed USB device number 2 using uhci_hcd
[  150.856586] atl1c 0000:02:00.0: atl1c: eth1 NIC Link is Up<100 Mbps Full Duplex>
[  154.402090] ata1: link is slow to respond, please be patient (ready=0)
[  154.617132] ata2.00: NODEV after polling detection
[  154.617133] ata2.00: revalidation failed (errno=-2)
[  159.770159] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
[  159.770161] ata1.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
[  159.770162] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[  159.778153] ata2.00: NODEV after polling detection
[  159.778154] ata2.00: revalidation failed (errno=-2)
[  159.778155] ata2.00: disabled
[  159.778165] ata2: soft resetting link
[  159.786014] ata1.00: configured for UDMA/133
[  159.786074] sd 0:0:0:0: [sda] Starting disk
[  159.939720] ata2: EH complete
[  159.939743] sd 1:0:0:0: [sdb] Starting disk
[  159.939754] sd 1:0:0:0: [sdb] START_STOP FAILED
[  159.939756] sd 1:0:0:0: [sdb]  
[  159.939757] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[  159.939763] dpm_run_callback(): scsi_bus_resume_common+0x0/0x69 returns 262144
[  159.939766] PM: Device 1:0:0:0 failed to resume async: error 262144
[  159.939894] PM: resume of devices complete after 10700.553 msecs
[  159.940088] PM: Finishing wakeup.
[  159.940089] Restarting tasks ... done.
[  162.409321] atl1c 0000:02:00.0: irq 44 for MSI/MSI-X
[  162.409459] atl1c 0000:02:00.0: atl1c: eth1 NIC Link is Up<100 Mbps Full Duplex>
[  162.544155] atl1c 0000:02:00.0: irq 44 for MSI/MSI-X
[  162.544290] atl1c 0000:02:00.0: atl1c: eth1 NIC Link is Up<100 Mbps Full Duplex>
[  163.324112] uhci_hcd 0000:00:1d.0: setting latency timer to 64
[  163.358719] uhci_hcd 0000:00:1d.1: setting latency timer to 64
[  163.394916] uhci_hcd 0000:00:1d.3: setting latency timer to 64

==================== power on ==================================
[  177.969850] sd 1:0:0:0: [sdb] Unhandled error code
[  177.969856] sd 1:0:0:0: [sdb]  
[  177.969858] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[  177.969862] sd 1:0:0:0: [sdb] CDB: 
[  177.969864] Read(10): 28 00 00 00 00 00 00 01 00 00
[  177.969874] end_request: I/O error, dev sdb, sector 0
[  177.969877] Buffer I/O error on device sdb, logical block 0
[  177.969884] Buffer I/O error on device sdb, logical block 1
[  177.969887] Buffer I/O error on device sdb, logical block 2
[  177.969890] Buffer I/O error on device sdb, logical block 3
[  177.969893] Buffer I/O error on device sdb, logical block 4
[  177.969896] Buffer I/O error on device sdb, logical block 5
[  177.969898] Buffer I/O error on device sdb, logical block 6
[  177.969901] Buffer I/O error on device sdb, logical block 7
[  177.969904] Buffer I/O error on device sdb, logical block 8
[  177.969908] sd 1:0:0:0: [sdb] Unhandled error code
[  177.969910] sd 1:0:0:0: [sdb]  
[  177.969911] Buffer I/O error on device sdb, logical block 9
[  177.969916] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[  177.969919] sd 1:0:0:0: [sdb] CDB: 
[  177.969921] Read(10): 28 00 00 00 00 00 00 00 08 00
[  177.969931] end_request: I/O error, dev sdb, sector 0
[  180.481832] sd 1:0:0:0: [sdb] Unhandled error code
[  180.481836] sd 1:0:0:0: [sdb]  
[  180.481838] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[  180.481840] sd 1:0:0:0: [sdb] CDB: 
[  180.481842] Read(10): 28 00 00 00 00 00 00 01 00 00
[  180.481848] end_request: I/O error, dev sdb, sector 0
[  180.481895] sd 1:0:0:0: [sdb] Unhandled error code
[  180.481897] sd 1:0:0:0: [sdb]  
[  180.481898] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[  180.481900] sd 1:0:0:0: [sdb] CDB: 
[  180.481901] Read(10): 28 00 00 00 00 00 00 00 08 00
[  180.481906] end_request: I/O error, dev sdb, sector 0

I think this is linux kernel bug, because when I use windows 7, installed on this ssd, both suspend2ram and suspend2disk works perfect.
Comment 1 Dimitris Damigos 2012-10-23 08:36:11 UTC 
It should be the same bug I reported yesterday.
https://bugzilla.kernel.org/show_bug.cgi?id=49331
Is your system a Vaio? Another user has reported the same bug on a Vaio.
https://bbs.archlinux.org/viewtopic.php?id=150774
Comment 2 xorik 2012-10-23 08:46:53 UTC 
No, i try it on my laptop Samsung r-528 and on PC with linux, installed on hdd
Comment 3 Felix 2012-10-23 19:47:32 UTC 
May be the same bug. OpenSUSE 12.2 with default kernel 3.4.11-2.16-desktop installed on OCZ Vertex 4 128 GB which connected to jmicron controller (AHCI or IDE mode - no difference) on ASUS P5KC M/B. Hard freezes or complete system hangs after s2ram only, not after hibernate. But there is no problem at all if SSD connected to the ICH9 controller which support only IDE mode.

hdparm output:

# hdparm -i /dev/sdc

/dev/sdc:

 Model=OCZ-VERTEX4, FwRev=1.5, SerialNo=OCZ-WW1RM1ZIU1K470Y5
 Config={ }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=12288
 BuffType=unknown, BuffSize=unknown, MaxMultSect=16, MultSect=16
 (maybe): CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=250069680
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio3 pio4 
 DMA modes:  mdma0 mdma1 mdma2 
 UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6 
 AdvancedPM=no WriteCache=enabled
 Drive conforms to: Unspecified:  ATA/ATAPI-6,7

 * signifies the current active mode

syslog fragment after awakening from s2ram:

Oct 21 13:47:56 PC kernel: [ 1691.008186] ata2.00: failed command: WRITE FPDMA QUEUED
Oct 21 13:47:56 PC kernel: [ 1691.008189] ata2.00: cmd 61/00:70:68:95:54/04:00:02:00:00/40 tag 14 ncq 524288 out
Oct 21 13:47:56 PC kernel: [ 1691.008190]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 21 13:47:56 PC kernel: [ 1691.008192] ata2.00: status: { DRDY }
Oct 21 13:47:56 PC kernel: [ 1691.008194] ata2.00: failed command: WRITE FPDMA QUEUED
Oct 21 13:47:56 PC kernel: [ 1691.008197] ata2.00: cmd 61/00:78:68:99:54/04:00:02:00:00/40 tag 15 ncq 524288 out
Oct 21 13:47:56 PC kernel: [ 1691.008198]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 21 13:47:56 PC kernel: [ 1691.008200] ata2.00: status: { DRDY }
Oct 21 13:47:56 PC kernel: [ 1691.008202] ata2.00: failed command: WRITE FPDMA QUEUED
Oct 21 13:47:56 PC kernel: [ 1691.008205] ata2.00: cmd 61/00:80:68:9d:54/04:00:02:00:00/40 tag 16 ncq 524288 out
Oct 21 13:47:56 PC kernel: [ 1691.008206]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 21 13:47:56 PC kernel: [ 1691.008208] ata2.00: status: { DRDY }
Oct 21 13:47:56 PC kernel: [ 1691.008210] ata2.00: failed command: WRITE FPDMA QUEUED
Oct 21 13:47:56 PC kernel: [ 1691.008213] ata2.00: cmd 61/00:88:68:a1:54/04:00:02:00:00/40 tag 17 ncq 524288 out
Oct 21 13:47:56 PC kernel: [ 1691.008214]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 21 13:47:56 PC kernel: [ 1691.008216] ata2.00: status: { DRDY }
Oct 21 13:47:56 PC kernel: [ 1691.008218] ata2.00: failed command: WRITE FPDMA QUEUED
Oct 21 13:47:56 PC kernel: [ 1691.008222] ata2.00: cmd 61/00:90:68:a5:54/04:00:02:00:00/40 tag 18 ncq 524288 out
Oct 21 13:47:56 PC kernel: [ 1691.008222]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 21 13:47:56 PC kernel: [ 1691.008224] ata2.00: status: { DRDY }
Oct 21 13:47:56 PC kernel: [ 1691.008226] ata2.00: failed command: WRITE FPDMA QUEUED
Oct 21 13:47:56 PC kernel: [ 1691.008230] ata2.00: cmd 61/00:98:68:a9:54/04:00:02:00:00/40 tag 19 ncq 524288 out
Oct 21 13:47:56 PC kernel: [ 1691.008230]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 21 13:47:56 PC kernel: [ 1691.008232] ata2.00: status: { DRDY }
Oct 21 13:47:56 PC kernel: [ 1691.008234] ata2.00: failed command: WRITE FPDMA QUEUED
Oct 21 13:47:56 PC kernel: [ 1691.008238] ata2.00: cmd 61/00:a0:68:ad:54/04:00:02:00:00/40 tag 20 ncq 524288 out
Oct 21 13:47:56 PC kernel: [ 1691.008239]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 21 13:47:56 PC kernel: [ 1691.008241] ata2.00: status: { DRDY }
Oct 21 13:47:56 PC kernel: [ 1691.008242] ata2.00: failed command: WRITE FPDMA QUEUED
Oct 21 13:47:56 PC kernel: [ 1691.008246] ata2.00: cmd 61/00:a8:68:b1:54/04:00:02:00:00/40 tag 21 ncq 524288 out
Oct 21 13:47:56 PC kernel: [ 1691.008247]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 21 13:47:56 PC kernel: [ 1691.008249] ata2.00: status: { DRDY }
Oct 21 13:47:56 PC kernel: [ 1691.008250] ata2.00: failed command: WRITE FPDMA QUEUED
Oct 21 13:47:56 PC kernel: [ 1691.008254] ata2.00: cmd 61/00:b0:68:b5:54/04:00:02:00:00/40 tag 22 ncq 524288 out
Oct 21 13:47:56 PC kernel: [ 1691.008255]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 21 13:47:56 PC kernel: [ 1691.008257] ata2.00: status: { DRDY }
Oct 21 13:47:56 PC kernel: [ 1691.008258] ata2.00: failed command: WRITE FPDMA QUEUED
Oct 21 13:47:56 PC kernel: [ 1691.008262] ata2.00: cmd 61/18:b8:68:b9:54/02:00:02:00:00/40 tag 23 ncq 274432 out
Oct 21 13:47:56 PC kernel: [ 1691.008263]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 21 13:47:56 PC kernel: [ 1691.008265] ata2.00: status: { DRDY }
Oct 21 13:47:56 PC kernel: [ 1691.008267] ata2.00: failed command: WRITE FPDMA QUEUED
Oct 21 13:47:56 PC kernel: [ 1691.008270] ata2.00: cmd 61/10:c0:30:e7:d6/00:00:04:00:00/40 tag 24 ncq 8192 out
Oct 21 13:47:56 PC kernel: [ 1691.008271]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 21 13:47:56 PC kernel: [ 1691.008273] ata2.00: status: { DRDY }
Oct 21 13:47:56 PC kernel: [ 1691.008275] ata2.00: failed command: WRITE FPDMA QUEUED
Oct 21 13:47:56 PC kernel: [ 1691.008278] ata2.00: cmd 61/08:c8:70:bc:cf/00:00:03:00:00/40 tag 25 ncq 4096 out
Oct 21 13:47:56 PC kernel: [ 1691.008279]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 21 13:47:56 PC kernel: [ 1691.008281] ata2.00: status: { DRDY }
Oct 21 13:47:56 PC kernel: [ 1691.008283] ata2.00: failed command: READ FPDMA QUEUED
Oct 21 13:47:56 PC kernel: [ 1691.008286] ata2.00: cmd 60/08:d0:f8:a2:40/00:00:01:00:00/40 tag 26 ncq 4096 in
Oct 21 13:47:56 PC kernel: [ 1691.008287]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Oct 21 13:47:56 PC kernel: [ 1691.008289] ata2.00: status: { DRDY }
Oct 21 13:47:56 PC kernel: [ 1691.008293] ata2: hard resetting link
Oct 21 13:47:57 PC kernel: [ 1691.468026] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct 21 13:47:57 PC kernel: [ 1691.469273] ata2.00: configured for UDMA/133
Oct 21 13:47:57 PC kernel: [ 1691.480018] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480021] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480024] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480027] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480029] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480031] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480034] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480036] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480039] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480041] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480044] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480046] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480049] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480051] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480054] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480056] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480058] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480061] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480063] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480066] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480068] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480071] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480073] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480076] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480078] ata2.00: device reported invalid CHS sector 0
Oct 21 13:47:57 PC kernel: [ 1691.480081] ata2.00: device reported invalid CHS sector 0
Note You need to log in before you can comment on or make changes to this bug.