Arch Linux

ss2

Member

Registered: 2007-10-05

Posts: 83

[SOLVED] ThinkPad X61s: Resume from Hibernation fails with Error -61

Hello, a long time lurker where who just succesfully resurrected this old profile from the dark edges of my hard disk.

I possess an old ThinkPad X61s that suffers from a problem in which it will randomly not successfully resume from hibernation.  It has gotten to the point where I gladly just want to find out what it is.  Yes, I've been trying to figure this problem in years now.  If I recall correctly, the hard disk was replaced with an SSD maybe five years ago.  At some point the mainboard had to be replaced too, after spilling coffee over it.  That was a joy, but it works fine ever since.

Except for resuming.  If it weren't for this, this machine would be perfect the way it works.  In my quest to find out the reason, I replaced the hard disk with a brand new SSD again, did a memtest, openned up the case all the way down to the mainboard being removed and cleaned the fan to a new state.  Then I removed xf86-video-intel, moved KMS to early KMS according to the manuals.  That last part, I hadn't known yet that this driver isn't used anymore.

No chance.  Here a snippet of the boot log:

[    2.751879] sd 0:0:0:0: [sda] 468875199 512-byte logical blocks: (240 GB/224 GiB)
[    2.751913] sd 0:0:0:0: [sda] Write Protect is off
[    2.751916] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    2.751968] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    2.756552]  sda: sda1 sda2 sda3
[    2.757853] sd 0:0:0:0: [sda] Attached SCSI disk
[    2.868144] PM: Image signature found, resuming
[    2.868147] PM: resume from hibernation
[    2.868294] Freezing user space processes ... (elapsed 0.001 seconds) done.
[    2.869487] OOM killer disabled.
[    2.869597] PM: Marking nosave pages: [mem 0x00000000-0x00000fff]
[    2.869599] PM: Marking nosave pages: [mem 0x0009d000-0x000fffff]
[    2.869604] PM: Marking nosave pages: [mem 0xbf6b0000-0xffffffff]
[    2.870756] PM: Basic memory bitmaps created
[    2.967697] PM: Using 1 thread(s) for decompression
[    2.967699] PM: Loading and decompressing image data (388397 pages)...
[    3.219818] PM: Image loading progress:   0%
[    5.238802] PM: Image loading progress:  10%
[    6.106339] PM: Image loading progress:  20%
[    6.419952] random: crng init done
[    6.979103] PM: Image loading progress:  30%
[    7.884791] PM: Image loading progress:  40%
[    8.706948] PM: Image loading progress:  50%
[    9.539675] PM: Image loading progress:  60%
[   10.383901] PM: Image loading progress:  70%
[   11.263028] PM: Image loading progress:  80%
[   12.079039] PM: Image loading progress:  90%
[   12.744791] PM: Image loading progress: 100%
[   12.744933] PM: Image loading done
[   12.744937] PM: Invalid image CRC32!
[   12.744941] PM: Read 1553588 kbytes in 9.77 seconds (159.01 MB/s)
[   12.746567] PM: Error -61 resuming
[   12.746584] PM: Failed to load hibernation image, recovering.
[   12.841577] PM: Basic memory bitmaps freed
[   12.841581] OOM killer enabled.
[   12.841582] Restarting tasks ... done.
[   12.843902] video LNXVIDEO:00: Restoring backlight state
[   12.845219] PM: resume from hibernation failed (-61)
[   13.311447] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)

From there on the system will boot from scratch recovering the journal -- which can be frustrating making this laptop very unreliable as I really like to boot from hibernation.  Honestly, I've looked through the interwebs for answers, and I haven't found much so far.  Especially trying to figure out what Error -61 and Invalid image CRC32! could mean.

This weird problem just dosn't make sense to me.  Given that the mainboard and hard disk have been been replaced, I am hoping to claim that this is still a software problem, but I can't be sure if not.

Hence I want to reach out for help here with hopes to settle this annoyance for good.

[EDIT]

Marking this thread as solved. In the mean time I replaced the mainboard, effectively solving the problem.  I can only guess the previous mainboard was faulty and had problems while booting.

Last edited by ss2 (2020-01-10 16:33:19)