Somewhere in this long thread, I think, an engineer suggested the following.
Somehow, in my particular case - a case in which, on my ThinkPad X1CG6, no work-arounds worked and neither did the test version of the kernel patch - my motherboard was at fault.
Well, the engineer was right. For, I got my motherboard changed - for another reason - and 'deep sleep' now works properly.
Now, as it turns out - and the engineer who changed the motherboard did not tell me this - the new motherboard has a different model number to the old one. So either Lenovo has fixed the problem with a new version of the motherboard. Or else my old motherboard had an idiosyncratic fault.
By the way, did the kernel patch for the problem ever get merged?
Somewhere in this long thread, I think, an engineer suggested the following.
Somehow, in my particular case - a case in which, on my ThinkPad X1CG6, no work-arounds worked and neither did the test version of the kernel patch - my motherboard was at fault.
Well, the engineer was right. For, I got my motherboard changed - for another reason - and 'deep sleep' now works properly.
Now, as it turns out - and the engineer who changed the motherboard did not tell me this - the new motherboard has a different model number to the old one. So either Lenovo has fixed the problem with a new version of the motherboard. Or else my old motherboard had an idiosyncratic fault.
By the way, did the kernel patch for the problem ever get merged?