Homepage
Forum
Drivers
HMM
MTM
Feed
Within the last two months my normally trusty X220 i7 has developed a nasty problem where it crashes some 30 secs after a sleep/suspend signal has been issued (after the screen has gone black). This happens about 9/10 times, but not all. It has never acted up in any other way before with crashes an such.
This guy has described exact the same problem, but his “solution” does not apply:
https://unix.stackexchange.com/question ... ded-to-ram
Here’s what I’ve tried and thought:
- Battery was old and not good. Tried to buy a new one, same problem. A bit daft, since it also happens on AC – but the batt was EOL, so I thought it was worth a try
- I was running Debian buster when the problem began. So I tried to upgrade to bullseye, same problem. Perhaps my total install was messed, so I’ve tried boot from a USB live image, same, but perhaps not so often. Some mess in the Debian drivers?, I tried a Ubuntu live, same. There is nothing whatsoever to find in journal logs or others when it happens – it looks like a normal suspend, upon startup there is note about recovering disk (from the crash) but nothing other. On a controlled reboots there are not driver errors or similar in the logs. I don’t have a Win image to try with.
- Faulty nodes on the SSD? Tried to put replace with an older spindle drive and installed Ubuntu, same.
- Funky signal route mismatch from lid-close in Gnome? Tried Fn+F4 and “systemctl suspend”, same.
- Tried “hibernate” (which is very wonky on its own), same.
- Tried to shift the two 4Gb RAM modules around, exchanged them with some others, same. Tried a single module in either socket, same.
- Tried to upgrade BIOS to 1.40 to 1.46, same.
The fact that a complete shutdown signal also hangs in “reboot: power down” for 30 secs, as the guy on Stackexchange also mentions, baffles me. But all in all it seems like some mean HW failure has arisen.
I’m lost…
Does anyone have experienced similar or have any good suggestions what to try?
Thanks,
Regards
Perif
