You are not logged in.
- Topics: Active | Unanswered
#1 2010-11-01 20:20:29
- DarksideEE7
- Member
- From: Arkansas, United States
- Registered: 2009-06-06
- Posts: 356
OCZ Vertex 2 fails to fully resume from suspend to RAM
I have installed an OCZ Vertex 2 60GB SSD in my laptop and I cannot resume normally from S3 using pm-suspend or any other method. It looks like / isn't remounting, however it does seem that home is remounting.
I have flashed the firmware to the latest. I tested suspend after a base install, with only acpi and hal (pm-utils being a dep for hal) and it failed.
Here is fstab, mtab, and fdisk -l. If any other information is needed let me know.
Disk /dev/sda: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xb8372fcd
Device Boot Start End Blocks Id System
/dev/sda1 2048 206847 102400 83 Linux
/dev/sda2 206848 21178367 10485760 83 Linux
/dev/sda3 21178368 117231407 48026520 83 Linuxproc /proc proc rw,relatime
sys /sys sysfs rw,relatime
udev /dev devtmpfs rw,nosuid,relatime,size=10240k,nr_inodes=502347,mode=755
/dev/disk/by-uuid/fd40337d-ed8a-4e76-be3f-aa09f5558998 / ext4 rw,noatime,barrier=1,data=ordered,discard
devpts /dev/pts devpts rw 0 0
shm /dev/shm tmpfs rw,nosuid,nodev 0 0
/dev/sda3 /home ext4 rw,noatime,discard 0 0
/dev/sda1 /boot ext2 rw 0 0
none /tmp tmpfs rw,nosuid,nodev,noatime,size=1000M,mode=1777 0 0#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
#/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
#/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
UUID=8f046367-0eec-410f-b3b5-0e298e065c5e /home ext4 defaults,noatime,discard 0 1
UUID=a6f6aa9a-e5d8-4763-ad75-0b0b6c549929 /boot ext2 defaults 0 1
UUID=fd40337d-ed8a-4e76-be3f-aa09f5558998 / ext4 defaults,noatime,discard 0 1
none /tmp tmpfs nodev,nosuid,noatime,size=1000M,mode=1777 0 0Here are some errors after suspend:
http://img180.imageshack.us/f/fserror.jpg/
I've also been advised to try enter S1, however I'm not sure how to do that since power states don't seem to work like this anymore (since kernel 2.6):
#echo 1 > sleepI'm very frustrated at this point and I will be extremely gracious for any advice on this problem 
Offline
#2 2010-11-01 21:17:23
- surfed
- Member
- From: Vienna Austria
- Registered: 2009-10-30
- Posts: 86
Re: OCZ Vertex 2 fails to fully resume from suspend to RAM
just as a note that i have same drive without your problem. same fstab and all works well....what laptop are u using?
Offline
#3 2010-11-01 21:21:53
- DarksideEE7
- Member
- From: Arkansas, United States
- Registered: 2009-06-06
- Posts: 356
Re: OCZ Vertex 2 fails to fully resume from suspend to RAM
just as a note that i have same drive without your problem. same fstab and all works well....what laptop are u using?
ASUS UL30A-X4. How did you go about aligning your partitions? I booted into the net install USB, then aligned everything using fdisk, created then filesystems, then entered /arch/setup. It doesn't let you skip the 'Prepare the hard drives' section AFAIK, so I had to select 'Manually prepare', then ignore the prompts. I saved the output of fdisk when I aligned it manually in a spreadsheet:
Disk /dev/sdc: 60.0 GB, 60022480896 bytes
32 heads, 32 sectors/track, 114483 cylinders, total 117231408 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xb8372fcd
Device Boot Start End Blocks Id System
/dev/sdc1 2048 206847 102400 83 Linux
/dev/sdc2 206848 21178367 10485760 83 Linux
/dev/sdc3 21178368 117231407 48026520 83 Linux However when I run fdisk on the laptop I get:
Disk /dev/sda: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders, total 117231408 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xb8372fcd
Device Boot Start End Blocks Id System
/dev/sda1 2048 206847 102400 83 Linux
/dev/sda2 206848 21178367 10485760 83 Linux
/dev/sda3 21178368 117231407 48026520 83 LinuxI guess the install rewrote it. I am prepared to reinstall if you could let me know how you aligned and set up your drive with /arch/setup......
Many thanks for the response, I'm feeling much better now. 
Last edited by DarksideEE7 (2010-11-01 21:22:50)
Offline
#4 2010-11-01 21:55:53
- surfed
- Member
- From: Vienna Austria
- Registered: 2009-10-30
- Posts: 86
Re: OCZ Vertex 2 fails to fully resume from suspend to RAM
On further digging i have the vertex 1 not 2, but i dont see why it should be a problem. Originally i partitioned my drive with chakra linux's intaller "tribe" only after they dropped kdemod i switched to arch but without reformat/partitioning. I wonder why your first partition starts at 2048 all of mine SSD/HDD and USB partitions start at 63. SDA is my OCZ sdb is my external hdd and sdc is a usb stick.
sudo fdisk -l
Password:
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders, total 125045424 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x96088b2a
Device Boot Start End Blocks Id System
/dev/sda1 63 116647964 58323951 83 Linux
/dev/sda2 116647965 125033894 4192965 82 Linux swap / Solaris
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xd73508a1
Device Boot Start End Blocks Id System
/dev/sdb1 63 80324 40131 6 FAT16
/dev/sdb2 * 80325 30800324 15360000 7 HPFS/NTFS
/dev/sdb3 30812670 282743999 125965665 7 HPFS/NTFS
/dev/sdb4 282744000 976768064 347012032+ 5 Extended
/dev/sdb5 282744063 976768064 347012001 83 Linux
Disk /dev/sdc: 32.1 GB, 32078036992 bytes
255 heads, 63 sectors/track, 3899 cylinders, total 62652416 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xc3072e18Last edited by surfed (2010-11-01 21:57:06)
Offline
#5 2010-11-01 22:03:02
- surfed
- Member
- From: Vienna Austria
- Registered: 2009-10-30
- Posts: 86
Re: OCZ Vertex 2 fails to fully resume from suspend to RAM
maybe post the output of:
sudo hdparm -I /dev/sda
Offline
#6 2010-11-01 22:05:46
- DarksideEE7
- Member
- From: Arkansas, United States
- Registered: 2009-06-06
- Posts: 356
Re: OCZ Vertex 2 fails to fully resume from suspend to RAM
When I use fdisk manually in a terminal (I just checked on a flash drive) it defaults to 2048. I read that you must set the initial value to the >= the erase block size (I believe that's what it's called) in order to have it properly aligned. I just used 2048 to be safe.
BTW you probably shouldn't use a swap file....that will add a lot of IO activity that will degrade the lifespan of the drive.
I'm going to reinstall....right now I'm just trying to formulate a plan. After all there is a finite amount of reads/writes on these drives. There is a 3 year warranty, however.
Funny you should mention hdparm, I was just reading through that before you posted. Here it is:
/dev/sda:
ATA device, with non-removable media
Model Number: OCZ-VERTEX2
Serial Number: OCZ-29TG7J1907SP9GNE
Firmware Revision: 1.23
Transport: Serial
Standards:
Used: unknown (minor revision code 0x0028)
Supported: 8 7 6 5
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 117231408
LBA48 user addressable sectors: 117231408
Logical Sector size: 512 bytes
Physical Sector size: 512 bytes
Logical Sector-0 offset: 0 bytes
device size with M = 1024*1024: 57241 MBytes
device size with M = 1000*1000: 60022 MBytes (60 GB)
cache/buffer size = unknown
Nominal Media Rotation Rate: Solid State Device
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, no device specific minimum
R/W multiple sector transfer: Max = 16 Current = 1
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* NOP cmd
* DOWNLOAD_MICROCODE
SET_MAX security extension
* 48-bit Address feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* 64-bit World wide name
* IDLE_IMMEDIATE with UNLOAD
* WRITE_UNCORRECTABLE_EXT command
* Segmented DOWNLOAD_MICROCODE
* Gen1 signaling speed (1.5Gb/s)
* Gen2 signaling speed (3.0Gb/s)
* Native Command Queueing (NCQ)
* Host-initiated interface power management
* Phy event counters
* DMA Setup Auto-Activate optimization
Device-initiated interface power management
* Software settings preservation
* SMART Command Transport (SCT) feature set
* SCT LBA Segment Access (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
* Data Set Management TRIM supported (limit 1 block)
* Deterministic read data after TRIM
Security:
supported
not enabled
not locked
frozen
not expired: security count
not supported: enhanced erase
400min for SECURITY ERASE UNIT. 400min for ENHANCED SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 5e83a97fbee61cc8
NAA : 5
IEEE OUI : e83a97
Unique ID : fbee61cc8
Checksum: correctLast edited by DarksideEE7 (2010-11-01 22:06:46)
Offline
#7 2010-11-01 22:27:08
- DarksideEE7
- Member
- From: Arkansas, United States
- Registered: 2009-06-06
- Posts: 356
Re: OCZ Vertex 2 fails to fully resume from suspend to RAM
You know I never really messed around with cfdisk but it actually is much more intuitive than fdisk. I'm testing on a flash drive to see how to align with 32 heads/32 sectors alignment and then I'm going to reinstall arch. Fingers crossed.......
Still open to suggestions!
Offline
#8 2010-11-01 22:31:10
- surfed
- Member
- From: Vienna Austria
- Registered: 2009-10-30
- Posts: 86
Re: OCZ Vertex 2 fails to fully resume from suspend to RAM
maybe read this:
http://www.ocztechnologyforum.com/forum … -alignment
swap is debatable i have 4gb ram so swap is very rarely used and by the time i have reached the drives max read/write cycle i am sure i will have upgraded...
read this:
http://www.storagesearch.com/ssdmyths-endurance.html
so with the average sdd rated at >1000000 write cycles i am not worried....
Offline
#9 2010-11-01 22:32:49
- DarksideEE7
- Member
- From: Arkansas, United States
- Registered: 2009-06-06
- Posts: 356
Re: OCZ Vertex 2 fails to fully resume from suspend to RAM
maybe read this:
http://www.ocztechnologyforum.com/forum … -alignment
swap is debatable i have 4gb ram so swap is very rarely used and by the time i have reached the drives max read/write cycle i am sure i will have upgraded...
read this:
http://www.storagesearch.com/ssdmyths-endurance.htmlso with the average sdd rated at >1000000 write cycles i am not worried....
Good, that makes me feel better. I've actually read that thread at OCZ, and posted a tweak from our wiki for putting Chromium's profile in tmpfs.
I appreciate the help. Right now I'm trying to find out the exact erase block size for my drive then I'm going to reinstall....I would think hdparm would be able to report it, but it doesn't.
Last edited by DarksideEE7 (2010-11-01 22:33:38)
Offline
#10 2010-11-01 22:39:54
- surfed
- Member
- From: Vienna Austria
- Registered: 2009-10-30
- Posts: 86
Re: OCZ Vertex 2 fails to fully resume from suspend to RAM
i think it is 512kb
Offline
#11 2010-11-01 22:43:51
- surfed
- Member
- From: Vienna Austria
- Registered: 2009-10-30
- Posts: 86
Re: OCZ Vertex 2 fails to fully resume from suspend to RAM
Offline
#12 2010-11-01 22:46:03
- DarksideEE7
- Member
- From: Arkansas, United States
- Registered: 2009-06-06
- Posts: 356
Re: OCZ Vertex 2 fails to fully resume from suspend to RAM
Yea either will work, I just called tech support and they said as long as it's divisible by 64 kB it's all good.
Well fingers crossed....
Offline
#13 2010-11-01 23:14:42
- DarksideEE7
- Member
- From: Arkansas, United States
- Registered: 2009-06-06
- Posts: 356
Re: OCZ Vertex 2 fails to fully resume from suspend to RAM
I have cfdisk working well except for one thing....I don't know how to specify the start sector. I have a 32/32 partition table, however it asks for beginning/end on partition location....doesn't allow you to specify sector location.
Any ideas?
Offline
#14 2010-11-01 23:18:06
- graysky
- Wiki Maintainer
- From: :wq
- Registered: 2008-12-01
- Posts: 10,734
- Website
Re: OCZ Vertex 2 fails to fully resume from suspend to RAM
https://wiki.archlinux.org/index.php/SS … bservation
?
Also, if you haven't read it already: https://wiki.archlinux.org/index.php/SSD
Last edited by graysky (2010-11-01 23:18:31)
Offline
#15 2010-11-01 23:22:13
- DarksideEE7
- Member
- From: Arkansas, United States
- Registered: 2009-06-06
- Posts: 356
Re: OCZ Vertex 2 fails to fully resume from suspend to RAM
https://wiki.archlinux.org/index.php/SS … bservation
?
Also, if you haven't read it already: https://wiki.archlinux.org/index.php/SSD
Yes, I've read the SSD wiki page. With the partition table I created it showed my boot partition starting at sector 32 when I ran fdisk -l. I was just a bit confused because I'm used to fdisk.....
It seems I'm getting contradictory information on the first partition's sector location. According to this it must be >= the EBS or divisible by the EBS.
http://www.ocztechnologyforum.com/forum … sing-fdisk
Alignment (Part 2 - the rule)
Ahhh. Alignment. How crazy it is I loathe you. It's pretty easy and much easier once you know the practice behind partitioning using sectors. It's gonna be a walk in the park. I promise. When it comes to alignment, you only need to keep 1 rule in your head. The starting sector must be divisible by 512 evenly (no remainder). It does not matter the size of the partition or where that partition ends. All that matters is that the partition you create starts on a sector divisible by 512 (evenly).
However in the arch wiki it has the first partitions sector location as 32....
If 1 sector = 512 bytes then I should be good. Ugh, I'm a bit tired 
I think the problem with that SSD guide at OCZ forums it that he's confusing his units. The EBS is in bytes, while he's interchanging sectors and bytes. At least that's how I read it.
Last edited by DarksideEE7 (2010-11-01 23:29:03)
Offline
#16 2010-11-02 00:24:46
- DarksideEE7
- Member
- From: Arkansas, United States
- Registered: 2009-06-06
- Posts: 356
Re: OCZ Vertex 2 fails to fully resume from suspend to RAM
So far base installed, hdparm reports 256 MB/s. So far so good. On to getting suspend to work.
EDIT:
Well my base system plus hal, pm-utils, and vim can't suspend to ram. Great. It suspends, then upon returning I just get the prompt with the command remaining. Caps lock toggles, I can ping (on ethernet ATM, used to not be able to ping on wifi). I can't ssh into the laptop either. Ctrl+alt+del doesn't work either.
Last edited by DarksideEE7 (2010-11-02 00:40:38)
Offline
#17 2010-11-02 00:53:18
- surfed
- Member
- From: Vienna Austria
- Registered: 2009-10-30
- Posts: 86
Re: OCZ Vertex 2 fails to fully resume from suspend to RAM
hmm digging around it seems you are not the only one... are u using latest FW?
Last edited by surfed (2010-11-02 00:54:27)
Offline
#18 2010-11-02 00:56:20
- DarksideEE7
- Member
- From: Arkansas, United States
- Registered: 2009-06-06
- Posts: 356
Re: OCZ Vertex 2 fails to fully resume from suspend to RAM
hmm digging around it seems you are not the only one... are u using latest FW?
Yea I talked to someone at Phoronix earlier today who had the same problem. He just RMA'd and got an Intel SSD. For the price and speed of this drive I suppose I can do without suspend.
Who knows what the future may bring as far as firmware updates go. Maybe a kernel update will fix it.....
It is DAMN fast though. I'm getting another one for my desktop probably soon and merging all of my mechanical HDDs to my RAID5 array
Offline
#19 2010-11-04 07:28:43
- DarksideEE7
- Member
- From: Arkansas, United States
- Registered: 2009-06-06
- Posts: 356
Re: OCZ Vertex 2 fails to fully resume from suspend to RAM
I just successfully suspended to RAM. I was redirecting the log file to text file to make sure it kept it.....here it is. I'm going to check it out further to see if a package update fixed it, or if it was simply dumb luck.
/usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
Kernel modesetting video driver detected, not using quirks.
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
kernel.acpi_video_flags = 0
/usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
Mon Nov 1 19:35:30 CDT 2010: performing suspend
Initial commandline parameters:
Thu Nov 4 00:54:33 CDT 2010: Running hooks for suspend.
Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend:
Linux l33tpc 2.6.36-ARCH #1 SMP PREEMPT Sun Oct 31 09:29:11 CET 2010 x86_64 Genuine Intel(R) CPU U7300 @ 1.30GHz GenuineIntel GNU/Linux
Module Size Used by
cryptd 6262 0
aes_x86_64 7412 1
aes_generic 26170 1 aes_x86_64
ipv6 281961 14
ext2 63599 1
usb_storage 42540 0
uvcvideo 61404 0
videodev 64318 1 uvcvideo
v4l1_compat 15578 2 uvcvideo,videodev
v4l2_compat_ioctl32 10212 1 videodev
arc4 1378 2
ecb 2041 2
snd_hda_codec_intelhdmi 10645 1
snd_hda_codec_realtek 275631 1
i915 320893 2
snd_seq_dummy 1431 0
ath9k 79976 0
snd_seq_oss 28760 0
joydev 10055 0
snd_seq_midi_event 5436 1 snd_seq_oss
snd_hda_intel 22253 0
snd_seq 50082 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 5297 3 snd_seq_dummy,snd_seq_oss,snd_seq
uhci_hcd 21926 0
snd_hda_codec 79192 3 snd_hda_codec_intelhdmi,snd_hda_codec_realtek,snd_hda_intel
mac80211 195924 1 ath9k
drm_kms_helper 25963 1 i915
snd_pcm_oss 39157 0
snd_mixer_oss 17106 1 snd_pcm_oss
ath9k_common 3496 1 ath9k
snd_hwdep 6110 1 snd_hda_codec
drm 175314 2 i915,drm_kms_helper
ath9k_hw 289341 2 ath9k,ath9k_common
snd_pcm 71921 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
ath 8822 2 ath9k,ath9k_hw
ehci_hcd 36860 0
i2c_algo_bit 4911 1 i915
asus_laptop 14243 0
i2c_core 18726 5 videodev,i915,drm_kms_helper,drm,i2c_algo_bit
sparse_keymap 2563 1 asus_laptop
snd_timer 19265 2 snd_seq,snd_pcm
ac 3105 0
vboxdrv 1740411 0
battery 10039 0
cfg80211 142886 3 ath9k,mac80211,ath
snd 57562 11 snd_hda_codec_realtek,snd_seq_oss,snd_seq,snd_hda_intel,snd_seq_device,snd_pcm_oss,snd_hda_codec,snd_hwdep,snd_mixer_oss,snd_pcm,snd_timer
atl1c 31532 0
video 19305 1 i915
iTCO_wdt 10669 0
sg 25652 0
processor 25936 2
rfkill 15882 2 asus_laptop,cfg80211
soundcore 5969 1 snd
psmouse 52592 0
output 1940 1 video
iTCO_vendor_support 1801 1 iTCO_wdt
thermal 12242 0
button 4834 1 i915
usbcore 137506 5 usb_storage,uvcvideo,uhci_hcd,ehci_hcd
evdev 8519 7
serio_raw 4486 0
intel_agp 29427 2 i915
led_class 2331 2 ath9k,asus_laptop
pcspkr 1819 0
snd_page_alloc 7249 2 snd_hda_intel,snd_pcm
ext4 313574 2
mbcache 5722 2 ext2,ext4
jbd2 69002 1 ext4
crc16 1297 1 ext4
sd_mod 25824 4
ahci 20353 3
libahci 17886 1 ahci
libata 156316 2 ahci,libahci
scsi_mod 124859 4 usb_storage,sg,sd_mod,libata
total used free shared buffers cached
Mem: 4020904 219844 3801060 0 22892 53336
-/+ buffers/cache: 143616 3877288
Swap: 0 0 0
/usr/lib/pm-utils/sleep.d/00logging suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:
/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub suspend suspend:
/usr/lib/pm-utils/sleep.d/01grub suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/11netcfg suspend suspend:
/usr/lib/pm-utils/sleep.d/11netcfg suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:
/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend:
Having NetworkManager put all interaces to sleep...Done.
/usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:
/usr/lib/pm-utils/sleep.d/75modules suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:
/usr/lib/pm-utils/sleep.d/90clock suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/91wicd suspend suspend:
/usr/lib/pm-utils/sleep.d/91wicd suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:
/usr/lib/pm-utils/sleep.d/95led suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend:
Kernel modesetting video driver detected, not using quirks.
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend:
kernel.acpi_video_flags = 0
/usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
Thu Nov 4 00:54:34 CDT 2010: performing suspend
Thu Nov 4 00:57:50 CDT 2010: Awake.
Thu Nov 4 00:57:50 CDT 2010: Running hooks for resume
Running hook /usr/lib/pm-utils/sleep.d/99video resume suspend:
/usr/lib/pm-utils/sleep.d/99video resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend:
/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95led resume suspend:
/usr/lib/pm-utils/sleep.d/95led resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq resume suspend:
/usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/91wicd resume suspend:
/usr/lib/pm-utils/sleep.d/91wicd resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock resume suspend:
/usr/lib/pm-utils/sleep.d/90clock resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules resume suspend:
Reloaded unloaded modules.
/usr/lib/pm-utils/sleep.d/75modules resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend:
Having NetworkManager wake interfaces back up...Done.
/usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth resume suspend:
/usr/lib/pm-utils/sleep.d/49bluetooth resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/11netcfg resume suspend:
/usr/lib/pm-utils/sleep.d/11netcfg resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub resume suspend:
/usr/lib/pm-utils/sleep.d/01grub resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave resume suspend:
/usr/lib/pm-utils/sleep.d/00powersave resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/00logging resume suspend:
/usr/lib/pm-utils/sleep.d/00logging resume suspend: success.
Thu Nov 4 00:57:52 CDT 2010: Finished.It failed again. I have compared the logs and the last entry is :
/usr/lib/pm-utils/sleep.d/99video suspend suspend: success.
Thu Nov 4 01:24:45 CDT 2010: performing suspendLast edited by DarksideEE7 (2010-11-04 07:29:06)
Offline
#20 2012-11-03 18:41:29
- hirs
- Member
- Registered: 2003-10-11
- Posts: 18
- Website
Re: OCZ Vertex 2 fails to fully resume from suspend to RAM
Hi,
I have an Asus ul30a with a 60GB OCZ vertex2, and 90% of the times I try to resume from suspend it fails. I'm using the latest firmware 1.37.
Other distros behave the same, the disk just doesn't wake up.
This is my partition table, I don't use swap, but it makes no difference:
Disk /dev/sda: 60.0 GB, 60022480896 bytes, 117231408 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00066da1
Device Boot Start End Blocks Id System
/dev/sda1 2048 40962047 20480000 83 Linux
/dev/sda2 40962048 93435903 26236928 83 Linux
/dev/sda3 * 93435904 117228872 11896484+ 83 LinuxOffline