Hibernation Works in 10.10 *but* is 700% Slower. Why, How??

[vbgunz]

Hibernation works. It does. Using the Lucid kernels, I hibernated in 15 seconds with plenty of applications running. The latest Maverick mainline kernel (2.6.36-rc7), I can hibernate in 15 seconds. The current Maverick kernel (2.6.35-22) is 1:45 seconds.

Wth happened?

From being told "hibernation works, be happy" and "report a bug" the help that I've gotten so far about this sucks. Hibernation is critically important to me and why should I report a bug with the only evidence being "it's slow for me, not for you". It's not empirical. I don't want to cry bug. I'll go a couple weeks uploading files, the status will go from low to duplicate and by the time the answer is here it's in the form of Natty Narwhal.

I already see this coming.

I don't mean to be shrewd or mean about it, nothing is owed to me, I love this distro *but* I am stuck between a rock and a hard place and I already been over this months before at #ubuntu+1. I was told to basically go away and shew or report a bug. Really? It's obviously only my problem and without some rock solid evidence and troubleshooting skills reporting a bug is almost like breaking out of prison using a plastic spoon.

At least that's how I feel about it.

TL:DR
Heres the kicker. I can't really fallback to the Lucid kernels as they do not support TRIM for my SSD. I can't really use the 2.6.36+ Maverick RCs because I always seem to deadlock and freeze up. I can in no way turn the verbosity up. The only verbosity I get when suspending is an extrememly informative blinking underscore. That's it :( It's like a horse doing the kicking. As long as it's kicking I know it's doing the math :/

How do I turn the verbosity up? Extremely high? As least get a bold blinking underscore? Red would be nice? All jokes aside, how do I figure out why in the world my hibernation is 2.6.35 is 700% slower than anything before or after? Resuming is the same across all kernels. I'm back up in 15 seconds flat.

[vbgunz]

bump!

Fun Fact: In just 2 hours after posting the original topic above, this help request ended up on page 5.

[vek]

I think I might be getting the same issue - when I tell it to hibernate, it goes to the usual flashing underscore, turns off the secondary monitor, etc...

But I haven't actually considered waiting for 1:30 or longer to tell if its working or not. I figured it was locked up. Either way, something is broken, its clearly not intentional to take 100-200 times longer (I also have an SSD, so perhaps thats a commonality here? Due to the SSD being used for the hibernate storage, it was usually just a second or two to hibernate).

Edit: I just tried just waiting and it eventually successfully shut down to hibernate! But it took like 4 minutes. This is a very fast machine with a very fast HDD, it used to take a handful of seconds, now it takes minutes? This is much more than 700% slower.

[vbgunz]

Hey Vek, if you didn't uninstall your older Lucid kernel (in case you did an upgrade), can you try hibernating with that kernel?

[cyberkilla]

My Sony Vaio VGN-AR41E does a similar thing...

Hibernating worked in Karmic. It stopped working after I upgraded to Maverick. I get a flashing cursor on black screen, with no HDD activity.

I've never waited long enough to see if it would finally hibernate. After a minute or two of doing nothing, I just force emergency unmount and power off.

:facepalm:

[aspz]

I have the same problem with the blinking underscore after upgrading from 10.04 to 10.10 only it isn't just slow, hibernation never completes at all. I wouldn't mind if it just took a few minutes as I could just leave the PC sitting there and go home.

I also have an SSD (OCZ Vertex 2 60GB). Could be a clue there.

[vbgunz]

I've narrowed my issue down to the current kernel. The Lucid kernels and the latest vanilla 2.6.36-rc kernels hibernate in 15 seconds for me. The current kernel is up pass 700% slower to hibernate.

No matter what kernel I use though, I always have the blinking underscore when going into hibernation. The current and all future rc kernels as of this posting are nicely verbose when resuming.

I would really rather not fall back to using an older kernel from Lucid without TRIM *but* at the same time, even if I did, the older kernels give me a problem with my virtual terminals. Something about the framebuffer is going crazy on me

[vek]

I just verified that its the kernel change, too... 2.6.32-25 hibernates in about 5 seconds, but the latest takes about 4 minutes.

Perhaps the commonality here is the SSD? If you're affected by this (and I mean a VERY SLOW hibernate, not a non-working hibernate, thats more likely to be a different issue), do you have a SSD?

The latest kernel stuff added support for discard/TRIM stuff, so its a bit of a clue. IF you do have a SSD, is the swap on it?

[vbgunz]

I have an OCZ Vertex 2. Performance is excellent. I made the leap to SSD for one thing and that was hibernation. So when this went down I noticed right away. I dual boot for stuff that cannot be solved in Virtualbox so hibernating and resuming quicker than a normal shutdown/startup is always important to me.

Here's my hdparm -I /dev/disk

ATA device, with non-removable media
        Model Number:       OCZ-VERTEX2                             
        Firmware Revision:  1.11    
        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
        not     frozen
        not     expired: security count
        not     supported: enhanced erase
Logical Unit WWN Device Identifier: 5e83a97f1ed3cc16
        NAA             : 5
        IEEE OUI        : e83a97
        Unique ID       : f1ed3cc16
Checksum: correct

[vbgunz]

My swap is the first partition on the SSD. It's at 12GB.