x220 fails to resume from suspend

[scary]

Hello everyone,
I've been experiencing this problem lately with my x220 (i5 2410),
namely the laptop isn't able to resume after suspend anymore. The power led blinks when suspended as usual, but then when I try to resume, the system seems to be booting up, the BT icon is turned on, the light above the webcam is turned on for a split second, and then the laptop seemingly shuts down for a second, I hear some click from the HD as if I forced a shutdown, and the whole thing starts over again. This kind of cycle goes on forever until I keep the power button pressed down for 10 secs or so and forcibly shut down the system (needless to say, this is bad).

Now, this is happening under both windows (with all lenovo power manager bla blah installed and updated to latest version via the lenovo update tool) _and_ linux, so I'm tempted to exclude it's a SW problem.

The only possible culprit I can think of (other than some strange hw failure?) is the bios. Now, I'm sure suspend/resume DID work in the beginning, then there was maybe some update (including bios) and at some point the thing stopped working properly. I'm not sure this is what started it, since I don't use suspend that often.... Anyhow, it sure doesn't work with the latest bios from the lenovo system update (1.24 is it ?) and I also tried to update it with a more recent one from the lenovo website (1.25 it says), still no go.

Is anybody else experiencing this? I don't have any strange expansion card or sd etc, I even disabled bluetooth from bios, nothing changed. Should I attempt /downgrading/ the bios? is that even doable?

Any help on this would be greatly appreciated!

[no_man]

my X220 (i7,8GB,SSD,WIN7-ULT64) has done that once, the issue was the battery was drained(no power remaining). A charged battery solved the issue for me.

[scary]

Unfortunately this happens with a (charged) battery and even when plugged to AC

[GomJabbar]

Some suspend issues are addressed in BIOS updates, and others in Windows Update Modules.

http://support.lenovo.com/en_US/researc ... MIGR-77280

[scary]

Well, other than updating the bios to the latest version, keeping windows up to date and downloading all updates with lenovo system update I don't know what to do
And as I said, the fact that this happens with linux as well makes me think it's not a software/OS issue ..
Also, if it was a bios issue, I guess I wouldn't be the only one experiencing it ...

I've been looking around and some guy on the lenovo forums had a very similar problem, in the end he sent the laptop for repair and got his motherboard changed.. I'm afraid I will have to do the same

[GomJabbar]

I believe those Windows Update Modules in the link I posted do not show up with a normal Windows Update. If you did a clean install, you should probably install all of them. Most of them should already be installed otherwise. Try running Lenovo System Update (Update and Drivers) from Lenovo ThinkVantage Tools (off the Start menu button) and see what it finds to update.

[scary]

I had already all system updates installed..

Good news (?): I downgraded the bios to Version 1.22-1.12
and now suspend/resume seems to be working !! Already when suspending, the system behaves differently,
for example I cannot hear this "click" anymore (hard to describe, it's not really a click, more like what you would get when forcibly shutting down the laptop by pressing the power button for a few seconds..)

This is weird though, 'cause by looking at the changelogs I don't really see what happened between version 1.22 and 1.24 that would break suspend

Version 1.24-1.13
UEFI: 1.24 / ECP: 1.13

(New) Improved memory resource allocation process to reserve more memory space for optional hardware devices.
(Fix) Corrected a description of VERSION in this README document.
(Fix) Fixed an issue that intranet account login failure for ThinkVantage Hardware Password Manager
(Fix) Allowed system recovery from POST 191 error without loading setup defaults in BIOS setup menu by press F9 key.

Although I have no idea what this ECP is. But still, I find it kind of strange that nobody else is experiencing this problem with bios 1.24/25 ? What should I make of this?